INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-2 — Remaining Parsers + Unified Convert
AGENT: core
SCOPE: packages/core/src/convert/ and packages/core/src/__tests__/

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 2.1: Tokens Studio parser ───
Parse Tokens Studio JSON format with composition token expansion and theme/set grouping.

Create packages/core/src/convert/tokens-studio.ts

Build a parser for Tokens Studio JSON format.
Key differences from Style Dictionary:
- Uses $extensions for metadata
- Has set/theme groupings at top level
- Supports composition tokens (typography = fontFamily + fontSize + lineHeight)

Export: parseTokensStudio(input: string | object): TokenCollection
Handle composition tokens by expanding into individual tokens.
Create __tests__/tokens-studio.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 2.1: Tokens Studio parser"

─── TASK 2.2: Tailwind config parser ───
Parse Tailwind CSS configuration objects (theme.extend.colors, theme.spacing, etc.).

Create packages/core/src/convert/tailwind.ts

Parse Tailwind CSS config objects (theme/theme.extend).
Handle: nested color scales (primary.50-900), rem-to-px conversion,
tuple format for fontSize, category mapping.

Export: parseTailwind(input: string | object): TokenCollection
Create __tests__/tailwind.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 2.2: Tailwind config parser"

─── TASK 2.3: CSS Variables parser ───
Parse CSS custom properties from a CSS file or :root block using css-tree.

Create packages/core/src/convert/css-variables.ts

Parse CSS custom properties using css-tree.
Extract --custom-property declarations, categorize by naming convention,
resolve var() references, handle fallback values.

Export: parseCssVariables(input: string): TokenCollection
Create __tests__/css-variables.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 2.3: CSS Variables parser"

─── TASK 2.4: Unified convert function ───
Single convert() entry point with auto-format detection routing to the correct parser.

Create packages/core/src/convert/index.ts

Build unified convert function with auto-format detection.
Routes to correct parser, converts to DesignSystem, generates DESIGN.md.

Export: convert(input: string, options?: ConvertOptions): Promise<ConvertResult>
Update src/index.ts barrel export.
Create __tests__/convert.test.ts integration tests.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 2.4: Unified convert function"

FINAL SELF-CHECK (run after the last task):
  cd packages/core && npx tsc --noEmit && npx vitest run

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-2.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-2 — Remaining Parsers + Unified Convert

    - **Section:** day-2
    - **Agent:** core
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-2.md
    git commit -m "status: day-2 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-3 — Validation Engine
AGENT: core
SCOPE: packages/core/src/validate/ and packages/core/src/__tests__/

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 3.1: Build validation engine with 8 rule categories ───
Core validation logic: parse HTML with cheerio, parse DESIGN.md, run 8 rule checks, collect violations.

Create packages/core/src/validate/engine.ts and rules.ts

8 Rule Categories:
1. COLOR_MATCH -- deltaE comparison via chroma-js (threshold: 5)
2. CONTRAST_CHECK -- WCAG 2.1 AA (4.5:1 normal, 3:1 large)
3. TYPOGRAPHY_MATCH -- font-family, size, weight, line-height
4. SPACING_MATCH -- margin/padding vs scale (2px tolerance)
5. RADIUS_MATCH -- border-radius vs tokens
6. TOUCH_TARGET -- 44x44px minimum for interactive elements
7. HEADING_ORDER -- h1 > h2 > h3, no skipping
8. GUIDELINE_VIOLATION -- general DESIGN.md guidelines

Export: validate(html: string, designMd: string): Promise<ValidationResult>
Create __tests__/validate.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 3.1: Build validation engine with 8 rule categories"

─── TASK 3.2: Grade calculator ───
Convert violation counts and severities into a letter grade (A through F). Start at 100, subtract: errors -5, warnings -2, info -0.5.

Create packages/core/src/validate/grader.ts

Scoring: Start at 100. Errors: -5, Warnings: -2, Info: -0.5.
Grades: A=90+, B=80+, C=70+, D=60+, F=below 60.
Generate human-readable summary string.

Export: calculateGrade(violations: Violation[]): { grade, score, summary }
Create __tests__/grader.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 3.2: Grade calculator"

FINAL SELF-CHECK (run after the last task):
  cd packages/core && npx tsc --noEmit && npx vitest run src/validate/

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-3.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-3 — Validation Engine

    - **Section:** day-3
    - **Agent:** core
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-3.md
    git commit -m "status: day-3 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-4 — Diff Engine + Full Test Suite
AGENT: core
SCOPE: packages/core/src/diff/ and packages/core/src/__tests__/

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 4.1: Build diff engine ───
Compare two DESIGN.md files section-by-section, detecting additions, removals, and changes with deltaE for color comparisons.

Create packages/core/src/diff/engine.ts and categories.ts

Compare two DESIGN.md files section-by-section.
Match tokens by name. Detect additions/removals/changes.
Use deltaE for color comparison, percentage for numeric values.

Export: diff(systemA: string, systemB: string): Promise<DiffResult>
Update src/index.ts. Create __tests__/diff.test.ts

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 4.1: Build diff engine"

─── TASK 4.2: Integration tests (full pipeline) ───
Create packages/core/src/__tests__/integration.test.ts

Full pipeline tests: convert (all 4 formats), validate (grade check), diff (change detection).
Cross-format equivalence test (same system, 4 formats, same output).

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 4.2: Integration tests (full pipeline)"

FINAL SELF-CHECK (run after the last task):
  cd packages/core && npx tsc --noEmit && npx vitest run --coverage

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-4.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-4 — Diff Engine + Full Test Suite

    - **Section:** day-4
    - **Agent:** core
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-4.md
    git commit -m "status: day-4 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-5 — MCP Server + CLI + API Routes
AGENT: mcpcli
SCOPE: packages/mcp-server/, packages/cli/, and apps/web/src/app/api/

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 5.1: Build MCP server (3 tools) ───
Create MCP server with convert_tokens, validate_html, diff_systems tools using the official SDK.

Create packages/mcp-server/src/index.ts

MCP server with 3 tools: convert_tokens, validate_html, diff_systems.
Uses McpServer + StdioServerTransport from @modelcontextprotocol/sdk.
Zod validation on all inputs. Calls @stitchwand/core.
Set up package.json with name @stitchwand/mcp, bin field for npx.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 5.1: Build MCP server (3 tools)"

─── TASK 5.2: Build CLI (3 commands) ───
Create CLI with convert, validate, and diff commands using commander.js and chalk.

Create packages/cli/ with 3 commands: convert, validate, diff.
Commander.js for arg parsing, chalk for colored output.
CI-friendly exit codes (0=pass, 1=fail).
Set up package.json with bin: { stitch: dist/index.js }

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 5.2: Build CLI (3 commands)"

─── TASK 5.3: Create API routes in apps/web ───
Add 3 POST API routes calling @stitchwand/core.

