prizmkit 1.0.68 → 1.0.74

package/bundled/dev-pipeline/scripts/parse-stream-progress.py

@@ -56,10 +56,51 @@ class ProgressTracker:
         self._current_tool_input_parts = []
 
     def process_event(self, event):
-        """Process a single stream-json event and update state."""
+        """Process a single stream-json event and update state.
+
+        Supports two formats:
+        1. Claude API raw stream: message_start, content_block_start, content_block_delta, etc.
+        2. Claude Code verbose stream-json: assistant, user, tool_result, system, etc.
+           (produced by claude/claude-internal --verbose --output-format stream-json)
+        """
         event_type = event.get("type", "")
 
-        if event_type == "message_start":
+        # ── Claude Code verbose format ──────────────────────────────
+        if event_type == "assistant":
+            self.message_count += 1
+            self.is_active = True
+            message = event.get("message", {})
+            content_blocks = message.get("content", [])
+            for block in content_blocks:
+                block_type = block.get("type", "")
+                if block_type == "tool_use":
+                    tool_name = block.get("name", "unknown")
+                    self.current_tool = tool_name
+                    self.tool_call_counts[tool_name] += 1
+                    self.total_tool_calls += 1
+                    # Extract summary from input
+                    tool_input = block.get("input", {})
+                    if isinstance(tool_input, dict):
+                        self._extract_tool_summary_from_dict(tool_input)
+                    self._detect_phase(json.dumps(tool_input, ensure_ascii=False)[:500])
+                elif block_type == "text":
+                    text = block.get("text", "")
+                    if text.strip():
+                        self.last_text_snippet = text.strip()[:120]
+                    self._detect_phase(text)
+
+        elif event_type == "tool_result" or event_type == "user":
+            # tool_result contains output from tool execution
+            self.is_active = True
+
+        elif event_type == "system":
+            # System events (hooks, init, etc.) — track but don't count as messages
+            subtype = event.get("subtype", "")
+            if subtype == "init":
+                self.is_active = True
+
+        # ── Claude API raw stream format ────────────────────────────
+        elif event_type == "message_start":
             self.message_count += 1
             self.is_active = True
 
@@ -141,28 +182,31 @@ class ProgressTracker:
                     return
 
     def _extract_tool_summary(self, raw_input):
-        """Extract a human-readable summary from tool input JSON."""
+        """Extract a human-readable summary from tool input JSON string."""
         try:
             data = json.loads(raw_input)
-            # Common patterns in tool inputs
-            if isinstance(data, dict):
-                # Agent tool - look for description or prompt
-                if "description" in data:
-                    self.current_tool_input_summary = str(data["description"])[:100]
-                elif "command" in data:
-                    self.current_tool_input_summary = str(data["command"])[:100]
-                elif "file_path" in data:
-                    self.current_tool_input_summary = str(data["file_path"])[:100]
-                elif "pattern" in data:
-                    self.current_tool_input_summary = str(data["pattern"])[:100]
-                elif "query" in data:
-                    self.current_tool_input_summary = str(data["query"])[:100]
-                elif "prompt" in data:
-                    self.current_tool_input_summary = str(data["prompt"])[:100]
+            self._extract_tool_summary_from_dict(data)
         except (json.JSONDecodeError, TypeError):
             # Keep whatever partial summary we had
             pass
 
