switch skill docs to xdg mosaic config path

skills/kickstart/SKILL.md

@@ -38,7 +38,7 @@ Parse the argument (if any) provided after `/kickstart`:
 List open milestones and ask the user to choose:
 
 ```bash
-"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/milestone-list.sh" -s open
+"${MOSAIC_HOME:-$HOME/.config/mosaic}/rails/git/milestone-list.sh" -s open
 ```
 
 Present the results and ask:
@@ -101,8 +101,8 @@ Before orchestration begins, decide delegation mode:
 Fallback commands:
 
 ```bash
-~/.mosaic/bin/mosaic-orchestrator-matrix-cycle
-~/.mosaic/bin/mosaic-orchestrator-run --poll-sec 10
+~/.config/mosaic/bin/mosaic-orchestrator-matrix-cycle
+~/.config/mosaic/bin/mosaic-orchestrator-run --poll-sec 10
 ```
 
 ---
@@ -113,10 +113,10 @@ Fallback commands:
 
 ```bash
 # Get all open issues in this milestone
-"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-list.sh" -m "<milestone-name>" -s open
+"${MOSAIC_HOME:-$HOME/.config/mosaic}/rails/git/issue-list.sh" -m "<milestone-name>" -s open
 
 # For each issue, get details (labels, description)
-"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-view.sh" -i <number>
+"${MOSAIC_HOME:-$HOME/.config/mosaic}/rails/git/issue-view.sh" -i <number>
 ```
 
 Categorize issues by labels (feature, bug, task, security, etc.) to determine phasing.
@@ -124,7 +124,7 @@ Categorize issues by labels (feature, bug, task, security, etc.) to determine ph
 ### For issue target
 
 ```bash
-"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-view.sh" -i <number>
+"${MOSAIC_HOME:-$HOME/.config/mosaic}/rails/git/issue-view.sh" -i <number>
 ```
 
 Read the issue description, labels, and any linked milestone.
@@ -145,10 +145,10 @@ Report status to user before continuing.
 **CRITICAL:** Read the full orchestrator guide:
 
 ```
-Read ~/.mosaic/guides/orchestrator.md
+Read ~/.config/mosaic/guides/orchestrator.md
 ```
 
-Also load skills relevant to the project's tech stack from project docs (`AGENTS.md`/`SOUL.md`) plus `~/.mosaic/STANDARDS.md`. For example:
+Also load skills relevant to the project's tech stack from project docs (`AGENTS.md`/`SOUL.md`) plus `~/.config/mosaic/STANDARDS.md`. For example:
 - NestJS project → load `nestjs-best-practices`
 - Next.js project → load `next-best-practices`, `vercel-react-best-practices`
 - Python project → load `fastapi`, `python-performance-optimization`
@@ -214,14 +214,14 @@ Next task: MS-SEC-009 — "Add input validation to API endpoints"
 
 ## Step 5: Begin Orchestration
 
-You are now the **orchestrator**. Follow the protocol from `~/.mosaic/guides/orchestrator.md` exactly.
+You are now the **orchestrator**. Follow the protocol from `~/.config/mosaic/guides/orchestrator.md` exactly.
 
 ### Standing Orders (baked in — user never needs to specify these)
 
 1. **All coding changes go through workers** — you NEVER edit source code directly
 2. **All coding changes require** code review, security review, and QA passing before completion
 3. **Linting is mandatory** — workers MUST run the project linter and fix ALL violations in files they touch. Zero lint errors. No disabling rules. No skipping files. This is non-negotiable.
-4. **Completed issues are closed** in the repo via `"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-close.sh"`
+4. **Completed issues are closed** in the repo via `"${MOSAIC_HOME:-$HOME/.config/mosaic}/rails/git/issue-close.sh"`
 5. **tasks.md is the single source of truth** — you are the sole writer
 6. **Branch from `develop`** (or whatever was detected/confirmed in Step 1) as the upstream
 7. **Max 2 active worker tasks** at any time (applies to native and matrix modes)
@@ -240,7 +240,7 @@ WHILE tasks remain not-started or in-progress:
      - Quality gate commands
      - Expected JSON result format
      - Native mode: runtime Task/subagent primitive
-     - Matrix mode: queue task in `.mosaic/orchestrator/tasks.json` and run `~/.mosaic/bin/mosaic-orchestrator-matrix-cycle`
+     - Matrix mode: queue task in `.mosaic/orchestrator/tasks.json` and run `~/.config/mosaic/bin/mosaic-orchestrator-matrix-cycle`
   4. Parse worker result JSON
   5. Calculate variance: (actual - estimate) / estimate × 100
   6. Update tasks.md: status=done/failed, completed_at, used
@@ -275,7 +275,7 @@ do NOT skip files. If you changed it, you lint it.
 
 ### Skills
 Read these before starting:
-- ~/.mosaic/skills/{relevant-skill}/SKILL.md
+- ~/.config/mosaic/skills/{relevant-skill}/SKILL.md
 
 ### Report Format
 When done, report as JSON:
@@ -299,7 +299,7 @@ To resume, run:
 /kickstart resume
 
 Or programmatically:
-[runtime command] "Read ~/.mosaic/skills/kickstart/SKILL.md then kickstart resume for project at $(pwd)"
+[runtime command] "Read ~/.config/mosaic/skills/kickstart/SKILL.md then kickstart resume for project at $(pwd)"
 
 State: docs/tasks.md (committed and pushed)
 Progress: X/Y tasks complete
@@ -339,4 +339,4 @@ Examples: "pnpm lint && pnpm typecheck && pnpm test"
 - This skill transforms the current session — after kickstart, the agent IS the orchestrator
 - The skill itself is just setup instructions — the orchestrator guide has the full execution protocol
 - For programmatic use: pass this skill file path to your active runtime and request kickstart for the target repo.
-- This skill is runtime-agnostic and expects Mosaic rails/guides at `~/.mosaic`.
+- This skill is runtime-agnostic and expects Mosaic rails/guides at `~/.config/mosaic`.