Create 3 POST API routes in apps/web/src/app/api/:
- /api/convert -- calls convert() from core
- /api/validate -- calls validate() from core
- /api/diff -- calls diff() from core
Zod input validation, proper error handling, JSON responses.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 5.3: Create API routes in apps/web"

FINAL SELF-CHECK (run after the last task):
  cd packages/mcp-server && npm run build && cd ../cli && npm run build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-5.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-5 — MCP Server + CLI + API Routes

    - **Section:** day-5
    - **Agent:** mcpcli
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-5.md
    git commit -m "status: day-5 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-6 — Wire Convert + DESIGN.md + Analyze Pages
AGENT: web
SCOPE: apps/web/src/app/(routes)/ and apps/web/src/components/ — do not edit packages/core, packages/mcp-server, packages/cli

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 6.1: Wire /convert to real API + file upload ───
Replace setTimeout with fetch('/api/convert'). FileReader API for drag-and-drop upload. Auto-detect format. Save conversion history to localStorage.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/convert/page.tsx and packages/core/src/convert.ts. Replace all setTimeout/mock calls with real fetch('/api/convert') calls. Add FileReader API for drag-and-drop file upload. Auto-detect input format (Style Dictionary, Tokens Studio, Tailwind, CSS Custom Props). Save conversion history to localStorage using a useLocalStorage hook with key 'sw-convert-history'. Create the /api/convert route handler that calls @stitchwand/core convert(). No mock data should remain.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.1: Wire /convert to real API + file upload"

─── TASK 6.2: Wire /design-md editor with real parsing + persistence ───
DESIGN.md editor: load/save files, parse to token model, live preview. Store recent files in localStorage. Validate on save. Export to supported formats.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/design-md/page.tsx and packages/core/src/index.ts. Wire the DESIGN.md editor to load/save real .md files. Parse DESIGN.md content to the token model using @stitchwand/core. Add live preview that updates as user edits. Store recent files list in localStorage with key 'sw-designmd-recent'. Validate DESIGN.md on save and show errors inline. Add export buttons for all supported formats (Style Dictionary, Tokens Studio, Tailwind, CSS). All data must persist across page refreshes.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.2: Wire /design-md editor with real parsing + persistence"

─── TASK 6.3: Wire /analyze Validate tab to /api/validate ───
Real grades, violations, scores. File upload for HTML + DESIGN.md. Save validation results to localStorage for history.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/analyze/page.tsx and packages/core/src/validate.ts. Wire the Validate tab to call /api/validate with real file uploads. Create the route handler that calls @stitchwand/core validate(). Display real grades, violation lists with severity levels, and overall scores. Add drag-and-drop file upload for HTML + DESIGN.md files. Save validation results to localStorage with key 'sw-validate-history' for history view. Replace all mock/demo data with real validation output.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.3: Wire /analyze Validate tab to /api/validate"

─── TASK 6.4: Wire /analyze Diff tab to /api/diff ───
Real additions/removals/changes. File upload for two DESIGN.md files. Save diff snapshots to localStorage.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/analyze/page.tsx and packages/core/src/diff.ts. Wire the Diff tab to call /api/diff with two DESIGN.md file uploads. Create the route handler that calls @stitchwand/core diff(). Display real additions, removals, and changes with color-coded diff view (green for added, red for removed, amber for changed). Save diff snapshots to localStorage with key 'sw-diff-history'. Add side-by-side comparison view. Replace all mock data.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.4: Wire /analyze Diff tab to /api/diff"

─── TASK 6.5: Wire /analyze A11y + Lint tabs ───
A11y linter with WCAG rule checking. Lint tab for token naming conventions. Both persist results to localStorage.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/analyze/page.tsx. Wire the Accessibility tab to run WCAG contrast ratio checks, touch target sizing, and focus indicator validation against uploaded DESIGN.md tokens. Wire the Lint tab to check token naming conventions (camelCase, kebab-case consistency), detect unused tokens, and flag circular references. Both tabs persist results to localStorage with keys 'sw-a11y-history' and 'sw-lint-history'. Create /api/a11y and /api/lint route handlers using @stitchwand/core.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.5: Wire /analyze A11y + Lint tabs"

─── TASK 6.6: End-to-end test Convert + DESIGN.md + Analyze ───
Upload real token files, edit DESIGN.md, validate output, diff two versions. All pages work with real data. No setTimeout calls remain.

Run in web agent worktree (../stitchwand-agent-web).

Write Vitest integration tests for the Convert, DESIGN.md, and Analyze pages. Test real file uploads with sample token files (Style Dictionary JSON, Tailwind config). Test DESIGN.md editing, saving, and format export. Test Validate with real HTML + DESIGN.md producing real grades. Test Diff with two DESIGN.md versions showing real changes. Verify NO setTimeout calls remain in any of these pages: grep -r 'setTimeout' apps/web/src/app/(app)/convert apps/web/src/app/(app)/design-md apps/web/src/app/(app)/analyze. Run: npx vitest run --reporter=verbose

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 6.6: End-to-end test Convert + DESIGN.md + Analyze"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-6.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-6 — Wire Convert + DESIGN.md + Analyze

    - **Section:** day-6
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-6.md
    git commit -m "status: day-6 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-7 — Wire Prompt Library + Components
AGENT: web
SCOPE: apps/web/src/app/(routes)/ and apps/web/src/components/ — do not edit packages/core, packages/mcp-server, packages/cli

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 7.1: Prompt Library: data model + storage ───
Define PromptTemplate type (id, name, category, content, variables, createdAt, updatedAt). useLocalStorage hook for CRUD. Seed with 10+ Stitch prompt templates.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/prompts/page.tsx. Define a PromptTemplate TypeScript type with fields: id (string), name (string), category (string), content (string), variables (string[]), createdAt (ISO string), updatedAt (ISO string). Create a usePromptStorage hook using localStorage with key 'sw-prompts'. Implement CRUD operations (create, read, update, delete). Seed with 10+ Stitch-specific prompt templates covering: color palette generation, typography scale, spacing system, component scaffolding, accessibility audit, token conversion, brand voice, layout patterns, responsive breakpoints, dark mode tokens. Use strict TypeScript — no any.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.1: Prompt Library: data model + storage"

─── TASK 7.2: Prompt Library: full UI wiring ───
Create, edit, duplicate, delete prompts. Variable interpolation preview. Category filtering. Search. Copy-to-clipboard. All actions persist to localStorage.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/prompts/page.tsx. Wire the UI to the usePromptStorage hook. Implement: create new prompt with name/category/content fields, edit existing prompts inline, duplicate prompt, delete with confirmation dialog. Add variable interpolation — detect {{variableName}} patterns in content and show input fields for each variable with live preview. Add category filter dropdown and text search. Copy-to-clipboard button on each prompt output. All actions must persist to localStorage immediately. No mock data.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.2: Prompt Library: full UI wiring"