+    def _extract_tool_summary_from_dict(self, data):
+        """Extract a human-readable summary from tool input dict."""
+        if isinstance(data, dict):
+            # Common patterns in tool inputs
+            if "description" in data:
+                self.current_tool_input_summary = str(data["description"])[:100]
+            elif "command" in data:
+                self.current_tool_input_summary = str(data["command"])[:100]
+            elif "file_path" in data:
+                self.current_tool_input_summary = str(data["file_path"])[:100]
+            elif "pattern" in data:
+                self.current_tool_input_summary = str(data["pattern"])[:100]
+            elif "query" in data:
+                self.current_tool_input_summary = str(data["query"])[:100]
+            elif "prompt" in data:
+                self.current_tool_input_summary = str(data["prompt"])[:100]
+
     def to_dict(self):
         """Export current state as a dictionary for JSON serialization."""
         tool_calls = [

package/bundled/dev-pipeline/templates/agent-knowledge-template.md

@@ -0,0 +1,13 @@
+# {{AGENT_ROLE}}
+
+## FINDINGS
+- <discovery>: <why it matters>
+
+## DECISIONS
+- <decision>: <rationale>
+
+## INTERFACES_DISCOVERED
+- <module.function>: <signature> — <behavior note>
+
+## CONTEXT_BUILT
+- <file-path>: <one-line summary>

package/bundled/dev-pipeline/templates/bootstrap-tier1.md

@@ -42,6 +42,28 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 ## Execution
 
+### Phase 0.5: Agent Knowledge Setup
+
+Create the agent knowledge directory and initialize your own knowledge doc:
+```bash
+mkdir -p .prizmkit/specs/{{FEATURE_SLUG}}/agents
+```
+
+Write `.prizmkit/specs/{{FEATURE_SLUG}}/agents/orchestrator.md`:
+```markdown
+# Orchestrator
+
+## FINDINGS
+
+## DECISIONS
+
+## INTERFACES_DISCOVERED
+
+## CONTEXT_BUILT
+```
+
+After each phase, append notable DECISIONS/FINDINGS to your `agents/orchestrator.md`.
+
 {{IF_INIT_NEEDED}}
 ### Phase 0: Project Bootstrap
 - Run `/prizmkit-init` (invoke the prizmkit-init skill)
@@ -108,24 +130,19 @@ Key decisions: [list]
 
 **CP-2**: All acceptance criteria met, tests pass, code review passed.
 
-### Phase 4.5: Memory Maintenance (mandatory before commit)
+### Phase 4.5: Architecture Sync & Memory Sedimentation (mandatory before commit)
 
-Run `/prizmkit-retrospective` — the **sole maintainer** of `.prizm-docs/`:
+Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index) and platform memory files:
 1. **Structural sync**: Use `git diff --cached --name-status` to locate changed modules, update KEY_FILES/INTERFACES/DEPENDENCIES/file counts in affected `.prizm-docs/` files
-2. **Knowledge injection** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizm-docs/`
-3. Stage all doc changes: `git add .prizm-docs/`
+2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES from completed work into `.prizm-docs/`
+3. **Memory sedimentation** (feature sessions only): Sediment DECISIONS and interface conventions to platform memory file (`CLAUDE.md` for Claude Code, BOTH `CODEBUDDY.md` AND `memory/MEMORY.md` for CodeBuddy)
+4. Stage all doc changes: `git add .prizm-docs/`
 
 Doc maintenance pass condition (pipeline-enforced): `.prizm-docs/` changed in the final commit.
 
-### Phase 5: Commit
+### Phase 5: Session Status + Commit
 
-- Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
-- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
-- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
-
----
-
-## Step 3: Write Session Status
+**5a. Write preliminary session-status.json** (safety net — ensures pipeline sees a status file even if session terminates during commit):
 
 Write to: `{{SESSION_STATUS_PATH}}`
 
@@ -135,8 +152,8 @@ Write to: `{{SESSION_STATUS_PATH}}`
   "feature_id": "{{FEATURE_ID}}",
   "feature_slug": "{{FEATURE_SLUG}}",
   "exec_tier": 1,
-  "status": "<success|partial|failed|commit_missing|docs_missing>",
-  "completed_phases": [0, 1, 2, 3, 4, 5],
+  "status": "partial",
+  "completed_phases": [0, 1, 2, 3, 4],
   "current_phase": 5,
   "checkpoint_reached": "CP-2",
   "tasks_completed": 0,
@@ -150,23 +167,31 @@ Write to: `{{SESSION_STATUS_PATH}}`
     "context_snapshot_path": ".prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md",
     "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md"
   },
-  "git_commit": "<commit hash>",
-  "timestamp": "2026-03-04T10:00:00Z"
+  "git_commit": "",
+  "timestamp": "<current ISO timestamp>"
 }
 ```
 
