cfsa-antigravity 3.0.2 → 3.1.0

package/template/.agent/workflows/validate-phase.md

@@ -56,6 +56,6 @@ Runs production readiness checks: API documentation sync, accessibility audit, p
 Before reporting completion to the user:
 
 1. **Memory check** — Apply rule `memory-capture`. Write any patterns, decisions, or blockers from this workflow to `.memory/wiki/`. If nothing to write, confirm: "No new patterns/decisions/blockers."
-2. **Progress update** — Update `.agent/progress/` tracking files if they exist.
-3. **Session log** — Write session entry to `.agent/progress/sessions/`.
+2. **Progress update** — Update `.memory/pipeline/progress/` tracking files if they exist.
+3. **Session log** — Write session entry to `.memory/pipeline/progress/sessions/`.
 

package/template/.agent/workflows/verify-infrastructure.md

@@ -196,7 +196,7 @@ Read `.memory/wiki/specs/*-architecture-design.md` section `## Observability Arc
 
 ## 6.7. Spec pipeline integrity check
 
-1. Read `.agent/progress/spec-pipeline.md` — verify all IA/BE/FE columns show ✅ for all shards included in the current phase
+1. Read `.memory/pipeline/progress/spec-pipeline.md` — verify all IA/BE/FE columns show ✅ for all shards included in the current phase
 2. If `.memory/wiki/specs/feature-ledger.md` exists:
    - Read the ledger and verify no **Must Have** features have gaps in IA/BE/FE coverage
    - If any Must Have feature has an empty column → **STOP**: "Feature `[ID: name]` is missing `[column]` coverage. Complete the spec before proceeding to implementation."

package/template/.agent/workflows/write-architecture-spec-deepen.md

@@ -113,7 +113,7 @@ Change the shard's status from 🔲 to ✅ in `.memory/wiki/specs/ia/index.md`.
 ## 11. Update spec pipeline
 
 Read `.agent/skills/session-continuity/protocols/08-spec-pipeline-update.md` and follow the **Spec Pipeline Update Protocol**
-to mark this shard's IA column as complete in `.agent/progress/spec-pipeline.md`.
+to mark this shard's IA column as complete in `.memory/pipeline/progress/spec-pipeline.md`.
 
 ## 11.5. Bootstrap Tech Stack Skills (if applicable)
 
@@ -149,7 +149,7 @@ Read `.agent/skills/session-continuity/protocols/ambiguity-gates.md` and run the
 
 ## 13.5. Completion Gate (MANDATORY)
 
-1. **Verify pipeline tracker** — Read `.agent/progress/spec-pipeline.md` and confirm the IA column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 11. Go back and run Protocol 08 now before proceeding."
+1. **Verify pipeline tracker** — Read `.memory/pipeline/progress/spec-pipeline.md` and confirm the IA column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 11. Go back and run Protocol 08 now before proceeding."
 2. **Verify spec graph refresh** — Confirm Protocol 08 called `memory_compile` and that the compile succeeded. If graph refresh did not run → **STOP**: "Spec graph was not refreshed after tracker update. Run `memory_compile` before proceeding."
 3. Scan this conversation for memory-capture triggers (see rule: `memory-capture`):
    - Patterns observed → write to `.memory/wiki/patterns.md`
@@ -175,7 +175,7 @@ Use `notify_user` to present the completed IA shard for review. Your message MUS
 
 Do NOT proceed to the next step until the user sends a message explicitly approving this output. Proposing next steps is not the same as receiving approval. Wait for explicit approval before continuing.
 
-Read `.agent/progress/spec-pipeline.md` to determine the pipeline state, then propose the appropriate next step:
+Read `.memory/pipeline/progress/spec-pipeline.md` to determine the pipeline state, then propose the appropriate next step:
 
 - **More skeleton shards remain** → "Next: Run `/write-architecture-spec` for shard [next-shard-number]"
 - **All IA shards complete** → "All IA shards complete and /audit-ambiguity ia has already run (mandatory Step 13 above). If it scored 0%, proceed to `/write-be-spec`. If it found gaps, resolve them and re-run /audit-ambiguity ia as a fresh invocation before proceeding."

package/template/.agent/workflows/write-architecture-spec-design.md

@@ -24,7 +24,7 @@ Explore requirements, map all interactions, and define contracts, data models, a
 
 ## 0. Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the IA column = `not-started`.
    - If none → **STOP**: "All IA shards are already complete. Next step: `/write-be-spec`."

package/template/.agent/workflows/write-architecture-spec.md

@@ -41,7 +41,7 @@ Fill in a skeleton IA shard with full interaction details, data models, access c
 
 ### Step 0 — Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the IA column = `not-started`.
    - If none → **STOP**: "All IA shards are already complete. Next step: `/write-be-spec`."
@@ -84,6 +84,6 @@ Read .agent/skills/code-review-pro/SKILL.md and apply its adversarial review dis
 Before reporting completion to the user:
 
 1. **Memory check** — Apply rule `memory-capture`. Write any patterns, decisions, or blockers from this workflow to `.memory/wiki/`. If nothing to write, confirm: "No new patterns/decisions/blockers."
-2. **Progress update** — Update `.agent/progress/` tracking files if they exist.
-3. **Session log** — Write session entry to `.agent/progress/sessions/`.
+2. **Progress update** — Update `.memory/pipeline/progress/` tracking files if they exist.
+3. **Session log** — Write session entry to `.memory/pipeline/progress/sessions/`.
 

package/template/.agent/workflows/write-be-spec-classify.md

@@ -26,7 +26,7 @@ Identify the target IA shard, classify it, load skills, and read all source mate
 
 ## 0. Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the BE column = `not-started` AND the IA column = `complete`.
    - If no shards have IA `complete` → **STOP**: "IA layer not complete — run `/write-architecture-spec` first."

package/template/.agent/workflows/write-be-spec-write.md

@@ -71,7 +71,7 @@ If a shard was classified as **structural reference** with 0 BE specs, add a row
 
 ## 9. Update spec pipeline
 
-Read `.agent/skills/session-continuity/protocols/08-spec-pipeline-update.md` and follow the **Spec Pipeline Update Protocol** to mark this shard's BE column as complete in `.agent/progress/spec-pipeline.md`.
+Read `.agent/skills/session-continuity/protocols/08-spec-pipeline-update.md` and follow the **Spec Pipeline Update Protocol** to mark this shard's BE column as complete in `.memory/pipeline/progress/spec-pipeline.md`.
 
 ## 9.5. Iterative deepening passes
 
@@ -154,7 +154,7 @@ If `.memory/wiki/specs/feature-ledger.md` exists, read `.agent/skills/prd-templa
 
 ## 13.7. Completion Gate (MANDATORY)
 