─── TASK 7.3: Components: data model + storage ───
Define ComponentEntry type (id, name, category, html, designMdRef, props, variants, createdAt). useLocalStorage for CRUD. Seed with example components (Button, Card, Input, Modal).

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/components/page.tsx. Define a ComponentEntry TypeScript type with fields: id (string), name (string), category (string), html (string), css (string), designMdRef (string | null), props (Record<string, string>), variants (Array<{name: string, overrides: Record<string, string>}>), createdAt (ISO string). Create a useComponentStorage hook using localStorage with key 'sw-components'. Implement CRUD operations. Seed with example components: Button (primary, secondary, ghost variants), Card, Input, Modal, Badge, Avatar.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.3: Components: data model + storage"

─── TASK 7.4: Components: full UI wiring ───
Component browser with live preview. Create from DESIGN.md tokens. Variant switcher. Props editor. Code export (HTML, React, Tailwind). All persist to localStorage.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/components/page.tsx. Wire the component browser UI to useComponentStorage. Add live preview iframe that renders component HTML + CSS. Create component form with HTML/CSS code editors. Variant switcher — select variant to see different styles applied. Props editor — edit prop values and see preview update in real time. Code export in 3 formats: raw HTML, React JSX, Tailwind utility classes. All CRUD operations persist to localStorage. Add category filter and search.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.4: Components: full UI wiring"

─── TASK 7.5: Wire Components to @stitchwand/core token resolution ───
Components reference tokens from loaded DESIGN.md. Changing tokens updates component previews. Validate components against their design system.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/components/page.tsx and packages/core/src/index.ts. Wire component previews to resolve design tokens from a loaded DESIGN.md file. When a user loads a DESIGN.md, extract tokens and inject them as CSS custom properties into component preview iframes. Changing a token value in DESIGN.md should update all component previews that reference it. Add a 'Validate' button that checks components against their design system tokens using @stitchwand/core validate().

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.5: Wire Components to @stitchwand/core token resolution"

─── TASK 7.6: End-to-end test Prompt Library + Components ───
Create prompts, use variables, copy output. Create components, switch variants, export code. Refresh page — all data persists.

Run in web agent worktree (../stitchwand-agent-web).

Write Vitest integration tests for Prompt Library and Components pages. Test: create a prompt with {{variables}}, fill variable values, copy interpolated output. Create a component with variants, switch between variants, export as React JSX. Test localStorage persistence — save data, simulate page refresh, verify data loads correctly. Verify seeded templates and components are present on first load. Run: npx vitest run --reporter=verbose

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 7.6: End-to-end test Prompt Library + Components"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-7.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-7 — Wire Prompt Library + Components

    - **Section:** day-7
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-7.md
    git commit -m "status: day-7 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-8 — Wire Starter Kits + Design Swarm + Doc Writer
AGENT: web
SCOPE: apps/web/src/app/(routes)/ and apps/web/src/components/ — do not edit packages/core, packages/mcp-server, packages/cli

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 8.1: Starter Kits: data permanence + real generation ───
SavedKit type persists to localStorage. Wizard generates real Stitch prompts + DESIGN.md from user input (brand, colors, typography, style). Export generated files. Kit history with edit/duplicate/delete.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/components/manifest/manifest-page.tsx. Define SavedKit type with: id, name, brandName, colors (Record<string, string>), typography ({heading: string, body: string, mono: string}), style (string), generatedPrompts (string[]), generatedDesignMd (string), createdAt, updatedAt. Create useKitStorage hook with localStorage key 'sw-kits'. Wire the wizard to generate real Stitch prompts and DESIGN.md content from user input. Add export buttons for generated files. Kit history with edit, duplicate, delete. All data persists across refreshes.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.1: Starter Kits: data permanence + real generation"

─── TASK 8.2: Design Swarm: data model + storage ───
Define SwarmSession type (id, name, agents[], messages[], designMdOutput, status, createdAt). useLocalStorage for CRUD. Multi-agent orchestration UI with real conversation flow.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/swarm/page.tsx. Define SwarmSession type with: id (string), name (string), agents (Array<{role: string, specialty: string, color: string}>), messages (Array<{agentId: string, content: string, timestamp: string}>), designMdOutput (string), status ('active' | 'completed' | 'paused'), createdAt (ISO string). Create useSwarmStorage hook with localStorage key 'sw-swarms'. Implement CRUD. Define agent roles: Color Specialist, Typography Expert, Layout Architect, Accessibility Auditor, Brand Strategist.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.2: Design Swarm: data model + storage"

─── TASK 8.3: Design Swarm: full UI wiring ───
Create swarm sessions. Configure agents (color, typography, layout specialists). Run swarm to generate DESIGN.md collaboratively. View conversation history. Save/load sessions. Export results.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/swarm/page.tsx. Wire the UI to useSwarmStorage. Create swarm session with name and agent selection checkboxes. Show agent conversation as a chat-like timeline with colored agent avatars and role labels. Each agent 'contributes' to building a DESIGN.md collaboratively. View conversation history for completed sessions. Save/load sessions from localStorage. Export final DESIGN.md output as downloadable file. Duplicate and restart sessions. Session list sidebar with status badges (active, completed, paused).

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.3: Design Swarm: full UI wiring"

─── TASK 8.4: Doc Writer: data model + storage ───
Define Document type (id, name, docType, content, designMdRef, createdAt, updatedAt). useLocalStorage for CRUD. Support multiple doc types: README, CONTRIBUTING, API docs, changelog.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/doc-writer/page.tsx. Define Document TypeScript type with: id (string), name (string), docType ('readme' | 'contributing' | 'api' | 'changelog' | 'custom'), content (string), designMdRef (string | null), createdAt (ISO string), updatedAt (ISO string). Create useDocStorage hook with localStorage key 'sw-docs'. Implement CRUD operations. Seed with template starters for each doc type with placeholder content that references DESIGN.md token patterns.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.4: Doc Writer: data model + storage"

─── TASK 8.5: Doc Writer: full UI wiring ───
Generate docs from DESIGN.md context. Markdown editor with live preview. Template library. Export as .md files. Document management (create, edit, delete, duplicate).

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/doc-writer/page.tsx. Wire the UI to useDocStorage. Generate documentation content informed by loaded DESIGN.md context (token names, color values, typography scale). Build a markdown editor with live preview pane using a split-view layout. Template library with quick-start options for each doc type. Export as .md file download. Document management: create, edit, delete, duplicate from sidebar list. Auto-save on edit with debounce (500ms). All data persists to localStorage.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.5: Doc Writer: full UI wiring"

─── TASK 8.6: Dashboard: update quick actions for all shipping features ───
Dashboard shows quick action cards for all Core + Advanced features. Recent activity feed pulls from localStorage history across all tools.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/page.tsx (dashboard/home page). Update quick action cards to link to all Core + Advanced features: DESIGN.md, Prompt Library, Token Studio (Convert), Components, Analyze, Starter Kits, Design Swarm, Doc Writer. Add a recent activity feed that reads latest items from localStorage across all tools (sw-convert-history, sw-prompts, sw-components, sw-kits, sw-swarms, sw-docs). Show item counts and last-modified timestamps for each tool. Use the same icon set from sidebar.tsx.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.6: Dashboard: update quick actions for all shipping features"