-### Step 3.1: Final Clean Check (before exit)
+**5b. Commit** — Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
+
+**5c. Update session-status.json to success** — After commit succeeds, update `{{SESSION_STATUS_PATH}}`:
+- Set `"status": "success"`
+- Set `"completed_phases": [0, 1, 2, 3, 4, 5]`
+- Set `"git_commit": "<actual commit hash from git log -1 --format=%H>"`
+- Set `"timestamp": "<current ISO timestamp>"`
 
-After writing `session-status.json`, verify repository is clean:
+**5d. Final Clean Check** — Verify repository is clean:
 
 ```bash
 git status --short
 ```
 
-If any files remain (e.g. session-status.json), stage and create a follow-up commit:
+If any files remain, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
 
 ```bash
-git add -A
+git add <specific-file-1> <specific-file-2>
 git commit -m "chore({{FEATURE_ID}}): include session artifacts"
 ```
 
@@ -186,6 +211,7 @@ Re-check `git status --short` and ensure it is empty before exiting.
 - Tier 1: you handle everything directly — invoke skills yourself (no subagents needed for simple tasks)
 - MANDATORY skills: `/prizmkit-code-review`, `/prizmkit-retrospective`, `/prizmkit-committer` — never skip these
 - Build context-snapshot.md FIRST; use it throughout instead of re-reading files
-- ALWAYS write session-status.json before exiting
+- Session-status.json is written BEFORE commit (as partial), then updated to success AFTER commit — this prevents pipeline from treating a terminated session as crashed
 - `/prizmkit-committer` is mandatory — do NOT skip the commit phase, and do NOT replace it with manual git commit commands
 - Before exiting, `git status --short` must be empty
+- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`

package/bundled/dev-pipeline/templates/bootstrap-tier2.md

@@ -46,13 +46,35 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 If a subagent times out:
 1. `ls .prizmkit/specs/{{FEATURE_SLUG}}/` — check what exists
-2. Re-spawn with: `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for full context. Do NOT re-read individual source files."` + only remaining steps + `model: "lite"`
+2. Re-spawn with: `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for full context. Also read .prizmkit/specs/{{FEATURE_SLUG}}/agents/*.md for knowledge from previous agents. Do NOT re-read individual source files."` + only remaining steps + `model: "lite"`
 3. Max 2 retries. After 2 failures, complete the work yourself.
 
 ---
 
 ## Execution
 
+### Phase 0.5: Agent Knowledge Setup
+
+Create the agent knowledge directory and initialize your own knowledge doc:
+```bash
+mkdir -p .prizmkit/specs/{{FEATURE_SLUG}}/agents
+```
+
+Write `.prizmkit/specs/{{FEATURE_SLUG}}/agents/orchestrator.md`:
+```markdown
+# Orchestrator
+
+## FINDINGS
+
+## DECISIONS
+
+## INTERFACES_DISCOVERED
+
+## CONTEXT_BUILT
+```
+
+After each phase, append notable DECISIONS/FINDINGS to your `agents/orchestrator.md`.
+
 {{IF_INIT_NEEDED}}
 ### Phase 0: Project Bootstrap
 - Run `/prizmkit-init` (invoke the prizmkit-init skill)
@@ -106,7 +128,8 @@ Prompt:
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — all project context, source files, and tests are embedded there.
 > 2. Read `.prizmkit/specs/{{FEATURE_SLUG}}/plan.md` (including Tasks section).
 > 3. Implement task-by-task using TDD. Mark each task `[x]` in plan.md Tasks section immediately after completion.