-1. **Verify pipeline tracker** — Read `.agent/progress/spec-pipeline.md` and confirm the BE column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 9. Go back and run Protocol 08 now before proceeding."
+1. **Verify pipeline tracker** — Read `.memory/pipeline/progress/spec-pipeline.md` and confirm the BE column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 9. Go back and run Protocol 08 now before proceeding."
 2. **Verify spec graph refresh** — Confirm Protocol 08 called `memory_compile` and that the compile succeeded. If graph refresh did not run → **STOP**: "Spec graph was not refreshed after tracker update. Run `memory_compile` before proceeding."
 3. Scan this conversation for memory-capture triggers (see rule: `memory-capture`):
    - Patterns observed → write to `.memory/wiki/patterns.md`
@@ -176,7 +176,7 @@ Use `notify_user` presenting:
 1. **Spec created** (link)
 2. **Cross-reference verification**
 3. **Ambiguity Gate confirmation**
-4. **Pipeline State** — read `.agent/progress/spec-pipeline.md` and propose the next step from the **ONLY** permitted options below:
+4. **Pipeline State** — read `.memory/pipeline/progress/spec-pipeline.md` and propose the next step from the **ONLY** permitted options below:
 
 - **More BE specs remain** → "Next: Run `/write-be-spec` for shard [next-shard-number]"
 - **All BE specs complete** → "All BE specs complete and `/audit-ambiguity be` has already run (mandatory Step 12 above). If it scored 0%, proceed to `/write-fe-spec`. If it found gaps, resolve them and re-run `/audit-ambiguity be` before proceeding."

package/template/.agent/workflows/write-be-spec.md

