mustard-claude 3.1.6 → 3.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mustard-claude",
-  "version": "3.1.6",
+  "version": "3.1.7",
   "description": "Framework-agnostic CLI for Claude Code project setup",
   "type": "module",
   "bin": {

package/templates/.claude/commands/stack.md

@@ -1,86 +1,86 @@
-<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
-# Stack: Templates
-
-> Technology stack and tooling for the Mustard templates subproject.
-
-## Runtime
-
-| Component | Version | Notes |
-|-----------|---------|-------|
-| Node.js | >=18 | All hooks/scripts use CommonJS (`require`) |
-| JavaScript | ES2020+ | Optional chaining, nullish coalescing, `Set`, `Map` |
-
-## Dependencies
-
-None. All template files are dependency-free — they use only Node.js built-in modules:
-
-| Module | Used In |
-|--------|---------|
-| `fs` | All hooks, all scripts |
-| `path` | All hooks, all scripts |
-| `child_process` | `auto-format.js`, `pre-compact.js`, `statusline.js`, `sync-detect.js`, `sync-registry.js` |
-| `crypto` | `sync-detect.js` (SHA-256 hashing) |
-| `os` | `statusline.js`, `session-cleanup.js` |
-
-## File Categories
-
-| Category | Path | Count | Purpose |
-|----------|------|-------|---------|
-| Hooks | `hooks/*.js` | 8 | PreToolUse/PostToolUse/Session lifecycle guards |
-| Scripts | `scripts/*.js` | 3 | Sync-detect, sync-registry, statusline |
-| Commands | `commands/mustard/*/SKILL.md` | 14 | Slash command definitions |
-| Skills | `skills/*/SKILL.md` | 6 | Foundation skills (design-craft, react-best-practices, etc.) |
-| Config | `settings.json` | 1 | Hook wiring, permissions, statusline |
-| Config | `pipeline-config.md` | 1 | Agent dispatch rules, wave system, model selection |
-| Template | `CLAUDE.md` | 1 | Orchestrator rules template |
-
-## Commands
-
-```bash
-# Run hook tests
-node --test hooks/__tests__/hooks.test.js
-
-# Run sync-detect (outputs JSON)
-node scripts/sync-detect.js
-node scripts/sync-detect.js --no-cache
-
-# Run sync-registry
-node scripts/sync-registry.js
-node scripts/sync-registry.js --force
-```
-
-## Structure
-
-```
-templates/
-├── CLAUDE.md                    # Orchestrator rules (copied to .claude/CLAUDE.md)
-├── settings.json                # Hook wiring + permissions
-├── pipeline-config.md           # Agent/wave/model config
-├── commands/mustard/             # 14 slash commands
-│   ├── feature/SKILL.md
-│   ├── bugfix/SKILL.md
-│   ├── scan/SKILL.md
-│   ├── git/SKILL.md
-│   └── ... (approve, complete, resume, status, task, etc.)
-├── hooks/                        # 8 lifecycle hooks
-│   ├── bash-safety.js            # PreToolUse — block dangerous commands
-│   ├── file-guard.js             # PreToolUse — block sensitive files
-│   ├── enforce-registry.js       # PreToolUse — require entity-registry
-│   ├── auto-format.js            # PostToolUse — prettier/dotnet format
-│   ├── guard-verify.js           # PostToolUse — architectural rules
-│   ├── subagent-tracker.js       # Pre/SubagentStart/Stop — agent state
-│   ├── pre-compact.js            # PreCompact — snapshot before compaction
-│   ├── session-cleanup.js        # SessionEnd — prune stale state
-│   └── __tests__/hooks.test.js   # Tests (node:test + node:assert)
-├── scripts/
-│   ├── sync-detect.js            # Subproject discovery + role detection
-│   ├── sync-registry.js          # Entity registry generation
-│   └── statusline.js             # ANSI statusline renderer
-└── skills/                       # Foundation skills
-    ├── commit-workflow/
-    ├── design-craft/
-    ├── pipeline-execution/
-    ├── react-best-practices/
-    ├── senior-architect/
-    └── skill-creator/
-```
+<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
+# Stack: Templates
+
+> Technology stack and tooling for the Mustard templates subproject.
+
+## Runtime
+
+| Component | Version | Notes |
+|-----------|---------|-------|
+| Node.js | >=18 | All hooks/scripts use CommonJS (`require`) |
+| JavaScript | ES2020+ | Optional chaining, nullish coalescing, `Set`, `Map` |
+
+## Dependencies
+
+None. All template files are dependency-free — they use only Node.js built-in modules:
+
+| Module | Used In |
+|--------|---------|
+| `fs` | All hooks, all scripts |
+| `path` | All hooks, all scripts |
+| `child_process` | `auto-format.js`, `pre-compact.js`, `statusline.js`, `sync-detect.js`, `sync-registry.js` |
+| `crypto` | `sync-detect.js` (SHA-256 hashing) |
+| `os` | `statusline.js`, `session-cleanup.js` |
+
+## File Categories
+
+| Category | Path | Count | Purpose |
+|----------|------|-------|---------|
+| Hooks | `hooks/*.js` | 8 | PreToolUse/PostToolUse/Session lifecycle guards |
+| Scripts | `scripts/*.js` | 3 | Sync-detect, sync-registry, statusline |
+| Commands | `commands/mustard/*/SKILL.md` | 14 | Slash command definitions |
+| Skills | `skills/*/SKILL.md` | 6 | Foundation skills (design-craft, react-best-practices, etc.) |
+| Config | `settings.json` | 1 | Hook wiring, permissions, statusline |
+| Config | `.claude/pipeline-config.md` | 1 | Agent dispatch rules, wave system, model selection |
+| Template | `CLAUDE.md` | 1 | Orchestrator rules template |
+
+## Commands
+
+```bash
+# Run hook tests
+node --test hooks/__tests__/hooks.test.js
+
+# Run sync-detect (outputs JSON)
+node scripts/sync-detect.js
+node scripts/sync-detect.js --no-cache
+
+# Run sync-registry
+node scripts/sync-registry.js
+node scripts/sync-registry.js --force
+```
+
+## Structure
+
+```
+templates/
+├── CLAUDE.md                    # Orchestrator rules (copied to .claude/CLAUDE.md)
+├── settings.json                # Hook wiring + permissions
+├── pipeline-config.md           # Agent/wave/model config
+├── commands/mustard/             # 14 slash commands
+│   ├── feature/SKILL.md
+│   ├── bugfix/SKILL.md
+│   ├── scan/SKILL.md
+│   ├── git/SKILL.md
+│   └── ... (approve, complete, resume, status, task, etc.)
+├── hooks/                        # 8 lifecycle hooks
+│   ├── bash-safety.js            # PreToolUse — block dangerous commands
+│   ├── file-guard.js             # PreToolUse — block sensitive files
+│   ├── enforce-registry.js       # PreToolUse — require entity-registry
+│   ├── auto-format.js            # PostToolUse — prettier/dotnet format
+│   ├── guard-verify.js           # PostToolUse — architectural rules
+│   ├── subagent-tracker.js       # Pre/SubagentStart/Stop — agent state
+│   ├── pre-compact.js            # PreCompact — snapshot before compaction
+│   ├── session-cleanup.js        # SessionEnd — prune stale state
+│   └── __tests__/hooks.test.js   # Tests (node:test + node:assert)
+├── scripts/
+│   ├── sync-detect.js            # Subproject discovery + role detection
+│   ├── sync-registry.js          # Entity registry generation
+│   └── statusline.js             # ANSI statusline renderer
+└── skills/                       # Foundation skills
+    ├── commit-workflow/
+    ├── design-craft/
+    ├── pipeline-execution/
+    ├── react-best-practices/
+    ├── senior-architect/
+    └── skill-creator/
+```

package/templates/.claude/skills/templates-command-authoring/SKILL.md

@@ -1,88 +1,88 @@
----
-name: templates-command-authoring
-description: "Pattern for writing slash command SKILL.md files with trigger, procedure,
-  and rules. Use when creating a new mustard command, adding a pipeline command,
-  writing a /command, or the user says 'new command', 'add slash command',
-  'create /feature-like command', 'write command template'."
----
-<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
-
-# Command Authoring Pattern
-
-Slash commands are SKILL.md files in `commands/mustard/{command-name}/SKILL.md` that define orchestrator behavior.
-
-## Pattern
-
-### File Convention
-- Location: `commands/mustard/{command-name}/SKILL.md`
-- No YAML frontmatter (commands are not auto-loaded by description)
-- End with `ULTRATHINK` keyword **only for `/feature` and `/bugfix` commands** — do NOT add it to other commands
-
-### Structure
-
-```markdown
-# /{command-name} - Title
-
-> Advisory note (optional)
-
-## Trigger
-`/{command-name} <args>`
-
-## Description
-What the command does and when to use it.
-
-## Procedure / ## Action
-Step-by-step process. Use:
-- Tables for signal → action mappings
-- Numbered steps for sequential flow
-- Code blocks for bash commands
-- `### Phase` headers for multi-phase pipelines
-
-## Rules
-- Explicit constraints (NEVER, ALWAYS, MUST)
-- Budget limits (max reads, max API calls)
-- Delegation requirements
-```
-
-> Note: Add `ULTRATHINK` at the end only for `/feature` and `/bugfix` commands. All other commands end after the last rule/section.
-
-### Key Rules
-- Commands NEVER implement code directly — they orchestrate via Task tool
-- Pipeline commands create spec files and pipeline state JSON
-- Git commands read `mustard.json` for branch flow configuration
-- Zero-confirmation: most commands execute without asking user
-
-### Command Categories
-
-| Category | Examples | Characteristic |
-|----------|----------|---------------|
-| Pipeline | `/feature`, `/bugfix`, `/approve`, `/complete`, `/resume` | Multi-phase, creates spec, state tracking |
-| Task | `/task-analyze`, `/task-review`, `/task-refactor` | Single delegation, no spec |
-| Git | `/git sync`, `/git commit`, `/git push`, `/git merge` | Reads `mustard.json`, submodule-aware |
-| Scan | `/scan`, `/scan-format` | Discovery + analysis + generation |
-| Status | `/status`, `/validate` | Read-only, reporting |
-
-## Example
-
-```markdown
-# /my-command - Do Something
-
-## Trigger
-`/my-command <name>`
-
-## Procedure
-1. Read `pipeline-config.md` for agent config
-2. Dispatch Task agent with context
-3. Collect results and report
-
-## Rules
-- NEVER implement code directly
-- ALWAYS delegate via Task tool
-- Budget: max 5 API calls
-```
-Ref: `commands/mustard/feature/SKILL.md`, `commands/mustard/status/SKILL.md`
-
-## References
-
-For full code examples with variants:
-> Read `references/examples.md`
+---
+name: templates-command-authoring
+description: "Pattern for writing slash command SKILL.md files with trigger, procedure,
+  and rules. Use when creating a new mustard command, adding a pipeline command,
+  writing a /command, or the user says 'new command', 'add slash command',
+  'create /feature-like command', 'write command template'."
+---
+<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
+
+# Command Authoring Pattern
+
+Slash commands are SKILL.md files in `commands/mustard/{command-name}/SKILL.md` that define orchestrator behavior.
+
+## Pattern
+
+### File Convention
+- Location: `commands/mustard/{command-name}/SKILL.md`
+- No YAML frontmatter (commands are not auto-loaded by description)
+- End with `ULTRATHINK` keyword **only for `/feature` and `/bugfix` commands** — do NOT add it to other commands
+
+### Structure
+
+```markdown
+# /{command-name} - Title
+
+> Advisory note (optional)
+
+## Trigger
+`/{command-name} <args>`
+
+## Description
+What the command does and when to use it.
+
+## Procedure / ## Action
+Step-by-step process. Use:
+- Tables for signal → action mappings
+- Numbered steps for sequential flow
+- Code blocks for bash commands
+- `### Phase` headers for multi-phase pipelines
+
+## Rules
+- Explicit constraints (NEVER, ALWAYS, MUST)
+- Budget limits (max reads, max API calls)
+- Delegation requirements
+```
+
+> Note: Add `ULTRATHINK` at the end only for `/feature` and `/bugfix` commands. All other commands end after the last rule/section.
+
+### Key Rules
+- Commands NEVER implement code directly — they orchestrate via Task tool
+- Pipeline commands create spec files and pipeline state JSON
+- Git commands read `mustard.json` for branch flow configuration
+- Zero-confirmation: most commands execute without asking user
+
+### Command Categories
+
+| Category | Examples | Characteristic |
+|----------|----------|---------------|
+| Pipeline | `/feature`, `/bugfix`, `/approve`, `/complete`, `/resume` | Multi-phase, creates spec, state tracking |
+| Task | `/task-analyze`, `/task-review`, `/task-refactor` | Single delegation, no spec |
+| Git | `/git sync`, `/git commit`, `/git push`, `/git merge` | Reads `mustard.json`, submodule-aware |
+| Scan | `/scan`, `/scan-format` | Discovery + analysis + generation |
+| Status | `/status`, `/validate` | Read-only, reporting |
+
+## Example
+
+```markdown
+# /my-command - Do Something
+
+## Trigger
+`/my-command <name>`
+
+## Procedure
+1. Read `.claude/pipeline-config.md` for agent config
+2. Dispatch Task agent with context
+3. Collect results and report
+
+## Rules
+- NEVER implement code directly
+- ALWAYS delegate via Task tool
+- Budget: max 5 API calls
+```
+Ref: `commands/mustard/feature/SKILL.md`, `commands/mustard/status/SKILL.md`
+
+## References
+
+For full code examples with variants:
+> Read `references/examples.md`

package/templates/.claude/skills/templates-command-authoring/references/examples.md

@@ -1,83 +1,83 @@
-<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
-# Command Authoring Examples
-
-## Example 1: Simple Status Command
-
-```markdown
-# /status - Consolidated Status
-
-## Trigger
-`/status`
-
-## Description
-Shows consolidated project status.
-
-## Information
-1. **Git Status** — branch, modified files, pending push
-2. **Pipeline** — active pipeline, current phase
-3. **Build** — last validation result
-4. **Entity Registry** — entity count, last update
-
-ULTRATHINK
-```
-Ref: `commands/mustard/status/SKILL.md`
-
-## Example 2: Pipeline Command (Feature)
-
-Key sections from the feature command:
-
-```markdown
-# /feature - Feature Pipeline
-
-## Trigger
-`/feature <feature-name>`
-
-### ANALYZE Phase
-1. Read `pipeline-config.md`
-2. Read `entity-registry.json` via Grep
-3. Determine layers from signals
-
-#### Scope Detection
-| Signal | Scope |
-|--------|-------|
-| 1-2 layers, ≤5 files | Light |
-| 3+ layers, 5+ files | Full |
-
-### PLAN Phase
-Create `.claude/spec/active/{date}-{name}/spec.md`
-
-## Rules
-- NEVER implement code in Full scope
-- ALWAYS create pipeline state at PLAN phase
-- Light scope + user chose "implement now" → EXECUTE inline
-
-ULTRATHINK
-```
-Ref: `commands/mustard/feature/SKILL.md`
-
-## Example 3: Git Command with Action Dispatch
-
-```markdown
-# /git - Git Operations
-
-## Trigger
-`/git <action>`
-
-## Actions
-| Action | Description |
-|--------|-------------|
-| `sync` | Pull parent into current |
-| `commit` | Create commit (no push) |
-| `push` | Sync + commit + push |
-
-## Step 0 — Resolve Parent
-cat mustard.json → match branch against flow patterns
-
-## Behavior
-- ZERO confirmations
-- Minimize Bash calls — chain with &&
-- Submodules BEFORE parent
-
-ULTRATHINK
-```
-Ref: `commands/mustard/git/SKILL.md`
+<!-- mustard:generated at:2026-03-25T00:00:00.000Z role:general -->
+# Command Authoring Examples
+
+## Example 1: Simple Status Command
+
+```markdown
+# /status - Consolidated Status
+
+## Trigger
+`/status`
+
+## Description
+Shows consolidated project status.
+
+## Information
+1. **Git Status** — branch, modified files, pending push
+2. **Pipeline** — active pipeline, current phase
+3. **Build** — last validation result
+4. **Entity Registry** — entity count, last update
+
+ULTRATHINK
+```
+Ref: `commands/mustard/status/SKILL.md`
+
+## Example 2: Pipeline Command (Feature)
+
+Key sections from the feature command:
+
+```markdown
+# /feature - Feature Pipeline
+
+## Trigger
+`/feature <feature-name>`
+
+### ANALYZE Phase
+1. Read `.claude/pipeline-config.md`
+2. Read `entity-registry.json` via Grep
+3. Determine layers from signals
+
+#### Scope Detection
+| Signal | Scope |
+|--------|-------|
+| 1-2 layers, ≤5 files | Light |
+| 3+ layers, 5+ files | Full |
+
+### PLAN Phase
+Create `.claude/spec/active/{date}-{name}/spec.md`
+
+## Rules
+- NEVER implement code in Full scope
+- ALWAYS create pipeline state at PLAN phase
+- Light scope + user chose "implement now" → EXECUTE inline
+
+ULTRATHINK
+```
+Ref: `commands/mustard/feature/SKILL.md`
+
+## Example 3: Git Command with Action Dispatch
+
+```markdown
+# /git - Git Operations
+
+## Trigger
+`/git <action>`
+
+## Actions
+| Action | Description |
+|--------|-------------|
+| `sync` | Pull parent into current |
+| `commit` | Create commit (no push) |
+| `push` | Sync + commit + push |
+
+## Step 0 — Resolve Parent
+cat mustard.json → match branch against flow patterns
+
+## Behavior
+- ZERO confirmations
+- Minimize Bash calls — chain with &&
+- Submodules BEFORE parent
+
+ULTRATHINK
+```
+Ref: `commands/mustard/git/SKILL.md`

package/templates/CLAUDE.md

@@ -87,4 +87,4 @@ RTK (Rust Token Killer) is integrated as core infrastructure. A PreToolUse hook
 - If RTK is not installed, the hook silently passes through (zero impact)
 
 ## Full Reference
-Rules, pipeline, naming: `pipeline-config.md`
+Rules, pipeline, naming: `.claude/pipeline-config.md`

package/templates/commands/mustard/approve/SKILL.md

@@ -18,7 +18,7 @@ Approves the active spec and prepares the implementation phase. Does NOT execute
 1. **Step 0: AUTO-SYNC (MANDATORY)** — Run via Bash tool BEFORE any other action:
    - `node .claude/scripts/sync-registry.js`
    - Do NOT proceed to step 2 without running this command
-2. **Read** `pipeline-config.md` — agents, model selection
+2. **Read** `.claude/pipeline-config.md` — agents, model selection
 3. Locate active spec in `.claude/spec/active/`
 4. **Spec Checkpoint — update spec header:**
    - `### Status: approved`
@@ -29,7 +29,7 @@ Approves the active spec and prepares the implementation phase. Does NOT execute
    - Parse Tasks from spec to extract tasks per agent (DB, Backend, Frontend, etc.)
    - Create `.claude/.pipeline-states/` directory if it doesn't exist
    - Write state file with `specName`, `status: "approved"`, `phaseName: "PLAN"`, `tasks` with names and agents, `model`, `updatedAt`
-6. **Model selection** — read `Model Selection` from `pipeline-config.md` and record `"model"` field in state:
+6. **Model selection** — read `Model Selection` from `.claude/pipeline-config.md` and record `"model"` field in state:
    - Count total estimated files in spec
    - Apply rule: ≤5 files/known patterns → `"model": "sonnet"`, 5+ files/new patterns → `"model": "opus"`
 7. **Task Tracking — create TaskCreate for each agent:**

package/templates/commands/mustard/bugfix/SKILL.md

@@ -87,7 +87,7 @@ Rules:
 ### EXECUTE (fix + validate)
 
 Every agent prompt dispatched in Fast Path MUST include:
-`Return format cap: ≤50 lines. Apply compact Return Format from pipeline-config.md strictly.`
+`Return format cap: ≤50 lines. Apply compact Return Format from .claude/pipeline-config.md strictly.`
 
 Dispatch bugfix agent with:
 - Root cause from ANALYZE
@@ -110,7 +110,7 @@ After the bugfix agent returns, check for an escalation status before closing:
 - `PARTIAL` — agent fixed some but not all reported issues; resume from the last incomplete fix step (max 2 retries)
 - `DEFERRED` — agent intentionally left a related issue unfixed with justification; confirm with user before closing
 
-See `pipeline-config.md` Escalation Statuses for the full status table.
+See `.claude/pipeline-config.md` Escalation Statuses for the full status table.
 
 #### Retry Compact Advisory
 If an agent fails and requires >2 retry attempts during EXECUTE:

package/templates/commands/mustard/complete/SKILL.md

@@ -11,7 +11,7 @@ Finalizes the current pipeline, either completing or canceling.
 ## Verification Gate (MANDATORY)
 
 1. **Review completed**: Check pipeline state — review agent MUST have run and returned APPROVED. If not → dispatch review first (see resume.md step 19)
-2. **Build passes**: run build command for each affected subproject (from pipeline-config.md)
+2. **Build passes**: run build command for each affected subproject (from .claude/pipeline-config.md)
 3. **Changes match spec**: each `[x]` corresponds to a real file
 4. **Zero CRITICAL issues**: review report shows zero CRITICAL violations (SOLID, design system, patterns, i18n, integration)
 5. **No regressions**: existing features still work
@@ -41,7 +41,7 @@ Before finalizing, scan the active spec for any `## Concerns` section written du
 - If all concerns are `CONCERN` or `DEFERRED` (non-blocking): note them and proceed
 - This step is a read-only scan — do NOT alter or dismiss concerns during CLOSE
 
-See `pipeline-config.md` Escalation Statuses for concern classification rules.
+See `.claude/pipeline-config.md` Escalation Statuses for concern classification rules.
 
 ## Action
 

package/templates/commands/mustard/feature/SKILL.md

@@ -53,7 +53,7 @@ Prepend the following to EVERY subagent prompt dispatched during the pipeline:
 
 If the diff file is empty or missing, skip the Git State header entirely. Never dispatch an agent without attempting interpolation.
 
-1. Read `pipeline-config.md` — agents, wave transitions, model selection
+1. Read `.claude/pipeline-config.md` — agents, wave transitions, model selection
 2. Read `entity-registry.json` via Grep for the specific entity name (e.g. `"Contract":`) — NEVER read the full JSON. Entity found? infer layers. Not found? all layers.
 3. Determine layers from signals:
 
@@ -166,13 +166,13 @@ Rules:
 When user chooses "Approve and implement now":
 1. Update spec: `Status: implementing`, `Phase: EXECUTE`
    Every agent prompt dispatched in Light scope MUST include:
-   `Return format cap: ≤50 lines. Apply compact Return Format from pipeline-config.md strictly.`
+   `Return format cap: ≤50 lines. Apply compact Return Format from .claude/pipeline-config.md strictly.`
 2. Update pipeline state: `status: "implementing"`, `phase: 3`
-3. Read `pipeline-config.md` for agent config. For `entity-registry.json`: Grep for specific entity block only
+3. Read `.claude/pipeline-config.md` for agent config. For `entity-registry.json`: Grep for specific entity block only
 4. Match recipes by title via Grep on `{subproject}/.claude/commands/recipes.md` — do NOT read full file. Extract recipe number + pattern refs
 5. Identify relevant skills for `{recommended_skills}`: list skill names most relevant to the task (e.g., `api-endpoint-wiring, api-dto-validation`). Agents use these as hints — Claude natively decides which to load based on descriptions
-6. Dispatch agents (wave rules: DB+Backend parallel, Frontend after Backend UNLESS spec marks task as `(parallel-safe)` — see `pipeline-config.md` Parallel Rules). Agent prompt includes `{recommended_skills}` as skill hints — agents read SKILL.md of relevant skills before implementing
-7. Wave transitions between waves (from `pipeline-config.md`)
+6. Dispatch agents (wave rules: DB+Backend parallel, Frontend after Backend UNLESS spec marks task as `(parallel-safe)` — see `.claude/pipeline-config.md` Parallel Rules). Agent prompt includes `{recommended_skills}` as skill hints — agents read SKILL.md of relevant skills before implementing
+7. Wave transitions between waves (from `.claude/pipeline-config.md`)
 8. On return: validate (build/type-check), update spec `[ ]` → `[x]` (line-by-line edits, NEVER copy entire spec blocks as old_string)
 8b. **Agent Memory:** After agents return and spec is updated, write agent memory: `node .claude/scripts/memory-write.js --json '{"agent_type":"{type}","wave":{N},"pipeline":"{spec-name}","summary":"{what agent did}","details":{...}}'` — one per agent. Skip if single-wave pipeline (no downstream agents to benefit).
 
@@ -186,7 +186,7 @@ After each agent returns, check the return value for an escalation status before
 - `PARTIAL` — apply Granular Retry Protocol from the last completed step; do NOT restart from step 1
 - `DEFERRED` — note in spec with agent justification; ask user if the deferred item is load-bearing before closing
 
-If two or more agents in the same wave return `CONCERN`, surface all concerns together before starting the next wave. See `pipeline-config.md` Escalation Statuses and Diagnostic Failure Routing for the full status table.
+If two or more agents in the same wave return `CONCERN`, surface all concerns together before starting the next wave. See `.claude/pipeline-config.md` Escalation Statuses and Diagnostic Failure Routing for the full status table.
 
 9. **REVIEW** — dispatch review agent for each affected subproject (reads guards + relevant skills, runs 7-category checklist: SOLID, Design System, Patterns, i18n, Integration, Build, Elegance). REJECTED → fix + re-review (max 2 loops)
 10. All passed + APPROVED → CLOSE flow inline (sync registry, move spec, cleanup state)
@@ -208,13 +208,13 @@ Progress: `[v] ANALYZE  [>] PLAN  [ ] EXECUTE  [ ] CLOSE`
 Scope tag: `[LIGHT]` or `[FULL]` after progress line.
 
 ## Rules
-- This command is self-contained — reads `pipeline-config.md` directly
+- This command is self-contained — reads `.claude/pipeline-config.md` directly
 - NEVER implement code in Full scope — only PLAN. EXECUTE via `/approve` + `/resume`
 - NEVER launch Explore agent when entity already exists in registry — read 2-3 files directly
 - NEVER read additional files after Explore agent returns — its output is final
 - NEVER exceed 5 file reads in ANALYZE phase (registry + pipeline-config are free)
 - Light scope + user chose "implement now" → proceed to EXECUTE inline
-- ALWAYS read `pipeline-config.md` for agent/wave/model info
+- ALWAYS read `.claude/pipeline-config.md` for agent/wave/model info
 - ALWAYS create pipeline state at PLAN phase
 - ALWAYS record `scope` in spec header AND pipeline state
 - ALWAYS go straight to PLAN once you understand the change — more reads ≠ better spec

package/templates/commands/mustard/knowledge/SKILL.md

@@ -103,7 +103,7 @@ Manages persistent project observations injected into agent context during pipel
 | (no argument) | — | Lists all notes files |
 | `{subproject}` | `{subproject}/.claude/commands/notes.md` | Subproject agent context |
 
-**Monorepo**: discover targets from `pipeline-config.md` Agents table or Glob `*/.claude/commands/notes.md`.
+**Monorepo**: discover targets from `.claude/pipeline-config.md` Agents table or Glob `*/.claude/commands/notes.md`.
 **Single repo**: target is root → `.claude/commands/notes.md`.
 
 ### Flow — List (`/knowledge notes`)

package/templates/commands/mustard/maint/SKILL.md

@@ -1,68 +1,68 @@
-# /maint - Maintenance Utilities
-
-> Dependencies, build validation, and registry sync.
-
-## Trigger
-
-`/maint <action>`
-
-## Actions
-
-| Action | Description |
-|--------|-------------|
-| `deps` | Install dependencies for all projects |
-| `validate` | Run build and type-check validations |
-| `sync` | Update entity-registry.json from code |
-
----
-
-## deps
-
-Installs dependencies. Monorepo: runs in all subprojects. Single repo: runs in root.
-
-### Flow
-
-1. Read `pipeline-config.md` → extract `Agents` table for subproject paths and install commands
-2. For each subproject (or root if single repo), run the restore/install command from `## Commands` in `{subproject}/CLAUDE.md`
-3. Run all in parallel
-
-**Single repo**: read root `CLAUDE.md` → `## Commands` → run the install/restore command.
-
----
-
-## validate
-
-Runs build and type-check validations.
-
-### Flow
-
-1. Read `pipeline-config.md` → extract `Agents` table for validate/build commands
-2. For each subproject (or root if single repo), run the build/type-check command from `{subproject}/CLAUDE.md` → `## Commands`
-3. Run all in parallel
-
-### Result
-
-- **Success** — project compiles and passes type-check
-- **Failure** — lists errors found
-
-**Single repo**: read root `CLAUDE.md` → `## Commands` → run the build command.
-
----
-
-## sync
-
-Scans the project and updates `.claude/entity-registry.json`.
-
-### Flow
-
-1. `node .claude/scripts/sync-registry.js`
-2. If script not found, scan manually:
-   - Search database schemas (EF Core `DbSet<T>`, Drizzle `pgTable()`, Prisma `model`, etc.)
-   - Build entity map with relationships
-   - Update `.claude/entity-registry.json`
-
-### When to Use
-
-- After creating new entity
-- After importing existing code
-- To sync after manual changes
+# /maint - Maintenance Utilities
+
+> Dependencies, build validation, and registry sync.
+
+## Trigger
+
+`/maint <action>`
+
+## Actions
+
+| Action | Description |
+|--------|-------------|
+| `deps` | Install dependencies for all projects |
+| `validate` | Run build and type-check validations |
+| `sync` | Update entity-registry.json from code |
+
+---
+
+## deps
+
+Installs dependencies. Monorepo: runs in all subprojects. Single repo: runs in root.
+
+### Flow
+
+1. Read `.claude/pipeline-config.md` → extract `Agents` table for subproject paths and install commands
+2. For each subproject (or root if single repo), run the restore/install command from `## Commands` in `{subproject}/CLAUDE.md`
+3. Run all in parallel
+
+**Single repo**: read root `CLAUDE.md` → `## Commands` → run the install/restore command.
+
+---
+
+## validate
+
+Runs build and type-check validations.
+
+### Flow
+
+1. Read `.claude/pipeline-config.md` → extract `Agents` table for validate/build commands
+2. For each subproject (or root if single repo), run the build/type-check command from `{subproject}/CLAUDE.md` → `## Commands`
+3. Run all in parallel
+
+### Result
+
+- **Success** — project compiles and passes type-check
+- **Failure** — lists errors found
+
+**Single repo**: read root `CLAUDE.md` → `## Commands` → run the build command.
+
+---
+
+## sync
+
+Scans the project and updates `.claude/entity-registry.json`.
+
+### Flow
+
+1. `node .claude/scripts/sync-registry.js`
+2. If script not found, scan manually:
+   - Search database schemas (EF Core `DbSet<T>`, Drizzle `pgTable()`, Prisma `model`, etc.)
+   - Build entity map with relationships
+   - Update `.claude/entity-registry.json`
+
+### When to Use
+
+- After creating new entity
+- After importing existing code
+- To sync after manual changes

package/templates/commands/mustard/resume/SKILL.md

@@ -87,7 +87,7 @@ Before the normal detect-and-confirm flow, scan the newest pipeline state for a
 ### Diff Context (automatic)
 Run `node .claude/scripts/diff-context.js` to capture the current git state. Include the output in the agent prompt as `{diff_context}` so agents know what has already changed.
 
-7. **Read** `pipeline-config.md`. For `entity-registry.json`: use Grep to extract ONLY the relevant entity block (e.g. `"Contract":`), NEVER read the full JSON
+7. **Read** `.claude/pipeline-config.md`. For `entity-registry.json`: use Grep to extract ONLY the relevant entity block (e.g. `"Contract":`), NEVER read the full JSON
 9. **Update spec header:** `Status: implementing`, `Phase: EXECUTE`, `Checkpoint: {ISO now}`
 10. **Update/create pipeline state:** `status: "implementing"`, `phaseName: "EXECUTE"`, `specName`
 11. **TaskCreate** — 1 per pending agent (skip completed)
@@ -97,9 +97,9 @@ Run `node .claude/scripts/diff-context.js` to capture the current git state. Inc
 **CRITICAL: Main context IS the Pipeline Runner. NEVER delegate to intermediate Task agent.**
 
 12. **Match recipe by name only:** Grep `{subproject}/.claude/commands/recipes.md` for recipe title matching the task type — do NOT read the full recipes file. Extract only: recipe number, pattern refs, reference modules
-13. **Plan waves:** `Depends on: none` → Wave 1; dependencies → later. DB+Backend parallel. Frontend after Backend UNLESS all parallel override conditions met (see `pipeline-config.md` Parallel Rules). Review agents: ALWAYS dispatch in single parallel message. Skip completed tasks.
+13. **Plan waves:** `Depends on: none` → Wave 1; dependencies → later. DB+Backend parallel. Frontend after Backend UNLESS all parallel override conditions met (see `.claude/pipeline-config.md` Parallel Rules). Review agents: ALWAYS dispatch in single parallel message. Skip completed tasks.
 14. **Build agent prompts using template** (`.claude/commands/mustard/templates/agent-prompt/SKILL.md`):
-    - Read template once, then fill placeholders per agent using `pipeline-config.md` data:
+    - Read template once, then fill placeholders per agent using `.claude/pipeline-config.md` data:
       - `{subproject}` → from Agents table (Subproject column)
       - `{reference_files}` → 2-3 files from matched recipe
       - `{guards_summary}` → key guards from `{subproject}/CLAUDE.md`
@@ -108,12 +108,12 @@ Run `node .claude/scripts/diff-context.js` to capture the current git state. Inc
       - `{validate_command}`, `{build_command}` → from Agents table in config
       - `{retry_context}` → empty on first dispatch (see Step 4 for retries)
       - `{task_steps}` → checkboxed steps from spec
-      - `{recommended_skills}` → from Skill Recommendations in `pipeline-config.md`:
+      - `{recommended_skills}` → from Skill Recommendations in `.claude/pipeline-config.md`:
         1. Glob `{subproject}/.claude/skills/` for generated pattern skills
         2. Add foundation skills matching the role (ui→design-craft+react-best-practices, mobile→design-craft)
         3. Format as bullet list: `- {skill-name}`
 
-16. **Wave transitions** — between waves, execute transitions from `pipeline-config.md`:
+16. **Wave transitions** — between waves, execute transitions from `.claude/pipeline-config.md`:
     - After Wave 1 (api/database/library) completes, before Wave 2 (ui):
       - Execute each command listed in the matching `Wave Transitions` section
     - Wait for transitions to complete before dispatching next wave
@@ -136,7 +136,7 @@ After each agent returns, check the return value for an escalation status before
 - `PARTIAL` — apply Granular Retry Protocol from the last completed step; do NOT restart from step 1
 - `DEFERRED` — note in spec with agent justification; ask user if the deferred item is load-bearing before closing
 
-If two or more agents in the same wave return `CONCERN`, surface all concerns together before dispatching the next wave. See `pipeline-config.md` Escalation Statuses and Diagnostic Failure Routing for the full status table.
+If two or more agents in the same wave return `CONCERN`, surface all concerns together before dispatching the next wave. See `.claude/pipeline-config.md` Escalation Statuses and Diagnostic Failure Routing for the full status table.
 
 ### Step 4: Validate, Review & Complete
 
@@ -206,6 +206,6 @@ This eliminates decision fatigue on resume. The user can always override, but th
 - Wave dispatch: ALL agents in same wave in a SINGLE message
 - Each sub-agent reads its own `{subproject}/CLAUDE.md` + auto-loads relevant skills (orchestrator does NOT read them)
 - Update pipeline state + spec checkboxes at each transition
-- ALWAYS read `pipeline-config.md` for agent/wave/model config — NEVER hardcode project-specific values
+- ALWAYS read `.claude/pipeline-config.md` for agent/wave/model config — NEVER hardcode project-specific values
 - ALWAYS use agent-prompt template — NEVER build prompts from scratch
 - ALWAYS execute wave transitions between waves

package/templates/commands/mustard/scan/SKILL.md

@@ -112,10 +112,10 @@ You do NOT implement code — you delegate via Task tool.
 | Simple | config, docs, small refactor, rename, move | Delegate via Task |
 
 Any change that touches production code (schema, API, UI) → Pipeline Feature.
-Read `pipeline-config.md` for agent dispatch rules.
+Read `.claude/pipeline-config.md` for agent dispatch rules.
 
 ## Full Reference
-Rules, pipeline, naming: `pipeline-config.md`
+Rules, pipeline, naming: `.claude/pipeline-config.md`
 ```
 
 **Root `CLAUDE.md`** — project map from detected subprojects:

package/templates/commands/mustard/scan-format/SKILL.md

@@ -98,7 +98,7 @@ After generating command files, update the subproject's `CLAUDE.md`:
 - If `## Guards` section exists, update with key guards from analysis
 - If `## Stack` is empty, fill from detected stack
 - **`## Commands` section MUST include ALL detected tooling commands** — not just build/run. Include migration commands, code generation, seeding, testing, linting. Every command an agent might need to execute. If tooling detection (step 3) found commands, they MUST appear here.
-- **`## Recommended Skills`** — list generated pattern skills (`{subproject}-patterns-*`) + matching foundation skills from `pipeline-config.md` Skill Recommendations table. This section informs agents which skills to consult before implementation.
+- **`## Recommended Skills`** — list generated pattern skills (`{subproject}-patterns-*`) + matching foundation skills from `.claude/pipeline-config.md` Skill Recommendations table. This section informs agents which skills to consult before implementation.
 
 ## 8. Implementation Recipes
 

package/templates/skills/pipeline-execution/SKILL.md

@@ -111,7 +111,7 @@ Steps: update spec → summarize failure → Explore → rewrite tasks → re-ap
 
 ## Role Rules
 
-> See `pipeline-config.md § Role Rules` for role boundaries and validation rules.
+> See `.claude/pipeline-config.md § Role Rules` for role boundaries and validation rules.
 
 ## Pipeline Bugfix