-> 4. After ALL tasks complete, append an 'Implementation Log' section to `context-snapshot.md`:
+> 4. **Agent Knowledge Doc**: Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-1.md`. After each task, append FINDINGS/DECISIONS/INTERFACES_DISCOVERED if you discovered anything notable. If context-snapshot.md was MISSING, write CONTEXT_BUILT entries after scanning source files.
+> 5. After ALL tasks complete, append an 'Implementation Log' section to `context-snapshot.md`:
 >    - Files created/modified (with paths)
 >    - Key implementation decisions
 >    - Any deviations from plan.md
@@ -127,10 +150,12 @@ Prompt:
 >    - Section 1: acceptance criteria to verify against
 >    - Section 4: original source files (before changes)
 >    - 'Implementation Log': what Dev changed
-> 2. Run prizmkit-code-review: verify all acceptance criteria, check code quality and correctness. Only read files mentioned in the Implementation Log.
-> 3. Run the test suite and report results.
-> 4. Append a 'Review Notes' section to `context-snapshot.md`: issues found (severity), test results, final verdict.
-> 5. If review uncovers durable pitfalls or conventions, add corresponding TRAPS/RULES notes to relevant `.prizm-docs/` files.
+> 2. Read `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-*.md` (if exists) — understand Dev's implementation decisions and trade-offs.
+> 3. Run prizmkit-code-review: verify all acceptance criteria, check code quality and correctness. Only read files mentioned in the Implementation Log.
+> 4. Run the test suite and report results.
+> 5. Append a 'Review Notes' section to `context-snapshot.md`: issues found (severity), test results, final verdict.
+> 6. **Agent Knowledge Doc**: Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/reviewer.md`. Write FINDINGS/DECISIONS after review (e.g., patterns discovered, quality issues, architectural observations).
+> 7. If review uncovers durable pitfalls or conventions, add corresponding TRAPS/RULES notes to relevant `.prizm-docs/` files.
 > Report verdict: PASS, PASS_WITH_WARNINGS, or NEEDS_FIXES."
 
 Wait for Reviewer to return.
@@ -138,24 +163,19 @@ Wait for Reviewer to return.
 
 **CP-2**: Tests pass, verdict is not NEEDS_FIXES.
 
-### Phase 4.5: Memory Maintenance (mandatory before commit)
+### Phase 4.5: Architecture Sync & Memory Sedimentation (mandatory before commit)
 
-Run `/prizmkit-retrospective` — the **sole maintainer** of `.prizm-docs/`:
+Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index) and platform memory files:
 1. **Structural sync**: Use `git diff --cached --name-status` to locate changed modules, update KEY_FILES/INTERFACES/DEPENDENCIES/file counts in affected `.prizm-docs/` files
-2. **Knowledge injection** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizm-docs/`
-3. Stage all doc changes: `git add .prizm-docs/`
+2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES from completed work into `.prizm-docs/`
+3. **Memory sedimentation** (feature sessions only): Sediment DECISIONS and interface conventions to platform memory file (`CLAUDE.md` for Claude Code, BOTH `CODEBUDDY.md` AND `memory/MEMORY.md` for CodeBuddy)
+4. Stage all doc changes: `git add .prizm-docs/`
 
 Doc maintenance pass condition (pipeline-enforced): `.prizm-docs/` changed in the final commit.
 
-### Phase 5: Commit
+### Phase 5: Session Status + Commit
 
-- Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
-- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
-- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
-
----
-
-## Step 3: Write Session Status
+**5a. Write preliminary session-status.json** (safety net — ensures pipeline sees a status file even if session terminates during commit):
 
 Write to: `{{SESSION_STATUS_PATH}}`
 
@@ -165,8 +185,8 @@ Write to: `{{SESSION_STATUS_PATH}}`
   "feature_id": "{{FEATURE_ID}}",
   "feature_slug": "{{FEATURE_SLUG}}",
   "exec_tier": 2,
-  "status": "<success|partial|failed|commit_missing|docs_missing>",
-  "completed_phases": [0, 1, 2, 3, 4, 5],
+  "status": "partial",
+  "completed_phases": [0, 1, 2, 3, 4],
   "current_phase": 5,
   "checkpoint_reached": "CP-2",
   "tasks_completed": 0,
@@ -180,23 +200,31 @@ Write to: `{{SESSION_STATUS_PATH}}`
     "context_snapshot_path": ".prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md",
     "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md"
   },
-  "git_commit": "<commit hash>",
-  "timestamp": "2026-03-04T10:00:00Z"
+  "git_commit": "",
+  "timestamp": "<current ISO timestamp>"
 }
 ```
 