─── TASK 8.7: End-to-end test Starter Kits + Design Swarm + Doc Writer ───
Create Starter Kit, run design swarm, generate docs. Refresh page — all data persists. Cross-feature flow: kit → swarm → doc generation.

Run in web agent worktree (../stitchwand-agent-web).

Write Vitest integration tests for Starter Kits, Design Swarm, and Doc Writer. Test cross-feature flow: create a Starter Kit with brand settings, use generated DESIGN.md in a swarm session, generate documentation from swarm output. Test each page independently: create/save/load/delete items, export files. Verify localStorage persistence — save data, refresh, verify it loads. Run: npx vitest run --reporter=verbose

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 8.7: End-to-end test Starter Kits + Design Swarm + Doc Writer"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-8.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-8 — Wire Starter Kits + Design Swarm

    - **Section:** day-8
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-8.md
    git commit -m "status: day-8 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-9A — UI Polish + Voice Removal + Labs Gating
AGENT: web
SCOPE: apps/web/src/ — do not edit packages/core, packages/mcp-server, packages/cli

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 9a.1: Remove Voice Studio from codebase ───
Delete voice-studio route directory. Remove from sidebar nav, command palette, labs registry, and demo data. Complete removal — no traces.

Run in web agent worktree (../stitchwand-agent-web).

Find and remove all Voice Studio code. Delete apps/web/src/app/(app)/voice-studio/ directory. Remove the Voice Studio entry from apps/web/src/lib/labs-registry.ts. Search for any references to 'voice' or 'Voice Studio' in sidebar.tsx, command palette, demo data, and settings pages. Remove all traces completely. Run TypeScript compiler to verify no broken imports: npx tsc --noEmit

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 9a.1: Remove Voice Studio from codebase"

─── TASK 9a.2: Gate Labs features behind feature flags ───
Labs features only appear in sidebar when enabled in Settings > Labs. Each has a toggle with description. localStorage-backed.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/hooks/use-labs.ts and apps/web/src/lib/labs-registry.ts. Verify that Labs features only appear in the sidebar when individually enabled in Settings > Labs. Each lab feature should have a toggle with its name and description from the registry. Feature state stored in localStorage. Disabled labs routes should show a 'Feature not enabled — enable in Settings > Labs' page instead of 404. Test: disable a lab, verify hidden from sidebar, navigate to its URL directly to see gating message.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 9a.2: Gate Labs features behind feature flags"

─── TASK 9a.3: Settings: data management + export/import ───
Settings page with data management section. Export all localStorage data as JSON. Import from JSON backup. Clear all data. Storage usage display.

Run in web agent worktree (../stitchwand-agent-web).

Read apps/web/src/app/(app)/settings/page.tsx. Add a 'Data Management' section with: Export All Data button (downloads all localStorage keys with 'sw-' prefix as a single JSON file), Import Data button (file upload that merges or replaces localStorage data from JSON backup), Clear All Data button with confirmation dialog, Storage Usage display showing bytes used per feature (prompts, components, kits, swarms, docs, settings). Test the full export > clear > import round-trip to verify data integrity.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 9a.3: Settings: data management + export/import"

─── TASK 9a.4: Full app smoke test — all Core + Advanced pages ───
Test every Core + Advanced feature end-to-end: DESIGN.md, Convert, Analyze, Components, Prompt Library, Starter Kits, Design Swarm, Doc Writer. All use real data, all persist, no setTimeout calls remain.

Run in web agent worktree (../stitchwand-agent-web).

Run a full smoke test of every Core + Advanced feature. Open each page and verify:
1) DESIGN.md — load, edit, save, export
2) Convert — upload file, convert, view result
3) Analyze — validate, diff, a11y, lint with real files
4) Prompt Library — create, edit, use variables, copy
5) Components — create, preview, switch variants, export
6) Starter Kits — run wizard, save kit, load saved kit
7) Design Swarm — create session, view agents, export
8) Doc Writer — create doc, edit, export
Verify NO setTimeout mock calls remain: grep -r 'setTimeout' apps/web/src/
All data persists on page refresh.

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 9a.4: Full app smoke test — all Core + Advanced pages"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-9a.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-9a — UI Polish + Voice Removal + Labs

    - **Section:** day-9a
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-9a.md
    git commit -m "status: day-9a section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: ACTION-ANALYTICS — Analytics & Admin Panel
AGENT: web
SCOPE: apps/web/src/ — analytics lib, admin routes, admin panels, page instrumentation. Do NOT edit packages/core, packages/mcp-server, packages/cli.

This section now runs pre-launch. Some tasks may already be implemented by prior commits (see git log for "Analytics system" commit). CHECK FIRST before building.

READ FIRST:
- CLAUDE.md in repo root
- apps/web/AGENTS.md if it exists
- The files you will modify, to understand current state

IMPORTANT — CHECK BEFORE YOU BUILD:
  For every task below, first grep/read the codebase to check if the work is already done.
  If it is already implemented, SKIP the task, note "already done" in the status report, and move on.
  Only implement the tasks that are actually missing.

TASK LIST — execute each task in order, commit after each (unless skipping):

─── TASK 12.1: GA4 integration (gtag.js loader + pageview tracking) ───
Add Google Analytics 4 via gtag.js script loader. Automatic pageview tracking on route changes.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.1: GA4 integration (gtag.js loader + pageview tracking)"

─── TASK 12.2: Custom analytics engine (localStorage event tracking, session management, flow recording) ───
Built-in analytics engine using localStorage for event tracking, session management with unique IDs, and user flow recording across pages.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.2: Custom analytics engine (localStorage event tracking, session management, flow recording)"

─── TASK 12.3: Analytics provider component (auto page views) ───
React context provider that wraps the app and automatically tracks page views on route changes.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.3: Analytics provider component (auto page views)"

─── TASK 12.4: Analytics tracker component (mounted in app shell) ───
Tracker component mounted in the root app shell that initializes analytics and manages the tracking lifecycle.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.4: Analytics tracker component (mounted in app shell)"

─── TASK 12.5: Admin auth system (password-protected, sessionStorage) ───
Password-based admin authentication using sessionStorage for session persistence. Separate from future Auth0 user auth.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.5: Admin auth system (password-protected, sessionStorage)"

─── TASK 12.6: Admin gate component (password modal) ───
Modal component that gates admin routes behind password entry. Clean UI with error handling.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.6: Admin gate component (password modal)"

─── TASK 12.7: Admin route (/admin) ───
Protected /admin route with password gate. Only accessible to authenticated admin users.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.7: Admin route (/admin)"

─── TASK 12.8: Admin dashboard with tabbed layout ───
Tabbed admin dashboard with multiple analytics panels. Clean navigation between overview, flows, prompts, and feature usage.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.8: Admin dashboard with tabbed layout"