@@ -52,7 +52,7 @@ If a needed skill is missing, check if a matching entry exists in `.agent/skill-
 
 ### Step 0 — Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the BE column = `not-started` AND the IA column = `complete`.
    - If no shards have IA `complete` → **STOP**: "IA layer not complete — run `/write-architecture-spec` first."
@@ -91,6 +91,6 @@ Read .agent/skills/code-review-pro/SKILL.md and apply its adversarial review dis
 Before reporting completion to the user:
 
 1. **Memory check** — Apply rule `memory-capture`. Write any patterns, decisions, or blockers from this workflow to `.memory/wiki/`. If nothing to write, confirm: "No new patterns/decisions/blockers."
-2. **Progress update** — Update `.agent/progress/` tracking files if they exist.
-3. **Session log** — Write session entry to `.agent/progress/sessions/`.
+2. **Progress update** — Update `.memory/pipeline/progress/` tracking files if they exist.
+3. **Session log** — Write session entry to `.memory/pipeline/progress/sessions/`.
 

package/template/.agent/workflows/write-fe-spec-classify.md

@@ -26,7 +26,7 @@ Identify the target FE spec, classify it, load skills, and read all source mater
 
 ## 0. Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the FE column = `not-started` AND the BE column = `complete`.
    - If no shards have BE `complete` → **STOP**: "BE layer not complete — run `/write-be-spec` first."

package/template/.agent/workflows/write-fe-spec-write.md

@@ -148,7 +148,7 @@ If `.memory/wiki/specs/feature-ledger.md` exists, read `.agent/skills/prd-templa
 
 ## 12.7. Completion Gate (MANDATORY)
 
-1. **Verify pipeline tracker** — Read `.agent/progress/spec-pipeline.md` and confirm the FE column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 8. Go back and run Protocol 08 now before proceeding."
+1. **Verify pipeline tracker** — Read `.memory/pipeline/progress/spec-pipeline.md` and confirm the FE column for this shard shows `complete`. If it does not → **STOP**: "Pipeline tracker was not updated in Step 8. Go back and run Protocol 08 now before proceeding."
 2. **Verify spec graph refresh** — Confirm Protocol 08 called `memory_compile` and that the compile succeeded. If graph refresh did not run → **STOP**: "Spec graph was not refreshed after tracker update. Run `memory_compile` before proceeding."
 3. Scan this conversation for memory-capture triggers (see rule: `memory-capture`):
    - Patterns observed → write to `.memory/wiki/patterns.md`
@@ -167,7 +167,7 @@ Use `notify_user` presenting:
 1. **Spec created** (link)
 2. **Cross-reference verification**
 3. **Ambiguity Gate confirmation**
-4. **Pipeline State** — read `.agent/progress/spec-pipeline.md` and propose the next step from the **ONLY** permitted options below:
+4. **Pipeline State** — read `.memory/pipeline/progress/spec-pipeline.md` and propose the next step from the **ONLY** permitted options below:
 
 - **More FE specs remain** → "Next: Run `/write-fe-spec` for shard [next-shard-number]"
 - **All FE specs complete** → "All FE specs complete and `/audit-ambiguity fe` has already run (mandatory Step 11 above). If it scored 0% and the Navigation Completeness Check passes (Step 14 below), proceed to `/plan-phase`. If gaps remain, resolve them first."

package/template/.agent/workflows/write-fe-spec.md

@@ -49,7 +49,7 @@ If a needed skill is missing, check if a matching entry exists in `.agent/skill-
 
 ### Step 0 — Pipeline State Check
 
-1. Read `.agent/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
    - If the file does not exist → **STOP**: "No pipeline tracker found. Run `/decompose-architecture` first."
 2. Identify all shards where the FE column = `not-started` AND the BE column = `complete`.
    - If no shards have BE `complete` → **STOP**: "BE layer not complete — run `/write-be-spec` first."
@@ -88,6 +88,6 @@ Read .agent/skills/code-review-pro/SKILL.md and apply its adversarial review dis
 Before reporting completion to the user:
 
 1. **Memory check** — Apply rule `memory-capture`. Write any patterns, decisions, or blockers from this workflow to `.memory/wiki/`. If nothing to write, confirm: "No new patterns/decisions/blockers."
-2. **Progress update** — Update `.agent/progress/` tracking files if they exist.
-3. **Session log** — Write session entry to `.agent/progress/sessions/`.
+2. **Progress update** — Update `.memory/pipeline/progress/` tracking files if they exist.
+3. **Session log** — Write session entry to `.memory/pipeline/progress/sessions/`.
 

package/template/.claude/README.md

@@ -37,6 +37,8 @@ A Claude install also gets the shared `.memory/` runtime scaffold, including:
 
 Tool-specific MCP client config and Claude hook wiring are user-managed. If you want Claude to talk to the shared memory daemon, add the appropriate MCP client config yourself and then run the initial compile before opening Obsidian at `.memory/`.
 