-### Step 3.1: Final Clean Check (before exit)
+**5b. Commit** — Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
+
+**5c. Update session-status.json to success** — After commit succeeds, update `{{SESSION_STATUS_PATH}}`:
+- Set `"status": "success"`
+- Set `"completed_phases": [0, 1, 2, 3, 4, 5]`
+- Set `"git_commit": "<actual commit hash from git log -1 --format=%H>"`
+- Set `"timestamp": "<current ISO timestamp>"`
 
-After writing `session-status.json`, verify repository is clean:
+**5d. Final Clean Check** — Verify repository is clean:
 
 ```bash
 git status --short
 ```
 
-If any files remain (e.g. session-status.json), stage and create a follow-up commit:
+If any files remain, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
 
 ```bash
-git add -A
+git add <specific-file-1> <specific-file-2>
 git commit -m "chore({{FEATURE_ID}}): include session artifacts"
 ```
 
@@ -218,7 +246,8 @@ Re-check `git status --short` and ensure it is empty before exiting.
 - Tier 2: orchestrator builds context+plan, Dev implements, Reviewer reviews — use direct Agent spawn for agents
 - Build context-snapshot.md FIRST; all subagents read it instead of re-reading source files
 - Do NOT use `run_in_background=true` when spawning subagents
-- ALWAYS write session-status.json before exiting
+- Session-status.json is written BEFORE commit (as partial), then updated to success AFTER commit — this prevents pipeline from treating a terminated session as crashed
 - `/prizmkit-committer` is mandatory, and must not be replaced with manual git commit commands
 - Before exiting, `git status --short` must be empty
+- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`
 - On timeout: check snapshot → model:lite → remaining steps only → max 2 retries → orchestrator fallback

package/bundled/dev-pipeline/templates/bootstrap-tier3.md

@@ -85,13 +85,36 @@ LLM context is frozen at prompt time. Modifying a skill source file during this
 
 If any agent times out:
 1. `ls .prizmkit/specs/{{FEATURE_SLUG}}/` — check what exists
-2. If `context-snapshot.md` exists: open recovery prompt with `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for full context. Do NOT re-read individual source files."` + only remaining steps + `model: "lite"`
+2. If `context-snapshot.md` exists: open recovery prompt with `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for full context. Also read .prizmkit/specs/{{FEATURE_SLUG}}/agents/*.md for knowledge from previous agents. Do NOT re-read individual source files."` + only remaining steps + `model: "lite"`
 3. Max 2 retries per phase. After 2 failures, orchestrator completes the work directly and appends a Recovery Note to context-snapshot.md.
 
 ---
 
 ## Execution
 
+### Phase 0.5: Agent Knowledge Setup
+
+Create the agent knowledge directory and initialize your own knowledge doc:
+```bash
+mkdir -p .prizmkit/specs/{{FEATURE_SLUG}}/agents
+```
+
+Write `.prizmkit/specs/{{FEATURE_SLUG}}/agents/orchestrator.md`:
+```markdown
+# Orchestrator
+
+## FINDINGS
+
+## DECISIONS
+
+## INTERFACES_DISCOVERED
+
+## CONTEXT_BUILT
+```
+
+After each phase, append notable DECISIONS/FINDINGS to your `agents/orchestrator.md`.
+When spawning multiple Dev agents, each writes its own `agents/dev-{N}.md` (e.g., `dev-1.md`, `dev-2.md`).
+
 {{IF_INIT_NEEDED}}
 ### Phase 0: Project Bootstrap
 - Run `/prizmkit-init` (invoke the prizmkit-init skill)
@@ -191,6 +214,7 @@ Prompt:
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — all source files and project context are there. Do NOT re-read individual source files.
 > 2. Run prizmkit-analyze: cross-check `spec.md` and `plan.md` (including Tasks section) for consistency.
 > 3. Before flagging CRITICAL or HIGH issues, verify each against Section 4 of the snapshot. Do NOT report based on incomplete information.