─── TASK 12.9: Overview panel (KPIs, top pages, recent events, time range filter) ───
Key performance indicators, top pages by visits, recent event stream, and time range filtering (24h, 7d, 30d, all).

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.9: Overview panel (KPIs, top pages, recent events, time range filter)"

─── TASK 12.10: User flows panel (visual flow map with @xyflow/react, session timelines) ───
Visual flow map showing user navigation patterns using @xyflow/react. Session timelines with page-by-page breakdown.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.10: User flows panel (visual flow map with @xyflow/react, session timelines)"

─── TASK 12.11: Prompt analytics panel (most used prompts, action breakdown, activity timeline) ───
Track prompt usage: most used prompts ranked, action type breakdown (copy, create, edit, delete), activity timeline chart.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.11: Prompt analytics panel (most used prompts, action breakdown, activity timeline)"

─── TASK 12.12: Feature usage panel (core vs labs, feature ranking, lab toggles) ───
Feature usage analytics: core vs labs usage split, feature ranking by engagement, lab toggle tracking.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.12: Feature usage panel (core vs labs, feature ranking, lab toggles)"

─── TASK 12.13: Admin in user menu, topbar, command palette ───
Admin link accessible from user dropdown menu, topbar navigation, and command palette (Cmd+K) for quick access.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.13: Admin in user menu, topbar, command palette"

─── TASK 12.14: Page instrumentation (prompts, convert, components, magic kits, labs) ───
Event tracking instrumented across core pages: prompt actions, conversion events, component interactions, kit generation, and lab feature usage.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.14: Page instrumentation (prompts, convert, components, magic kits, labs)"

─── TASK 12.15: Set up GA4 Measurement ID in production environment ───
Configure GA4 Measurement ID environment variable for production deployment. Verify data flowing to Google Analytics dashboard.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.15: Set up GA4 Measurement ID in production environment"

─── TASK 12.16: Add more granular event tracking across remaining pages ───
Extend event tracking to remaining pages: DESIGN.md editor actions, analyze/validate/diff/lint operations, design swarm sessions, doc writer exports, settings changes.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.16: Add more granular event tracking across remaining pages"

─── TASK 12.17: DESIGN.md Merge upload modal with staged files ───
Upload modal with staged file list, staggered animation, remove buttons, save-to-library checkbox, and "Add to Merge" submit flow. "v" keyboard shortcut for demo files.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.17: DESIGN.md Merge upload modal with staged files"

─── TASK 12.18: Library deduplication fix ───
Prevent duplicate files in DESIGN.md library when saving from upload modal. Default saveToLibrary to false for demo shortcut.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.18: Library deduplication fix"

─── TASK 12.19: Starter Kits color picker layout — collapsible DESIGN.md list ───
Limit "FROM DESIGN.MD" theme list to 8 items with "+N more" toggle to prevent layout overflow from 99 design systems.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.19: Starter Kits color picker layout — collapsible DESIGN.md list"

─── TASK 12.20: Output display tab reorder (DESIGN.md first, Stitch Prompt last) ───
Reorder Generated Output tabs: DESIGN.md → Preview → Stitch Prompt. Default to DESIGN.md tab.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.20: Output display tab reorder (DESIGN.md first, Stitch Prompt last)"

─── TASK 12.21: Modal centering with sidebar offset ───
Fix modal centering across all modals (prompts, upload, save) with pl-[260px] offset to account for sidebar width.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.21: Modal centering with sidebar offset"

─── TASK 12.22: Light mode modal fix — solid background ───
Fix translucent modal in light mode by using bg-bg instead of bg-background for proper Tailwind v4 theme variable resolution.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.22: Light mode modal fix — solid background"

─── TASK 12.23: Auto-infer tags for all saved kits ───
Auto-generate tags from DESIGN.md content when kit has no tags. Uses keyword matching for design-system, dark-mode, enterprise, etc.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.23: Auto-infer tags for all saved kits"

─── TASK 12.24: Gallery cards — hero abstract UI + external link ───
Redesign Starter Kits Gallery cards with abstract UI mockup hero image using design system palette (darkest=bg, brand=primary, lightest=text). Added ExternalLink icon next to version opening design system documentation site in new tab.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.24: Gallery cards — hero abstract UI + external link"

─── TASK 12.25: My Kits cards — hero abstract UI with smart color picking ───
Hero preview uses pickHeroColors() to choose darkest color for background, brand color for accents, lightest for text — works correctly across all palette types.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.25: My Kits cards — hero abstract UI with smart color picking"

─── TASK 12.26: Kit naming convention — "X Kit" for duplicated kits ───
Changed gallery duplicate naming from "Copy of X" to "X Kit" to distinguish kits from design system source files.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.26: Kit naming convention — 'X Kit' for duplicated kits"

─── TASK 12.27: DESIGN.md Library — card/list view toggle ───
Added LayoutGrid/List toggle in Library toolbar. List view shows compact rows with color dots, name, version, token count, status, and date columns.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.27: DESIGN.md Library — card/list view toggle"

─── TASK 12.28: Fix console errors — script tag + hydration mismatch ───
Moved theme init script from <head> to <body> to fix React script rendering error. Added mounted guard to savedKits count badge to fix hydration mismatch from localStorage.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.28: Fix console errors — script tag + hydration mismatch"

─── TASK 12.29: Placeholder text contrast improvement ───
Made placeholder/hint text in Starter Kits inputs darker — changed from text-text-4/30 to text-text-3/50 for better readability in both dark and light mode.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.29: Placeholder text contrast improvement"

─── TASK 12.30: Rename "Magic Kits" to "Starter Kits" everywhere ───
Renamed across all UI (sidebar, topbar, manifest page, home page, admin panels), generate-output.ts, all docs (project-plan, pitch, demo, go-to-market, videos, index, OVERVIEW.md). Gallery cards display "X Kit" suffix (e.g., "Stripe Design Kit").

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.30: Rename 'Magic Kits' to 'Starter Kits' everywhere"

─── TASK 12.31: Sidebar renames: Prompt Library & Token Studio ───
Renamed sidebar items: "Prompt Tools" -> "Prompt Library", "Tokens" -> "Token Studio" for clearer feature identity.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.31: Sidebar renames: Prompt Library & Token Studio"

─── TASK 12.32: Activity Graph auto-seeding (500 prompts + 200 analytics) ───
Dashboard auto-seeds 500 prompt entries and 200 analytics events spanning a full year on first visit. Uses seeded pseudo-random for stable demo data. Denser activity toward recent dates.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.32: Activity Graph auto-seeding (500 prompts + 200 analytics)"

─── TASK 12.33: Free/Pro tier switch in user menu ───
User menu now has a Free/Pro toggle for demo and admin testing. Improved tab styling with better padding, borders, and visual weight.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.33: Free/Pro tier switch in user menu"

─── TASK 12.34: Advanced tools gating for Free tier ───
Free accounts see Starter Kits, Design Swarm, and Documents as locked with lock icons and "Pro" badge in the sidebar. Pro accounts have full access.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.34: Advanced tools gating for Free tier"