+Claude should point at `.memory/mcp-server/client.mjs`. That client now resolves the daemon from the current workspace's `.memory/runtime/cfsa-memory-daemon.json` and validates the daemon's `projectRoot` from `/health`, so a Claude session in one repo will not silently proxy into another repo's daemon.
+
 All runtimes should read and write shared project memory through `.memory/` and the MCP bridge.
 
 ```text
@@ -56,7 +58,7 @@ This directory is the standalone Claude Code runtime for the CFSA pipeline. It s
 
 1. **Skills vs Workflows**: Claude Code uses skills instead of passive workflow markdown files
 2. **Task System**: Uses Claude Code's built-in Tasks system for progress tracking
-3. **Progress + Shared Memory**: Uses `.claude/progress/` for Claude pipeline state and project-level `.memory/` for canonical cross-runtime memory
+3. **Progress + Shared Memory**: Uses `.memory/pipeline/progress/` for Claude pipeline state and project-level `.memory/` for canonical cross-runtime memory
 4. **Invocation**: Workflows are invoked as skills rather than slash commands in markdown
 5. **Hooks + MCP**: Claude adds native hooks on top of the shared `cfsa-memory` MCP bridge
 

package/template/.claude/instructions/workflow.md

@@ -6,7 +6,7 @@ Before taking any action on a task:
 - Read the agent config file at project root (`AGENTS.md` for Antigravity, `GEMINI.md` for Gemini CLI, or equivalent for your agent)
 - Read relevant `.claude/instructions/` files for the task type
 - Check [Engineering Standards](../../.memory/wiki/specs/ENGINEERING-STANDARDS.md) for quality bar — if this file doesn't exist yet, the pipeline hasn't reached /create-prd; run /ideate then /create-prd first
-- **Session Resumption**: If `.claude/progress/index.md` exists, read `.claude/skills/session-continuity/protocols/01-session-resumption.md` and follow the **Session Resumption Protocol** to load cross-session context and identify the resumption point
+- **Session Resumption**: If `.memory/pipeline/progress/index.md` exists, read `.claude/skills/session-continuity/protocols/01-session-resumption.md` and follow the **Session Resumption Protocol** to load cross-session context and identify the resumption point
 
 ## 2. Check Skills
 - Scan `.claude/skills/` for applicable skills
@@ -38,7 +38,7 @@ Do NOT mark a task complete until all validations pass.
 After completing a workflow or substantial task:
 
 - **Pattern Extraction**: Read `.claude/skills/session-continuity/protocols/04-pattern-extraction.md` and follow the **Pattern Extraction Protocol**. Reflect on what worked, what didn't, and log reusable patterns to `memory/patterns.md`. Skip only if the task was trivial (routine, nothing new learned).
-- **Session Close**: Read `.claude/skills/session-continuity/protocols/05-session-close.md` and follow the **Session Close Protocol**. Write a session log to `.claude/progress/sessions/` so the next session can resume cleanly.
+- **Session Close**: Read `.claude/skills/session-continuity/protocols/05-session-close.md` and follow the **Session Close Protocol**. Write a session log to `.memory/pipeline/progress/sessions/` so the next session can resume cleanly.
 
 > These steps are **not optional**. They are what differentiate a pipeline that gets
 > smarter over time from one that repeats the same mistakes.
@@ -46,7 +46,7 @@ After completing a workflow or substantial task:
 ## 6. Recommend Next Step (MANDATORY)
 
 Before reporting completion via `notify_user`:
-- Check the pipeline progress state (`.claude/progress/spec-pipeline.md` or equivalent)
+- Check the pipeline progress state (`.memory/pipeline/progress/spec-pipeline.md` or equivalent)
 - Propose the next valid pipeline command to the user
 - If multiple valid next steps exist, list them with brief context
 - Never end a conversation without telling the user what to do next

package/template/.claude/kit-sync.md

@@ -1,6 +1,6 @@
 # Kit Sync State
 
 upstream: https://github.com/RepairYourTech/cfsa-antigravity
-last_synced_commit: 63c31d9113ccb3f828aeb5c8a4902483cbbc2e8a
-last_synced_at: 2026-04-15T09:10:27Z
-kit_version: 3.0.2
+last_synced_commit: 41065b8165f7ea05b56a48f029eabcca52aa3049
+last_synced_at: 2026-05-03T19:45:21Z
+kit_version: 3.1.0

package/template/.claude/rules/completion-checklist.md

@@ -31,7 +31,7 @@ A unit of work is only DONE when:
 
 1. **The Code**: Implementation meets the contract and acceptance criteria.
 2. **The Tests**: All tests pass (validation step is green).
-3. **The Tracking**: Progress markdown files in `.claude/progress/` are updated.
+3. **The Tracking**: Progress markdown files in `.memory/pipeline/progress/` are updated.
    - Acceptance criteria marked `[x]`
    - Slice/Task marked `[x]`
    - Phase progress fractions updated (e.g., `3/10` → `4/10`)
@@ -42,10 +42,10 @@ A unit of work is only DONE when:
    - `decisions.md` — Any non-trivial decisions logged per Protocol 06
    - `blockers.md` — Any blockers hit logged with status and impact
    - See rule: `memory-capture` for triggers and format
-6. **The Session Log**: A session close log exists in `.claude/progress/sessions/`.
+6. **The Session Log**: A session close log exists in `.memory/pipeline/progress/sessions/`.
    - Follow `.claude/skills/session-continuity/protocols/05-session-close.md` — write what was accomplished, deferred, and where the next session should start
 7. **The Next Step**: The user is told what comes next in the pipeline.
-   - Read the pipeline progress file (`.claude/progress/spec-pipeline.md` or equivalent)
+   - Read the pipeline progress file (`.memory/pipeline/progress/spec-pipeline.md` or equivalent)
    - Propose the next valid pipeline command based on current state
    - If multiple options exist, present them as a numbered list with brief context
    - If the pipeline stage is complete, say so explicitly

package/template/.claude/skills/parallel-agents/SKILL.md

@@ -162,4 +162,4 @@ Enter parallel mode when the slice's tasks contain surface tags (`BE`, `FE`, `QA
 
 ### Progress Logging
 