+> 4. **Agent Knowledge Doc**: Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/reviewer.md`. Write FINDINGS/DECISIONS after analysis (e.g., consistency issues found, ambiguities identified).
 > Report: CRITICAL, HIGH, MEDIUM issues found (or 'No issues found')."
 
 Wait for Reviewer to return.
@@ -228,9 +252,10 @@ Prompt:
 > 2. Read `plan.md` (including Tasks section) from `.prizmkit/specs/{{FEATURE_SLUG}}/`.
 > 3. Implement task-by-task. Mark each `[x]` in plan.md Tasks section **immediately** after completion (do NOT batch).
 > 4. Use `TEST_CMD=<TEST_CMD>` to run tests — do NOT explore alternative test commands.
-> 5. After ALL tasks done, append 'Implementation Log' to context-snapshot.md: files changed/created, key decisions, deviations from plan.
-> 6. Do NOT execute any git commands (no git add/commit/reset/push).
-> 7. If `<TEST_CMD>` shows failures, check against BASELINE_FAILURES=`<BASELINE_FAILURES>`. Failures present in the baseline are pre-existing — list them explicitly in your COMPLETION_SIGNAL.
+> 5. **Agent Knowledge Doc**: Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-1.md`. After each task, append FINDINGS/DECISIONS/INTERFACES_DISCOVERED if you discovered anything notable. If context-snapshot.md was MISSING, read `agents/*.md` from other agents first, then scan source files and write CONTEXT_BUILT entries.
+> 6. After ALL tasks done, append 'Implementation Log' to context-snapshot.md: files changed/created, key decisions, deviations from plan.
+> 7. Do NOT execute any git commands (no git add/commit/reset/push).
+> 8. If `<TEST_CMD>` shows failures, check against BASELINE_FAILURES=`<BASELINE_FAILURES>`. Failures present in the baseline are pre-existing — list them explicitly in your COMPLETION_SIGNAL.
 > Do NOT exit until all tasks are [x] and the Implementation Log is written."
 
 Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
@@ -238,10 +263,12 @@ Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
 2. If any tasks remain: re-spawn Dev with this recovery prompt:
    > "Read {{DEV_SUBAGENT_PATH}}. You are resuming implementation of feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
    > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — Section 4 has original source, 'Implementation Log' (if present) has what was already done. Do NOT re-read individual source files.