─── TASK 12.35: Animated demo fill ('v' shortcut) ───
The 'v' key demo shortcut now types words one at a time with sparkle effects and glow on the textarea, then fills colors, font, tags, and URLs with staggered transitions. Much more impressive for demos.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.35: Animated demo fill ('v' shortcut)"

─── TASK 12.36: 99 community design systems ───
Community design systems file expanded from 70 to 99 entries. Starter Kit header now sticky with backdrop blur on scroll, description widened from max-w-lg to max-w-2xl, progress bar stays visible with shrink-0.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.36: 99 community design systems"

─── TASK 12.37: Starter Kit description rewrite ───
Rewritten to be concise and confident: "Your complete design kit: tokens, palettes, typography, spacing, components, and a Stitch-ready prompt. Tell us about your project and we build the system."

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task 12.37: Starter Kit description rewrite"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/action-analytics.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # action-analytics — Analytics & Admin Panel

    - **Section:** action-analytics
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] <task-id> — <task-name> — SKIPPED (already done: <reason>)

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/action-analytics.md
    git commit -m "status: action-analytics section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.

NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message (unless the task was skipped).
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: ACTION-ONBOARDING — Onboarding & Demo Data Production
AGENT: web
SCOPE: apps/web/src/app/app/page.tsx, onboarding.tsx, manifest-page.tsx, and related UI. Do NOT edit packages/core, packages/mcp-server, packages/cli.

This section must land before launch so first-time real users get a clean, honest onboarding (no seeded demo data, no fake Figma connection, no hardcoded 9 tools, no sample kits mixed into user gallery).

READ FIRST:
- CLAUDE.md in repo root
- apps/web/AGENTS.md if it exists
- The files you will modify, to understand current state

IMPORTANT — CHECK BEFORE YOU BUILD:
  For every task below, first grep/read the codebase to check if the work is already done.
  If it is already implemented, SKIP the task, note "already done" in the status report, and move on.
  Only implement the tasks that are actually missing.

TASK LIST — execute each task in order, commit after each (unless skipping):

─── TASK OB.1: Gate `seedDemoData()` behind demo mode only ───
In `apps/web/src/app/app/page.tsx`, the `seedDemoData()` function auto-generates 500 fake prompt history entries + 200 fake analytics events on first visit. This makes every new user see a year of fake activity in the heatmap. Fix: Only run `seedDemoData()` when demo mode is active (check `localStorage.getItem('sw:demo-mode') === '1'` or similar flag). Real users see an empty "No prompts yet — try the Prompt Library" state with a link to `/prompts`. Design a clean empty state for the activity graph (subtle grid with "Start building" CTA).

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.1: Gate `seedDemoData()` behind demo mode only"

─── TASK OB.2: Fix onboarding modal fake Figma connection ───
In `onboarding.tsx` step 1 (Figma path), clicking "Connect Figma" fakes a 1500ms delay then shows hardcoded "Acme Design Team" with "3 projects found." Since real Figma OAuth isn't ready, fix: Change to "Connect Later" flow — show "Figma integration coming soon" with option to skip. Or remove the fake success entirely and just collect the preference (user came from Figma vs Code) without pretending a connection happened. Keep the path selection (Figma vs Code) — it's useful for segmentation.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.2: Fix onboarding modal fake Figma connection"

─── TASK OB.3: Make "9 tools configured" count dynamic ───
In `onboarding.tsx` step 2 completion screen, "9 tools configured" is hardcoded. Fix: Count actual tools available based on tier. Free = 6 core tools, Pro = 6 core + 3 advanced = 9, Labs features count separately. Use `useTier()` hook to determine count. Show: "N tools ready" where N is computed.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.3: Make '9 tools configured' count dynamic"

─── TASK OB.4: Separate SAMPLE_KITS from user gallery ───
In `manifest-page.tsx`, 25 hardcoded SAMPLE_KITS appear alongside user's saved kits in the gallery. New users see 25 kits they didn't create. Fix: Show SAMPLE_KITS in a separate "Inspiration" or "Templates" tab/section with a clear "Example" badge on each. User's "My Kits" tab shows only their real kits (or empty state). The code already filters by `!k.id.startsWith("sk-")` — leverage this to split the views cleanly.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.4: Separate SAMPLE_KITS from user gallery"

─── TASK OB.5: Add empty states for all first-visit screens ───
After removing seeded data, these screens need empty states: (1) Dashboard activity graph — subtle grid with "No activity yet" + CTA, (2) Dashboard history sidebar — "Your prompt history will appear here", (3) Starter Kits "My Kits" — "Create your first kit" with arrow to Create tab, (4) Overview page activity graph — same empty grid. Each empty state should guide users to the right tool. Use consistent pattern: illustration + message + action button.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.5: Add empty states for all first-visit screens"

─── TASK OB.6: Add admin demo mode toggle ───
Add a toggle in Settings (or admin panel) to enable demo mode: sets `localStorage.setItem('sw:demo-mode', '1')`. When active, `seedDemoData()` runs and the "v" key demo shortcuts work. When off, users see real data only. This preserves the demo capability for conference presentations while keeping the product honest for real users. Show a small "DEMO" badge in the nav when active.

Implementation approach:
  - First, grep/read to check if the task is already done. If yes: skip, note it, move on.
  - Keep the change focused and minimal. Do not touch unrelated code.
  - Use existing patterns in the codebase — search for similar implementations first.
  - Run the dev server (port 3333) and manually verify in the browser if the change is visible.

Self-check for this task:
  1) Re-read the files you changed.
  2) cd apps/web && npx tsc --noEmit
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task OB.6: Add admin demo mode toggle"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/action-onboarding.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # action-onboarding — Onboarding & Demo Data Production

    - **Section:** action-onboarding
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] <task-id> — <task-name> — SKIPPED (already done: <reason>)

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/action-onboarding.md
    git commit -m "status: action-onboarding section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.

NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message (unless the task was skipped).
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: DAY-9 — Deploy + Publish
AGENT: all
SCOPE: apps/web/ (Vercel deploy, analytics), packages/*/ (npm publish), packages/mcp-server/ (registry listings)

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK 9.1: Deploy web app to Vercel + connect stitchwand.com (Hover) ───
Deploy production build to Vercel. Add stitchwand.com as custom domain. Configure Hover DNS: A record → 76.76.21.21, CNAME www → cname.vercel-dns.com. Verify SSL.

Run: cd apps/web && vercel --prod
Run: vercel domains add stitchwand.com
Print DNS records for Hover configuration.
Verify deployment is live.

Self-check for this task:
  1) Verify Vercel deployment URL returns 200.
  2) Print DNS records needed for Hover.
  3) git add -p && git commit -m "task 9.1: Deploy web app to Vercel"

─── TASK 9.2: Publish @stitchwand/core to npm ───
Build and publish the core package.

1. Verify packages/core/package.json has correct name, version, main, types, files fields.
2. Run: cd packages/core && npm run build
3. Dry run: npm publish --dry-run
4. Publish: npm publish --access public
5. Verify: npm view @stitchwand/core

Self-check for this task:
  1) npm view @stitchwand/core returns package info.
  2) git add -p && git commit -m "task 9.2: Publish @stitchwand/core to npm"

─── TASK 9.3: Publish @stitchwand/mcp-server to npm ───
Build and publish the MCP server package with bin field for npx execution.

1. Verify packages/mcp-server/package.json fields.
2. Run: cd packages/mcp-server && npm run build
3. Dry run: npm publish --dry-run
4. Publish: npm publish --access public
5. Test: npx @stitchwand/mcp-server --help

Self-check for this task:
  1) npm view @stitchwand/mcp-server returns package info.
  2) git add -p && git commit -m "task 9.3: Publish @stitchwand/mcp-server to npm"

─── TASK 9.4: Publish @stitchwand/cli to npm ───
Build and publish the CLI package. Verify bin maps stitchwand command.

1. Verify packages/cli/package.json fields.
2. Run: cd packages/cli && npm run build
3. Dry run: npm publish --dry-run
4. Publish: npm publish --access public
5. Test: npx @stitchwand/cli convert --help

Self-check for this task:
  1) npm view @stitchwand/cli returns package info.
  2) git add -p && git commit -m "task 9.4: Publish @stitchwand/cli to npm"

─── TASK 9.5: List MCP server on Smithery ───
Create smithery.yaml config in packages/mcp-server/. Include all MCP tool names and descriptions. Print Smithery submit URL.

Self-check for this task:
  1) Re-read smithery.yaml. Verify tool list matches server.ts.
  2) git add -p && git commit -m "task 9.5: Add Smithery config for MCP registry"

─── TASK 9.6: List on Glama + mcp.run + official MCP registry ───
Create any needed config files for Glama, mcp.run, and the official MCP registry. Print submission instructions for each.

Self-check for this task:
  1) Re-read config files created.
  2) git add -p && git commit -m "task 9.6: Add MCP registry configs"

─── TASK 9.7: Push repo to GitHub (private) ───
Create private GitHub repo, set description and homepage, add topics.

1. gh repo create stitchwand/stitchwand --private --source=. --push
2. gh repo edit --description "Design token toolchain for Google Stitch and DESIGN.md" --homepage "https://stitchwand.com"
3. gh repo edit --add-topic design-tokens,design-systems,google-stitch,mcp,design-md
4. gh repo view

Self-check for this task:
  1) gh repo view shows correct metadata.
  2) git add -p && git commit -m "task 9.7: Push repo to GitHub"

─── TASK 9.8: Add Plausible analytics ───
Add Plausible script to apps/web/src/app/layout.tsx. Production only. Use next/script with strategy="afterInteractive".

Self-check for this task:
  1) Re-read layout.tsx — verify script is present and production-gated.
  2) Run typecheck: cd apps/web && npx tsc --noEmit
  3) Verify dev server on port 3333 still works.
  4) git add -p && git commit -m "task 9.8: Add Plausible analytics"

─── TASK 9.9: Create Stitch Skill PR for google-labs-code/stitch-skills ───
Create skills/convert-to-design-md/ directory with SKILL.md, scripts/convert.ts, resources/format-guide.md, and examples/. Print fork + PR commands.

Self-check for this task:
  1) Re-read all files in skills/convert-to-design-md/.
  2) Verify SKILL.md follows Mission Control format.
  3) git add -p && git commit -m "task 9.9: Create Stitch Skill for stitch-skills repo"

FINAL SELF-CHECK (run after the last task):
  Verify all packages built successfully and all config files are valid.

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/day-9.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # day-9 — Deploy + Publish

    - **Section:** day-9
    - **Agent:** all
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/day-9.md
    git commit -m "status: day-9 section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: ACTION-AGENTS — Multi-Agent System
AGENT: coord
SCOPE: .claude/agents/, AGENTS.md files, docs/agents.html — do not touch production code paths

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK agent-1: Create git worktree for Core Engine agent ───
git worktree add ../stitchwand-agent-core -b agent/core. Isolated branch for packages/core development.

Create a git worktree for the Core Engine agent:
git worktree add ../stitchwand-agent-core -b agent/core

This agent owns packages/core exclusively. Verify the worktree is working by running: cd ../stitchwand-agent-core && ls packages/core

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-1: Create git worktree for Core Engine agent"

─── TASK agent-2: Create git worktree for MCP + CLI agent ───
git worktree add ../stitchwand-agent-mcp -b agent/mcp-cli. Isolated branch for packages/mcp-server and packages/cli.

Create a git worktree for the MCP + CLI agent:
git worktree add ../stitchwand-agent-mcp -b agent/mcp-cli

This agent owns packages/mcp-server and packages/cli. Verify: cd ../stitchwand-agent-mcp && ls packages/mcp-server packages/cli

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-2: Create git worktree for MCP + CLI agent"

─── TASK agent-3: Create git worktree for Web App agent ───
git worktree add ../stitchwand-agent-web -b agent/web-app. Isolated branch for apps/web development.

Create a git worktree for the Web App agent:
git worktree add ../stitchwand-agent-web -b agent/web-app

This agent owns apps/web exclusively. Verify: cd ../stitchwand-agent-web && ls apps/web

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-3: Create git worktree for Web App agent"

─── TASK agent-4: Write AGENTS.md for Core Engine agent ───
Place in packages/core/AGENTS.md. Define scope (parsers, generators, validators), conventions (strict TS, Result<T,E>, vitest), boundaries (never touch apps/web or mcp-server), and state checklist.

Create packages/core/AGENTS.md with:

# Agent: Core Engine
## Scope
- packages/core/ exclusively
- Parsers: Style Dictionary, Tokens Studio, Tailwind, CSS
- Generators: DESIGN.md output
- Validators: grade, violations, a11y, lint
- Diff engine: additions, removals, changes

## Conventions
- Strict TypeScript (no any)
- Result<T, E> error pattern
- Vitest for all tests (80%+ coverage)
- Barrel exports from index.ts

## Boundaries
- NEVER modify apps/web, packages/mcp-server, or packages/cli
- Export types from index.ts for other packages to consume

## State Checklist
- [ ] All parsers passing with real-world tokens
- [ ] DESIGN.md generator producing valid output
- [ ] Validation engine returning grades
- [ ] Diff engine comparing two systems

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-4: Write AGENTS.md for Core Engine agent"

─── TASK agent-5: Write AGENTS.md for MCP + CLI agent ───
Place in packages/mcp-server/AGENTS.md. Scope covers both MCP server (McpServer class, tool handlers) and CLI (commander.js). Consumes @stitchwand/core as dependency.

Create packages/mcp-server/AGENTS.md with:

# Agent: MCP + CLI
## Scope
- packages/mcp-server/ and packages/cli/
- MCP tools: convert, validate, diff (thin wrappers around @stitchwand/core)
- CLI commands: stitchwand convert, validate, diff

## Conventions
- McpServer class from @modelcontextprotocol/sdk
- commander.js for CLI
- All processing delegated to @stitchwand/core — never duplicate logic

## Boundaries
- NEVER modify packages/core or apps/web
- Import types and functions from @stitchwand/core

## State Checklist
- [ ] MCP server responds to all 3 tool calls
- [ ] CLI convert/validate/diff commands work from terminal
- [ ] Published to npm as @stitchwand/mcp-server and @stitchwand/cli

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-5: Write AGENTS.md for MCP + CLI agent"

─── TASK agent-6: Write AGENTS.md for Web App agent ───
Place in apps/web/AGENTS.md. Scope covers all pages, components, hooks, and API routes. Uses @stitchwand/core for all processing. Next.js 16 + React 19 conventions.

Create apps/web/AGENTS.md with:

# Agent: Web App
## Scope
- apps/web/ exclusively
- All pages: DESIGN.md, Convert, Analyze, Prompts, Components, Starter Kits, Design Swarm, Doc Writer
- Hooks: useLocalStorage, useLabs, usePromptStorage, etc.
- API routes under apps/web/src/app/api/

## Conventions
- Next.js 16 + React 19 (read docs in node_modules/next/dist/docs/)
- All processing via @stitchwand/core — pages are thin UI wrappers
- localStorage persistence with 'sw-' key prefix
- Strict TypeScript (no any)

## Boundaries
- NEVER modify packages/core, packages/mcp-server, or packages/cli
- Import from @stitchwand/core for all token processing

## State Checklist
- [ ] All Core pages wired to real @stitchwand/core functions
- [ ] All Advanced pages fully functional with localStorage persistence
- [ ] No setTimeout/mock data remaining
- [ ] Labs features gated behind feature flags

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task agent-6: Write AGENTS.md for Web App agent"

FINAL SELF-CHECK (run after the last task):
  Verify agents files are valid markdown and AGENTS.md scope references exist

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/action-agents.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # action-agents — Multi-Agent System

    - **Section:** action-agents
    - **Agent:** coord
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/action-agents.md
    git commit -m "status: action-agents section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.

INSTRUCTIONS — read this first

IF PLAN MODE IS ON:
  - Present a plan covering every task below and WAIT for the user to reply with the exact word: approved
  - Do NOT use Write, Edit, NotebookEdit, or any file-mutating Bash command until you receive "approved".

IF PLAN MODE IS OFF:
  - Execute every task below IN ORDER, automatically, one at a time.
  - Commit after each task. Run the per-task self-check between tasks.
  - Do NOT stop for approval between tasks.

IN BOTH MODES:
  - The STATUS REPORT at the end is mandatory. The section is not "done" until that report exists and is committed.

SECTION: ACTION-LOGO — Logo / Icon / Brand Assets
AGENT: web
SCOPE: apps/web/public/brand/, apps/web/src/components/Logo*, apps/web/src/app/layout.tsx metadata

READ FIRST:
- CLAUDE.md in repo root
- AGENTS.md in your assigned working directory (if present)
- Any existing files you will modify, before proposing changes

TASK LIST — execute each task in order, commit after each:

─── TASK logo-mood-1: Midjourney: core concept exploration ───
8-12 generations exploring wand+thread concept, abstract stitch patterns, developer tool aesthetics. Use --style raw, --sref codes for consistency.

/imagine mood board for design system tool brand, magical wand weaving threads of code, indigo and purple color palette, dark background, tech-forward aesthetic, geometric precision with organic flow, professional software branding, minimalist but warm --ar 3:2 --style raw --no text words letters

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task logo-mood-1: Midjourney: core concept exploration"

─── TASK logo-sketch-1: Logo Diffusion: primary sketch conversion ───
40-60 generations across all sketches. 3 influence levels per sketch: high (7-8, preserve proportions), medium (5-6, allow interpretation), creative (3-4, loose inspiration). Export SVGs early.

Mode: Sketch-to-Logo | Input Influence: 5-6 | Style: Geometric/Abstract

professional software brand logo, geometric precision, indigo and purple gradient option, sophisticated minimal, developer tool aesthetic

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task logo-sketch-1: Logo Diffusion: primary sketch conversion"

─── TASK logo-txt-1: Midjourney: text-to-logo batch ───
20-30 generations across 4 concept families: geometric minimal, abstract wand/thread, layer/stack motif, SW lettermark. Use --style raw, --sref codes.

/imagine minimal vector logo for design system tool, geometric interlocking shapes, connection nodes, indigo #6366F1 single color, white background, flat design, scalable icon, by Paul Rand --ar 1:1 --style raw --no shading gradient realistic detail text

Self-check for this task:
  1) Re-read the files you changed.
  2) Run typecheck + tests (see final self-check at the bottom for commands).
  3) If anything fails, FIX the root cause before moving on.
  4) git add -p && git commit -m "task logo-txt-1: Midjourney: text-to-logo batch"

FINAL SELF-CHECK (run after the last task):
  cd apps/web && npx tsc --noEmit && npx next build

STATUS REPORT — write AFTER the final self-check passes:

  Write the report to: docs/agent-status/action-logo.md
  (Create the folder if it does not exist. Overwrite any existing file at that path.)

  Use this exact markdown template, filling in real values from your work:

    # action-logo — Logo / Icon / Brand Assets

    - **Section:** action-logo
    - **Agent:** web
    - **Date:** <YYYY-MM-DD of today>
    - **Branch:** <output of `git rev-parse --abbrev-ref HEAD`>
    - **HEAD commit:** <output of `git rev-parse --short HEAD`>

    ## Tasks completed
    - [x] <task-id> — <task-name> — commit <short-hash>
    - [x] ...

    ## Self-check results
    - typecheck: PASS | FAIL
    - unit tests: <N passed / M failed>
    - build: PASS | FAIL | N/A
    - final command run: (the FINAL SELF-CHECK command above)

    ## Files changed (in scope only)
    ```
    <output of: git diff --stat <base>..HEAD>
    ```

    ## Notes / blockers / follow-ups
    <bullet list of decisions made, anything deferred, or anything the user should know. Write "None." if clean.>

  Then commit the status file:
    git add docs/agent-status/action-logo.md
    git commit -m "status: action-logo section complete"

  This file is how the user verifies the section is done without reading the chat transcript.
  If any self-check step FAILED, still write the report with FAIL clearly marked and STOP — do not continue.
NON-NEGOTIABLE RULES:
  * If plan mode is ON: present a plan and wait for "approved" before touching files.
  * If plan mode is OFF: execute every task in order automatically — do not stop between tasks.
  * Stay inside the SCOPE above. Do not edit files outside it.
  * Per-task self-check is required. Do not skip.
  * Commit after each task with a clear message.
  * If a test or typecheck fails, fix the root cause — do not disable, skip, or mock around it.
  * No --no-verify, no --force, no destructive git ops.
  * If blocked, stop and ask. Do not guess.
  * The STATUS REPORT is mandatory. No section is "done" until docs/agent-status/{section}.md exists and is committed.