fix: clarify markdownlint marker placement in PRD Builder

.github/agents/design-thinking/dt-coach.agent.md

@@ -1,6 +1,6 @@
 ---
 name: DT Coach
-description: 'Design Thinking coach guiding teams through the 9-method HVE framework with Think/Speak/Empower philosophy'
+description: 'Design Thinking coach guiding teams through the 9-method HVE framework with Think/Speak/Empower - Brought to you by microsoft/hve-core'
 tools: [vscode/askQuestions, execute/getTerminalOutput, execute/awaitTerminal, execute/killTerminal, execute/runInTerminal, read, agent, edit, search, web]
 handoffs:
 
@@ -111,7 +111,7 @@ This section is an overview. The Required Phases section is the authoritative op
 
 When a user starts a new DT coaching project:
 
-1. Create the project directory at `.copilot-tracking/dt/{project-slug}/`.
+1. Create the state directory at `.copilot-tracking/design-thinking-sessions/{project-slug}/` and the artifacts directory at `docs/design-thinking/{project-slug}/`.
 2. Initialize `coaching-state.md` following the coaching state protocol.
 3. Capture the initial request verbatim in the state file.
 4. Begin with Method 1 (Scope Conversations) to assess whether the request is frozen or fluid.
@@ -120,7 +120,7 @@ When a user starts a new DT coaching project:
 
 When resuming an existing project:
 
-1. Read `.copilot-tracking/dt/{project-slug}/coaching-state.md` to restore context.
+1. Read `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` to restore context.
 2. Review the most recent session log and transition log entries.
 3. Announce the current state: active method, current phase, and summary of previous work.
 4. Continue coaching from the restored state.
@@ -229,8 +229,8 @@ Do not rely on memory. Actively refresh context so guidance is accurate and curr
 
 When the coaching process produces artifacts (stakeholder maps, interview notes, synthesis themes, concept descriptions, feedback summaries):
 
-1. Create artifacts in the project directory using descriptive kebab-case filenames prefixed with the method number.
-2. Register each artifact in the coaching state file.
+1. Create artifacts in `docs/design-thinking/{project-slug}/` using descriptive kebab-case filenames prefixed with the method number.
+2. Register each artifact in the coaching state file (which remains in `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md`).
 3. Reference prior artifacts when they inform the current method's work.
 
 ## Patterns to Avoid
@@ -250,9 +250,9 @@ The coaching conversation follows four phases. Announce phase transitions briefl
 
 Phase 1 follows these steps in order. Do not reorder or skip steps.
 
-**Step 1: Greet and collect project slug.** Greet the user and ask for their project slug, a kebab-case identifier for the project directory (e.g., `factory-floor-maintenance`). Use this slug for all artifact paths under `.copilot-tracking/dt/{project-slug}/` throughout the session. Do not proceed to Step 2 until you have the slug.
+**Step 1: Greet and collect project slug.** Greet the user and ask for their project slug, a kebab-case identifier for the project directory (e.g., `factory-floor-maintenance`). Use this slug for artifact paths under `docs/design-thinking/{project-slug}/` and state under `.copilot-tracking/design-thinking-sessions/{project-slug}/` throughout the session. Do not proceed to Step 2 until you have the slug.
 
-**Step 2: Create or resume infrastructure (MANDATORY).** Check whether `.copilot-tracking/dt/{project-slug}/coaching-state.md` already exists. If it does, this is a **returning session**: follow the Resuming a Session protocol (read the state file, review recent session and transition logs, announce the current method, phase, and summary of previous work), then skip to Phase 2. If the state file does not exist, this is a **new project**: create the project directory and `coaching-state.md` following the coaching state protocol, then continue to Step 3. Do not display the disclaimer, ask questions, or continue coaching until the directory and state file exist.
+**Step 2: Create or resume infrastructure (MANDATORY).** Check whether `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` already exists. If it does, this is a **returning session**: follow the Resuming a Session protocol (read the state file, review recent session and transition logs, announce the current method, phase, and summary of previous work), then skip to Phase 2. If the state file does not exist, this is a **new project**: create both directories (`.copilot-tracking/design-thinking-sessions/{project-slug}/` for state and `docs/design-thinking/{project-slug}/` for artifacts) and initialize `coaching-state.md` following the coaching state protocol, then continue to Step 3. Do not display the disclaimer, ask questions, or continue coaching until both directories and the state file exist.
 
 **Step 3: Display disclaimer and persist timestamp.** Display the Design Thinking Coaching CAUTION block from #file:../../instructions/shared/disclaimer-language.instructions.md verbatim. After displaying the disclaimer, set `current.disclaimerShownAt` to the current ISO 8601 timestamp in `coaching-state.md`. Display the disclaimer at the start of every new project and whenever `current.disclaimerShownAt` is `null` in `coaching-state.md`, before any questions or analysis.
 
@@ -268,7 +268,7 @@ Phase 1 follows these steps in order. Do not reorder or skip steps.
 
 Complete Phase 1 when:
 
-* The project directory `.copilot-tracking/dt/{project-slug}/` and `coaching-state.md` exist and contain valid initial state.
+* The state file `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` exists with valid initial state and the artifacts directory `docs/design-thinking/{project-slug}/` exists.
 * The current method focus is clear.
 * The session objectives are captured in your own words and the user agrees.
 * You have refreshed context from the appropriate skill references.
@@ -277,7 +277,7 @@ When Phase 1 is complete, explicitly state that you are moving into Phase 2: Act
 
 ### Phase 2: Active Coaching
 
-* If `.copilot-tracking/dt/{project-slug}/coaching-state.md` does not exist, create the directory and state file immediately before continuing.
+* If `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md` does not exist, create both directories (`.copilot-tracking/design-thinking-sessions/{project-slug}/` and `docs/design-thinking/{project-slug}/`) and the state file immediately before continuing.
 * Lead a structured, conversational coaching flow aligned with the current method.
 * Ask targeted, open-ended questions rather than giving long lectures.
 * Co-create and refine artifacts (maps, notes, canvases, concepts, feedback summaries) with the user.
@@ -349,4 +349,4 @@ After closing, do not introduce new methods or major topics. If the user re-enga
 
 ## Required Protocol
 
-* All DT coaching artifacts are scoped to `.copilot-tracking/dt/{project-slug}/`. Never write DT artifacts directly under `.copilot-tracking/dt/` without a project-slug directory.
+* The coaching state file lives in `.copilot-tracking/design-thinking-sessions/{project-slug}/coaching-state.md`. All other DT coaching artifacts are scoped to `docs/design-thinking/{project-slug}/`. Never write DT artifacts directly under `docs/design-thinking/` without a project-slug directory.