-   > 2. Read plan.md Tasks section — complete ONLY the remaining `[ ]` tasks. Do NOT redo completed `[x]` tasks.
-   > 3. Use `TEST_CMD=<TEST_CMD>` to run tests.
-   > 4. Append progress to 'Implementation Log' in context-snapshot.md.
-   > 5. Do NOT execute any git commands."
+   > 2. Read `.prizmkit/specs/{{FEATURE_SLUG}}/agents/*.md` — knowledge from previous agents (context, decisions, interfaces).
+   > 3. Read plan.md Tasks section — complete ONLY the remaining `[ ]` tasks. Do NOT redo completed `[x]` tasks.
+   > 4. Use `TEST_CMD=<TEST_CMD>` to run tests.
+   > 5. Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-1.md` — append FINDINGS/DECISIONS as you work.
+   > 6. Append progress to 'Implementation Log' in context-snapshot.md.
+   > 7. Do NOT execute any git commands."
 3. Max 2 recovery retries. After 2 failures, orchestrator implements remaining tasks directly.
 
 All tasks `[x]`, tests pass.
@@ -267,19 +294,23 @@ Prompt:
 > **IMPORTANT**: Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST.
 > This file contains ALL source code and context. Do NOT re-read individual source files.
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — Section 4 has original source files, 'Implementation Log' section lists exactly what Dev changed. Do NOT re-read source files that are NOT mentioned in the Implementation Log.
-> 2. Run prizmkit-code-review: spec compliance (against spec.md), code quality, correctness. Read ONLY files listed in Implementation Log.
-> 3. Write and execute integration tests covering all user stories from spec.md. Use `TEST_CMD=<TEST_CMD>` — do NOT try alternative test commands.
-> 4. Append 'Review Notes' to context-snapshot.md: issues (severity), test results, final verdict.
+> 2. Read `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-*.md` (if exists) — understand Dev's implementation decisions, trade-offs, and discovered interfaces.
+> 3. Run prizmkit-code-review: spec compliance (against spec.md), code quality, correctness. Read ONLY files listed in Implementation Log.
+> 4. Write and execute integration tests covering all user stories from spec.md. Use `TEST_CMD=<TEST_CMD>` — do NOT try alternative test commands.
+> 5. Append 'Review Notes' to context-snapshot.md: issues (severity), test results, final verdict.
+> 6. **Agent Knowledge Doc**: Maintain `.prizmkit/specs/{{FEATURE_SLUG}}/agents/reviewer.md`. Write FINDINGS/DECISIONS after review (e.g., quality patterns, architectural observations).
 > Report verdict: PASS, PASS_WITH_WARNINGS, or NEEDS_FIXES."
 
 Wait for Reviewer to return.
 - If NEEDS_FIXES: spawn Dev to fix with this prompt:
   > "Read {{DEV_SUBAGENT_PATH}}. Fix NEEDS_FIXES issues for feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
   > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — 'Review Notes' section lists the exact issues to fix. Do NOT re-read source files not mentioned there.
-  > 2. Fix ONLY the issues listed in 'Review Notes'. Do NOT refactor unrelated code.
-  > 3. Use `TEST_CMD=<TEST_CMD>` to verify fixes.
-  > 4. Append fix summary to 'Implementation Log' in context-snapshot.md.
-  > 5. Do NOT execute any git commands."
+  > 2. Read `.prizmkit/specs/{{FEATURE_SLUG}}/agents/reviewer.md` (if exists) — understand reviewer's findings and rationale.
+  > 3. Fix ONLY the issues listed in 'Review Notes'. Do NOT refactor unrelated code.
+  > 4. Use `TEST_CMD=<TEST_CMD>` to verify fixes.
+  > 5. Append fix summary to 'Implementation Log' in context-snapshot.md.
+  > 6. Update `.prizmkit/specs/{{FEATURE_SLUG}}/agents/dev-1.md` with any new FINDINGS/DECISIONS from the fix.
+  > 7. Do NOT execute any git commands."
   Then re-run Review (max 3 rounds).
 
 **CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.
@@ -317,21 +348,14 @@ git log --oneline | grep "{{FEATURE_ID}}" | head -3
 - If a commit for `{{FEATURE_ID}}` already exists → **skip 7c** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to Step 3.
 - If no existing commit → proceed normally with 7a–7c.
 
-**7b.** Run `/prizmkit-retrospective` (**before commit**, the sole maintainer of `.prizm-docs/`):
+**7b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizm-docs/` architecture index and platform memory files):
 - **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
-- **Knowledge injection** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work
+- **Architecture knowledge** (feature sessions only): extract TRAPS, RULES from completed work into `.prizm-docs/`
+- **Memory sedimentation** (feature sessions only): sediment DECISIONS and interface conventions to platform memory file (`CLAUDE.md` for Claude Code, BOTH `CODEBUDDY.md` AND `memory/MEMORY.md` for CodeBuddy)
 - Stage all doc changes: `git add .prizm-docs/`
-- **For bug-fix sessions**: structural sync only, skip knowledge injection unless a genuinely new pitfall was discovered
-
-**7c.** Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
-
-**7d.** MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+- **For bug-fix sessions**: structural sync only, skip knowledge injection and memory sedimentation unless a genuinely new pitfall was discovered
 
-**7e.** Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
-
----
-
-## Step 3: Write Session Status
+**7b-safety.** Write preliminary session-status.json (safety net — ensures pipeline sees a status file even if session terminates during commit):
 
 Write to: `{{SESSION_STATUS_PATH}}`
 
@@ -341,8 +365,8 @@ Write to: `{{SESSION_STATUS_PATH}}`
   "feature_id": "{{FEATURE_ID}}",
   "feature_slug": "{{FEATURE_SLUG}}",
   "exec_tier": 3,
