fix(conductor): remove hardcoded path hints in favor of Universal File Resolution Protocol

Author: moisgobg

commands/conductor/implement.toml

@@ -63,7 +63,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
     a. **Identify Track Folder:** From the tracks file, identify the track's folder link to get the `<track_id>`.
     b. **Read Files:**
         -   **Track Context:** Using the **Universal File Resolution Protocol**, resolve and read the **Specification** and **Implementation Plan** for the selected track.
-        -   **Workflow:** Resolve **Workflow** (Default: `conductor/workflow.md`).
+        -   **Workflow:** Resolve **Workflow** (via the **Universal File Resolution Protocol** using the project's index file).
     c. **Error Handling:** If you fail to read any of these files, you MUST stop and inform the user of the error.
 
 4.  **Execute Tasks and Update Track Plan:**

commands/conductor/newTrack.toml

@@ -91,7 +91,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
 2.  **Generate Plan:**
     *   Read the confirmed `spec.md` content for this track.
-    *   Resolve and read the **Workflow** file (Default: `conductor/workflow.md`).
+    *   Resolve and read the **Workflow** file (via the **Universal File Resolution Protocol** using the project's index file).
     *   Generate a `plan.md` with a hierarchical list of Phases, Tasks, and Sub-tasks.
     *   **CRITICAL:** The plan structure MUST adhere to the methodology in the **Workflow** file (e.g., TDD tasks for "Write Tests" and "Implement").
     *   Include status markers `[ ]` for **EVERY** task and sub-task. The format must be:

commands/conductor/revert.toml

@@ -45,7 +45,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 
     *   **PATH B: Guided Selection Menu**
         1.  **Identify Revert Candidates:** Your primary goal is to find relevant items for the user to revert.
-            *   **Scan All Plans:** You MUST read the **Tracks Registry** and every track's **Implementation Plan** (resolved via **Universal File Resolution Protocol**, checking `conductor/tracks/<track_id>/index.md` if available).
+            *   **Scan All Plans:** You MUST read the **Tracks Registry** and every track's **Implementation Plan** (resolved via **Universal File Resolution Protocol** using the track's index file).
             *   **Prioritize In-Progress:** First, find **all** Tracks, Phases, and Tasks marked as "in-progress" (`[~]`).
             *   **Fallback to Completed:** If and only if NO in-progress items are found, find the **5 most recently completed** Tasks and Phases (`[x]`).
         2.  **Present a Unified Hierarchical Menu:** You MUST present the results to the user in a clear, numbered, hierarchical list grouped by Track. The introductory text MUST change based on the context.

commands/conductor/status.toml

@@ -32,7 +32,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai
 2.  **Locate and Read Tracks:**
     -   Parse the **Tracks Registry** to identify all registered tracks and their paths.
         *   **Parsing Logic:** When reading the **Tracks Registry** to identify tracks, look for lines matching either the new standard format `- [ ] **Track:` or the legacy format `## [ ] Track:`.
-    -   For each track, resolve and read its **Implementation Plan** (using **Universal File Resolution Protocol**, checking `conductor/tracks/<track_id>/index.md` if available).
+    -   For each track, resolve and read its **Implementation Plan** (using **Universal File Resolution Protocol** via the track's index file).
 
 ### 2.2 Parse and Summarize Plan
 1.  **Parse Content:**