-Log each dispatch phase to `.claude/progress/slices/phase-NN-slice-NN.md` under `## Dispatch Log`.
+Log each dispatch phase to `.memory/pipeline/progress/slices/phase-NN-slice-NN.md` under `## Dispatch Log`.

package/template/.claude/skills/plan-phase/SKILL.md

@@ -16,7 +16,7 @@ Runs phase planning in two shards: preflight → write.
 ## Prerequisites
 
 1. IA, BE, and FE spec layers are fully complete
-2. Phase progression state exists in `.claude/progress/`
+2. Phase progression state exists in `.memory/pipeline/progress/`
 3. Architecture phasing section and spec indexes are available
 
 ## Step-by-Step
@@ -44,7 +44,7 @@ Call skill: `plan-phase-write`
 Expected outputs:
 - `.memory/wiki/specs/phases/phase-N.md`
 - `.memory/wiki/specs/phases/phase-N-draft.md`
-- generated progress files in `.claude/progress/`
+- generated progress files in `.memory/pipeline/progress/`
 - verified bootstrap/map completeness for planning prerequisites
 
 ## Completion Checklist

package/template/.claude/skills/plan-phase-preflight/SKILL.md

@@ -14,13 +14,13 @@ parameters:
 ## Prerequisites
 
 1. Approved IA/BE/FE specs exist
-2. Progress state files exist under `.claude/progress/`
+2. Progress state files exist under `.memory/pipeline/progress/`
 
 ## Step-by-Step
 
 ### Step 0 — Phase sequencing gate
 
-1. Read `.claude/progress/index.md` for current phase number.
+1. Read `.memory/pipeline/progress/index.md` for current phase number.
 2. If planning Phase N>1, verify Phase N-1 is complete and has passing `/validate-phase`.
 3. Run architecture map freshness warning gate for N>1 (warning + user resolution).
 

package/template/.claude/skills/session-continuity/SKILL.md

@@ -2,7 +2,7 @@
 name: session-continuity
 description: >
   Cross-session progress tracking, pattern extraction, and session resumption.
-  Gives agents memory across sessions using markdown files in `.claude/progress/`.
+  Gives agents memory across sessions using markdown files in `.memory/pipeline/progress/`.
   Subsumes self-improving-agent — handles both implementation tracking AND
   experiential learning in one skill. Workflows invoke specific protocols by name.
 triggers:
@@ -16,7 +16,7 @@ triggers:
 
 Cross-session memory and spec-driven implementation tracking. This skill replaces
 `self-improving-agent` by combining progress tracking with pattern extraction
-in a single, workflow-driven system. Progress tracking remains in `.claude/progress/`, but shared cross-runtime memory now lives in the project-level `.memory/` root.
+in a single, workflow-driven system. Progress tracking is shared at `.memory/pipeline/progress/`; shared cross-runtime memory lives in the project-level `.memory/` root.
 
 ## Overview
 