-  "status": "<success|partial|failed|commit_missing|docs_missing>",
-  "completed_phases": [0, 1, 2, 3, 4, 5, 6],
+  "status": "partial",
+  "completed_phases": [0, 1, 2, 3, 4, 5],
   "current_phase": 6,
   "checkpoint_reached": "CP-3",
   "tasks_completed": 0,
@@ -357,23 +381,43 @@ Write to: `{{SESSION_STATUS_PATH}}`
     "spec_path": ".prizmkit/specs/{{FEATURE_SLUG}}/spec.md",
     "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md"
   },
-  "git_commit": "<commit hash>",
-  "timestamp": "2026-03-04T10:00:00Z"
+  "git_commit": "",
+  "timestamp": "<current ISO timestamp>"
 }
 ```
 
+**7c.** Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+
+**7d.** MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+
+**7e.** Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
+
+---
+
+## Step 3: Commit & Finalize Session Status
+
+**3a. Commit** — The commit was handled in Phase 6 (7c) above via `/prizmkit-committer`.
+
+**3b. Update session-status.json to success** — After commit succeeds, update `{{SESSION_STATUS_PATH}}`:
+
+Update the file to reflect final success:
+- Set `"status": "success"`
+- Set `"completed_phases": [0, 1, 2, 3, 4, 5, 6]`
+- Set `"git_commit": "<actual commit hash from git log -1 --format=%H>"`
+- Set `"timestamp": "<current ISO timestamp>"`
+
 ### Step 3.1: Final Clean Check (before exit)
 
-After writing `session-status.json`, verify repository is clean:
+After updating `session-status.json`, verify repository is clean:
 
 ```bash
 git status --short
 ```
 
-If any files remain (e.g. session-status.json), stage and create a follow-up commit:
+If any files remain, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
 
 ```bash
-git add -A
+git add <specific-file-1> <specific-file-2>
 git commit -m "chore({{FEATURE_ID}}): include session artifacts"
 ```
 
@@ -397,7 +441,8 @@ Re-check `git status --short` and ensure it is empty before exiting.
 - Tier 3: full team — Dev (implementation) → Reviewer (review) — spawn agents directly via Agent tool
 - context-snapshot.md is the team knowledge base: orchestrator writes it once, all agents read it
 - Do NOT use `run_in_background=true` when spawning agents
-- ALWAYS write session-status.json before exiting
+- ALWAYS write preliminary session-status.json BEFORE commit (as partial), then update to success AFTER commit — this prevents pipeline from treating a terminated session as crashed
 - Commit phase must use `/prizmkit-committer`; do NOT replace with manual git commit commands
 - Before exiting, `git status --short` must be empty
+- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`
 - On timeout: check snapshot → model:lite → remaining steps only → max 2 retries → orchestrator fallback

package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md

@@ -86,7 +86,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 ### Step 2: Pipeline Phases
 
-#### Phase 1: Triage — 分诊分类
+#### Phase 1: Triage — Classification
 
 **Goal**: Classify the bug, identify scope and severity, check known issues, produce fix-plan.md.
 
@@ -123,7 +123,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 ---
 
-#### Phase 2: Reproduce — 复现确认
+#### Phase 2: Reproduce — Reproduction Confirmation
 
 **Goal**: Create an automated reproduction that proves the bug exists.
 
@@ -145,7 +145,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 ---
 
-#### Phase 3: Fix — 修复实现
+#### Phase 3: Fix — Implementation
 
 **Goal**: Implement the fix. The reproduction test goes from red to green.
 
@@ -167,7 +167,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 ---
 
-#### Phase 4: Verify — 代码审查与回归验证
+#### Phase 4: Verify — Code Review & Regression Verification
 
 **Goal**: Ensure fix correctness and no regressions.
 
@@ -196,7 +196,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 ---
 
-#### Phase 5: Commit & Learn — 提交与知识积累
+#### Phase 5: Commit & Learn — Commit & Knowledge Capture
 
 **Goal**: Commit the fix, update TRAPS, generate fix-report.md.