@@ -50,10 +50,10 @@ This skill defines each protocol with exact steps, file formats, and rules.
 
 ## Directory Structure
 
-All progress state lives in `.claude/progress/`:
+All progress state lives in `.memory/pipeline/progress/`:
 
 ```
-.claude/progress/
+.memory/pipeline/progress/
 ├── index.md                      # Master checklist — phases + overall %
 ├── spec-pipeline.md              # Spec completion tracker (IA/BE/FE per shard)
 ├── phases/
@@ -91,7 +91,7 @@ for complex ones.
 
 ### Steps
 
-1. **Check if `.claude/progress/index.md` exists**
+1. **Check if `.memory/pipeline/progress/index.md` exists**
    - If no: this is a fresh project with no tracked progress. Skip resumption.
    - If yes: continue.
 
@@ -460,7 +460,7 @@ have IA specs, BE specs, and FE specs completed.
 
 1. **Read the IA index** — `.memory/wiki/specs/ia/index.md` — to get the list of shards.
 
-2. **Create `.claude/progress/spec-pipeline.md`**:
+2. **Create `.memory/pipeline/progress/spec-pipeline.md`**:
    ```markdown
    # Spec Pipeline Progress
 

package/template/.claude/skills/session-continuity/protocols/01-session-resumption.md

@@ -10,7 +10,7 @@
 
 ## Steps
 
-1. **Check if `.claude/progress/index.md` exists**
+1. **Check if `.memory/pipeline/progress/index.md` exists**
    - If no: this is a fresh project with no tracked progress. Skip resumption.
    - If yes: continue.
 

package/template/.claude/skills/session-continuity/protocols/02-progress-generation.md

@@ -12,7 +12,7 @@
 
 1. **Read the phase plan** that was just created (the output of `/plan-phase`).
 
-2. **Create or update `.claude/progress/index.md`**:
+2. **Create or update `.memory/pipeline/progress/index.md`**:
    ```markdown
    # Implementation Progress
 
@@ -27,7 +27,7 @@
    | Phase 1: {{NAME}} | not-started | 0/{{N}} | [→](phases/phase-01.md) |
    ```
 
-3. **Create `.claude/progress/phases/phase-NN.md`**:
+3. **Create `.memory/pipeline/progress/phases/phase-NN.md`**:
    ```markdown
    # Phase {{N}}: {{NAME}}
 
@@ -55,7 +55,7 @@
    - `files:` blocks are NOT written during generation — only during claim (Protocol 9)
    - Subtasks under tagged tasks inherit the parent's surface ownership
 
-4. **Create `.claude/progress/slices/phase-NN-slice-NN.md`** for each slice with ≥3 criteria:
+4. **Create `.memory/pipeline/progress/slices/phase-NN-slice-NN.md`** for each slice with ≥3 criteria:
    ```markdown
    # Phase {{P}} / Slice {{S}}: {{NAME}}
 

package/template/.claude/skills/session-continuity/protocols/03-progress-update.md

@@ -10,9 +10,9 @@
 
 ## Steps
 
-1. **Mark tasks and acceptance criteria `[x]`** in the slice's tracking location (use the exact files in the `.claude/progress/` directory, NEVER guess the path):
-   - If slice has its own file: update `.claude/progress/slices/phase-NN-slice-NN.md`
-   - If inline: update `.claude/progress/phases/phase-NN.md`
+1. **Mark tasks and acceptance criteria `[x]`** in the slice's tracking location (use the exact files in the `.memory/pipeline/progress/` directory, NEVER guess the path):
+   - If slice has its own file: update `.memory/pipeline/progress/slices/phase-NN-slice-NN.md`
+   - If inline: update `.memory/pipeline/progress/phases/phase-NN.md`
 
 2. **Release any claimed tasks** — if the completed task had `[!]`:
    - Change status from `[/]` to `[x]`
@@ -42,7 +42,7 @@
    **Progress**: 4/7 slices
    ```
 
-5. **Update `.claude/progress/index.md`** — recalculate overall progress:
+5. **Update `.memory/pipeline/progress/index.md`** — recalculate overall progress:
    ```markdown
    **Overall**: 12/20 slices (60%)
    ```

package/template/.claude/skills/session-continuity/protocols/07-spec-pipeline-generation.md

@@ -13,7 +13,7 @@ have IA specs, BE specs, and FE specs completed.
 
 1. **Read the IA index** — `.memory/wiki/specs/ia/index.md` — to get the list of shards.
 
-2. **Create `.claude/progress/spec-pipeline.md`**:
+2. **Create `.memory/pipeline/progress/spec-pipeline.md`**:
    ```markdown
    # Spec Pipeline Progress
 

package/template/.claude/skills/session-continuity/protocols/08-spec-pipeline-update.md

@@ -14,7 +14,7 @@
 1. **Identify the shard and layer** — which shard just got its spec completed,
    and which layer (IA, BE, or FE)?
 
-2. **Update `.claude/progress/spec-pipeline.md`** — before updating any cell, perform these validation checks:
+2. **Update `.memory/pipeline/progress/spec-pipeline.md`** — before updating any cell, perform these validation checks:
 
    (a) Read the `File` column for the shard from the tracker to get the expected file path.
    (b) Confirm the file exists at that path. If not → **skip the update** and report: `"Cannot mark [shard] [layer] as complete — file not found at [path]"`
@@ -44,7 +44,7 @@
 
 6. **Read-back verification** — immediately after updating the tracker:
 
-   (a) Read `.claude/progress/spec-pipeline.md` back.
+   (a) Read `.memory/pipeline/progress/spec-pipeline.md` back.
    (b) Locate the row for the shard that was just updated.
    (c) Verify the column that was just marked shows `complete` (not `not-started`, not unchanged, not any other value).
    (d) If the cell does NOT show `complete`:

package/template/.claude/skills/session-continuity/protocols/11-parallel-synthesis.md

@@ -4,7 +4,7 @@ Run after all parallel agents have completed and QA-GREEN has passed.
 
 ## Pre-Synthesis Plan
 
-Before beginning any synthesis work, write a `## Synthesis Plan` section to the slice file (`.claude/progress/slices/phase-NN-slice-NN.md`) listing:
+Before beginning any synthesis work, write a `## Synthesis Plan` section to the slice file (`.memory/pipeline/progress/slices/phase-NN-slice-NN.md`) listing:
 - All `// BOUNDARY:` stubs found across agent outputs (file path + stub description)
 - All cross-surface integrations to wire (e.g., "BE auth middleware → FE token refresh handler")
 

package/template/.claude/skills/setup/setup-cfsa.md

@@ -121,7 +121,7 @@ Call skill: `setup/setup-verify`
 
 After successful verification, initialize progress tracking:
 
-1. Create master progress file at `.claude/progress/spec-pipeline.md`
+1. Create master progress file at `.memory/pipeline/progress/spec-pipeline.md`
 2. Set initial state: "Ready to start ideation"
 3. Create session log for today
 4. Recommend next step: `/ideate`

package/template/.claude/skills/write-architecture-spec/SKILL.md

@@ -16,14 +16,14 @@ Runs IA specification authoring in two shards: design → deepen.
 ## Prerequisites
 
 1. Decomposition outputs exist (`.memory/wiki/specs/ia/` skeletons + indexes)
-2. `.claude/progress/spec-pipeline.md` exists and includes IA column states
+2. `.memory/pipeline/progress/spec-pipeline.md` exists and includes IA column states
 3. Stack map is resolved for required categories (Databases, Security, Surfaces)
 
 ## Step-by-Step
 
 ### Step 0 — Pipeline-state shard selection
 
-1. Read `.claude/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
 2. Select lowest-numbered IA shard with `not-started` status unless override is explicitly requested.
 3. If no IA shard remains: stop and direct next step to `/write-be-spec`.
 

package/template/.claude/skills/write-architecture-spec-deepen/SKILL.md

@@ -45,7 +45,7 @@ Ensure event-consumer cross-references are valid and bidirectional.
 ### Step 4 — Update indexes and tracker
 
 1. Mark shard complete in `.memory/wiki/specs/ia/index.md`.
-2. Update `.claude/progress/spec-pipeline.md` IA column via protocol.
+2. Update `.memory/pipeline/progress/spec-pipeline.md` IA column via protocol.
 3. Run conditional bootstrap if shard is the architecture-design stack-lock shard.
 
 ### Step 5 — Ambiguity gates and last-shard branch

package/template/.claude/skills/write-architecture-spec-design/SKILL.md

@@ -20,7 +20,7 @@ parameters:
 
 ### Step 0 — Pipeline and map guards
 
-1. Read `.claude/progress/spec-pipeline.md` and select target shard.
+1. Read `.memory/pipeline/progress/spec-pipeline.md` and select target shard.
 2. Verify required stack map values exist in `.claude/instructions/tech-stack.md`:
    - Databases
    - Security

package/template/.claude/skills/write-be-spec/SKILL.md

@@ -16,14 +16,14 @@ Runs BE specification authoring in two shards: classify → write.
 ## Prerequisites
 
 1. IA shard(s) are complete and marked ✅ in `.memory/wiki/specs/ia/index.md`
-2. `.claude/progress/spec-pipeline.md` exists
+2. `.memory/pipeline/progress/spec-pipeline.md` exists
 3. BE conventions/index files exist under `.memory/wiki/specs/be/`
 
 ## Step-by-Step
 
 ### Step 0 — Pipeline-state shard selection
 
-1. Read `.claude/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
 2. Find shards where IA is `complete` and BE is `not-started`.
 3. Select lowest-numbered eligible shard unless user explicitly overrides.
 4. If none remain, stop and recommend `/write-fe-spec`.
@@ -45,7 +45,7 @@ Call skill: `write-be-spec-write`
 Expected outputs:
 - Full BE spec file(s) in `.memory/wiki/specs/be/`
 - Updated `.memory/wiki/specs/be/index.md`
-- Updated `.claude/progress/spec-pipeline.md` BE status
+- Updated `.memory/pipeline/progress/spec-pipeline.md` BE status
 - Ambiguity gate results + next allowed command
 
 ## Quality Gate

package/template/.claude/skills/write-be-spec-classify/SKILL.md

@@ -14,7 +14,7 @@ parameters:
 ## Prerequisites
 
 1. Target IA shard is complete
-2. `.memory/wiki/specs/ia/index.md` and `.claude/progress/spec-pipeline.md` are present
+2. `.memory/wiki/specs/ia/index.md` and `.memory/pipeline/progress/spec-pipeline.md` are present
 
 ## Step-by-Step
 

package/template/.claude/skills/write-be-spec-write/SKILL.md

@@ -46,7 +46,7 @@ Apply line-count thresholds:
 ### Step 4 — Index and tracker updates
 
 1. Update `.memory/wiki/specs/be/index.md`.
-2. Update BE completion state in `.claude/progress/spec-pipeline.md`.
+2. Update BE completion state in `.memory/pipeline/progress/spec-pipeline.md`.
 3. Handle structural-reference no-spec rows when classification indicates 0 specs.
 
 ### Step 5 — Iterative deepening passes

package/template/.claude/skills/write-fe-spec/SKILL.md

@@ -16,7 +16,7 @@ Runs FE specification authoring in two shards: classify → write.
 ## Prerequisites
 
 1. BE spec for target shard is complete
-2. `.claude/progress/spec-pipeline.md` exists
+2. `.memory/pipeline/progress/spec-pipeline.md` exists
 3. FE conventions/index files exist under `.memory/wiki/specs/fe/`
 4. Design system and brand guidance are available for visual surfaces
 
@@ -24,7 +24,7 @@ Runs FE specification authoring in two shards: classify → write.
 
 ### Step 0 — Pipeline-state shard selection
 
-1. Read `.claude/progress/spec-pipeline.md`.
+1. Read `.memory/pipeline/progress/spec-pipeline.md`.
 2. Find shards where BE is `complete` and FE is `not-started`.
 3. Select lowest-numbered eligible shard unless user explicitly overrides.
 4. If none remain, stop and recommend `/plan-phase`.
@@ -47,7 +47,7 @@ Call skill: `write-fe-spec-write`
 Expected outputs:
 - Full FE spec file(s) in `.memory/wiki/specs/fe/`
 - Updated `.memory/wiki/specs/fe/index.md`
-- Updated `.claude/progress/spec-pipeline.md` FE status
+- Updated `.memory/pipeline/progress/spec-pipeline.md` FE status
 - Ambiguity + navigation completeness gate outcomes
 
 ## Quality Gate

package/template/.claude/skills/write-fe-spec-write/SKILL.md

@@ -34,7 +34,7 @@ Apply line-count thresholds:
 ### Step 3 — Index and tracker updates
 
 1. Update `.memory/wiki/specs/fe/index.md` status.
-2. Update FE completion state in `.claude/progress/spec-pipeline.md` via protocol.
+2. Update FE completion state in `.memory/pipeline/progress/spec-pipeline.md` via protocol.
 
 ### Step 4 — Iterative deepening passes