prizmkit 1.1.99 → 1.1.100

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

@@ -12,7 +12,7 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 **CRITICAL**: You MUST NOT exit until ALL work is complete and committed.
 
-**Tier 1 — Single Agent**: You handle everything directly. No normal work subagents; the log-size monitor is the only allowed persistent background subagent. No TeamCreate.
+**Tier 1 — Single Agent**: You handle everything directly. No normal work subagents. No TeamCreate.
 
 ### Feature Description
 
@@ -145,7 +145,7 @@ You know this project's tech stack. Identify ALL test commands that apply (e.g.,
 - Runs tests using `TEST_CMD` after each task
 - Writes '## Implementation Log' to `context-snapshot.md`
 
-**3b-compact.** Context management — if plan.md has more than 5 tasks, run `/compact` after completing every 3 tasks during implementation. This prevents context window exhaustion in long sessions. If `/compact` is not available (non-Claude CLI), skip this step.
+**3b-checkpoint.** Context management — if plan.md has more than 5 tasks, update durable checkpoints/artifacts after every 3 tasks, minimize output, and continue. If context overflow occurs in a headless run, the runner starts a fresh continuation session from those checkpoints and artifacts. In an interactive Claude Code session operated manually outside the headless pipeline, `/compact` may be used as an optional convenience only.
 
 **3c.** After implement completes, verify:
 1. All tasks in plan.md are `[x]`

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

@@ -10,7 +10,7 @@
 
 You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATURE_TITLE}}".
 
-**CRITICAL**: You MUST NOT exit until ALL work is complete and committed. When you spawn normal work subagents, wait for each to finish (run_in_background=false). The log-size monitor is the only allowed persistent background subagent.
+**CRITICAL**: You MUST NOT exit until ALL work is complete and committed. When you spawn normal work subagents, wait for each to finish (run_in_background=false).
 
 **Tier 2 — Dual Agent**: You handle context + planning directly. Then spawn Dev and Reviewer subagents. Spawn Dev and Reviewer agents via the Agent tool.
 
@@ -276,7 +276,7 @@ Prompt:
 > ⚠️ DO NOT re-read source files already listed in Section 4 File Manifest unless you need implementation detail beyond the interface summary.
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full context.
 > 2. Run `/prizmkit-implement` to execute the tasks in plan.md. Run tests with: `{{TEST_CMD}}`. Known baseline failures (pre-existing, not your fault): `{{BASELINE_FAILURES}}`.
-> 3. If plan.md has more than 5 tasks: run `/compact` after completing every 3 tasks to manage context budget. If `/compact` is unavailable, continue without it.
+> 3. If plan.md has more than 5 tasks: update durable checkpoints/artifacts after every 3 tasks, minimize output, and rely on runner continuation if context overflow occurs. In an interactive Claude Code session operated manually outside the headless pipeline, `/compact` may be used as an optional convenience only.
 > 4. After implement completes, verify the '## Implementation Log' section was written to context-snapshot.md.
 > 5. Do NOT execute any git commands (no git add/commit/reset/push).
 > Do NOT exit until all tasks are [x] and the '## Implementation Log' section is written in context-snapshot.md."
@@ -604,7 +604,7 @@ If you encounter an unrecoverable error, context overflow, or are about to exit
 - Build context-snapshot.md FIRST; all subagents read it instead of re-reading source files
 - context-snapshot.md is append-only: orchestrator writes Sections 1-4, Dev appends Implementation Log, Reviewer appends Review Notes
 - Gate checks enforce Implementation Log and Review Notes are written before proceeding
-- Do NOT use `run_in_background=true` when spawning normal work subagents; the log-size monitor is the only allowed persistent background subagent
+- Do NOT use `run_in_background=true` when spawning normal work subagents
 - **NEVER delete, modify, or touch any file under `.prizmkit/state/`** — those are pipeline runtime files managed by the runner
 - NEVER run `rm -rf`, `git clean`, or any destructive filesystem operations
 - `/prizmkit-committer` is mandatory, and must not be replaced with manual git commit commands

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

@@ -10,7 +10,7 @@
 
 You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATURE_TITLE}}".
 
-**CRITICAL**: You MUST NOT exit until ALL work is complete and committed. When you spawn normal work subagents, wait for each to finish (run_in_background=false). The log-size monitor is the only allowed persistent background subagent. Do NOT spawn work agents in background and exit — that kills the session.
+**CRITICAL**: You MUST NOT exit until ALL work is complete and committed. When you spawn normal work subagents, wait for each to finish (run_in_background=false). Do NOT spawn work agents in background and exit — that kills the session.
 
 **Tier 3 — Full Team**: For complex features, use the full pipeline (Phase 0–6) with Dev + Reviewer agents spawned via the Agent tool.
 
@@ -284,7 +284,7 @@ Prompt:
 > ⚠️ DO NOT re-read source files already listed in Section 4 File Manifest unless you need implementation detail beyond the interface summary.
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full context.
 > 2. Run `/prizmkit-implement` to execute the tasks in plan.md. Run tests with: `{{TEST_CMD}}`. Known baseline failures (pre-existing, not your fault): `{{BASELINE_FAILURES}}`.
-> 3. If plan.md has more than 5 tasks: run `/compact` after completing every 3 tasks to manage context budget. If `/compact` is unavailable, continue without it.
+> 3. If plan.md has more than 5 tasks: update durable checkpoints/artifacts after every 3 tasks, minimize output, and rely on runner continuation if context overflow occurs. In an interactive Claude Code session operated manually outside the headless pipeline, `/compact` may be used as an optional convenience only.
 > 4. After implement completes, verify the '## Implementation Log' section was written to context-snapshot.md.
 > 5. Do NOT execute any git commands (no git add/commit/reset/push).
 > Do NOT exit until all tasks are [x] and the '## Implementation Log' section is written in context-snapshot.md."
@@ -638,7 +638,7 @@ If you encounter an unrecoverable error, context overflow, or are about to exit
 - Tier 3: full team — Dev (implementation) → Reviewer (review) — spawn agents directly via Agent tool
 - context-snapshot.md is append-only: orchestrator writes Sections 1-4, Dev appends Implementation Log, Reviewer appends Review Notes
 - Gate checks enforce Implementation Log and Review Notes are written before proceeding
-- Do NOT use `run_in_background=true` when spawning normal work agents; the log-size monitor is the only allowed persistent background subagent
+- Do NOT use `run_in_background=true` when spawning normal work agents
 - Commit phase must use `/prizmkit-committer`; do NOT replace with manual git commit commands
 - **NEVER delete, modify, or touch any file under `.prizmkit/state/`** — those are pipeline runtime files managed by the runner
 - NEVER run `rm -rf`, `git clean`, or any destructive filesystem operations

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

@@ -13,7 +13,7 @@ You are the **bug fix session agent**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}".
 
 **CRITICAL**: You MUST NOT exit until ALL work is complete and committed.
 
-**SUBAGENT LIFECYCLE**: The log-size monitor is the only allowed persistent background subagent. Any normal work subagent must be awaited with `run_in_background=false`.
+**SUBAGENT LIFECYCLE**: Any normal work subagent must be awaited with `run_in_background=false`. Do not spawn persistent background subagents for headless recovery.
 
 **NON-INTERACTIVE MODE**: There is NO human on the other end. NEVER ask for user confirmation, NEVER wait for user input. Make decisions autonomously and move forward.
 

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

@@ -12,7 +12,7 @@
 
 You are the **refactor session orchestrator**. Execute Refactor {{REFACTOR_ID}}: "{{REFACTOR_TITLE}}".
 
-**CRITICAL SESSION LIFECYCLE RULE**: You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn normal work subagents, you MUST **wait for each to finish** (run_in_background=false) before proceeding. The log-size monitor is the only allowed persistent background subagent. Do NOT spawn a work agent in the background and exit — that kills the session.
+**CRITICAL SESSION LIFECYCLE RULE**: You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn normal work subagents, you MUST **wait for each to finish** (run_in_background=false) before proceeding. Do NOT spawn a work agent in the background and exit — that kills the session.
 
 **NON-INTERACTIVE MODE**: You are running in headless non-interactive mode. There is NO human on the other end. NEVER ask for user confirmation, NEVER wait for user input, NEVER use interactive prompts (e.g. "Would you like me to…"). If a skill has an interactive step (e.g. offer remediation, ask for approval), skip it and proceed autonomously. Make decisions based on the data available and move forward.
 
@@ -185,7 +185,7 @@ Evidence must cover affected UI render, primary user interactions, behavior-sens
 
 {{END_IF_BROWSER_INTERACTION}}
 
-  7. If the refactor involves multiple files: run `/compact` after completing half the tasks to free context budget. If `/compact` is unavailable, continue without it.
+  7. If the refactor involves multiple files: update durable checkpoints/artifacts at the midpoint, minimize output, and rely on runner continuation if context overflow occurs. In an interactive Claude Code session operated manually outside the headless pipeline, `/compact` may be used as an optional convenience only.
   8. After all tasks complete, run the full test suite one final time
   "
 - **Wait for Dev to return**
@@ -337,4 +337,4 @@ Write to: `{{SESSION_STATUS_PATH}}`
 - **Commit with** `refactor(<scope>):` prefix, NOT `feat:` or `fix:`
 - **Run full retrospective** (Job 1 + Job 2) — refactoring changes code structure
 - ALWAYS write session-status.json before exiting
-- Do NOT use `run_in_background=true` when spawning normal work agents; the log-size monitor is the only allowed persistent background subagent
+- Do NOT use `run_in_background=true` when spawning normal work agents

package/bundled/dev-pipeline/templates/sections/log-size-awareness.md

@@ -1,76 +1,41 @@
-## Session Log Budget Monitoring (PROACTIVE)
+## Session Log Budget Awareness (CHECKPOINT GUIDANCE)
 
-Your session log grows with every tool call and subagent spawn.
-To prevent context exhaustion, **spawn a background monitoring subagent at session start**.
+Your session log grows with every tool call and agent interaction. Use this
+section as passive checkpoint guidance only; do not spawn a background helper for
+log-size checks.
 
-### How to Set Up the Monitor
+### Checkpoint Before Large Work Batches
 
-1. **AS THE VERY FIRST ACTION** (before Phase 0), spawn a monitoring subagent
-   with `run_in_background: true` and this task:
+- `MAX_LOG_SIZE` controls whether this advisory section is included. It is not a
+  runtime recovery mechanism.
+- Before major phases or large task batches, update durable artifacts that a
+  continuation session can trust: plan/task checkboxes, context snapshots,
+  implementation or review notes, workflow checkpoints, session status, and test
+  reports where applicable.
+- Keep command output small. Capture large outputs to temporary files and read
+  only filtered summaries needed for the current decision.
+- Prefer already-built context snapshots and manifests over broad source-file
+  re-reads.
 
-   ```
-   Run this command and keep it running:
-   bash {{LOG_MONITOR_SCRIPT}} {{SESSION_LOG_PATH}} {{MAX_LOG_SIZE}} {{LOG_MONITOR_POLL_INTERVAL}} {{LOG_MONITOR_STATUS_FILE}} {{LOG_MONITOR_BASELINE_FILE}}
-   ```
+### Headless Recovery Source of Truth
 
-   The subagent MUST use `run_in_background: true`. It writes a JSON status
-   file every {{LOG_MONITOR_POLL_INTERVAL}} seconds.
+- Headless recovery must rely on durable checkpoints and artifacts, not an
+  interactive slash command.
+- If context overflow still occurs, the runner detects the overflow and starts a
+  fresh continuation session from checkpoint files and durable artifacts.
+- Durable checkpoint files and artifacts are the source of truth for what was
+  completed, what remains, and the tests or review gates already run.
 
-2. **BEFORE EACH MAJOR PHASE** (Phase 0, 1, 2, ...), read the status:
+### Interactive Claude Code Note
 
-   ```bash
-   cat {{LOG_MONITOR_STATUS_FILE}} 2>/dev/null || echo '{"status":"OK"}'
-   ```
-
-   The status file contains structured diagnostics:
-
-   ```json
-   {
-     "status": "OK | COMPACT_NEEDED",
-     "total_bytes": <current session.log size>,
-     "baseline_bytes": <size after last /compact>,
-     "effective_bytes": <total - baseline, incremental growth>,
-     "threshold_bytes": <{{MAX_LOG_SIZE}}>,
-     "overage_bytes": <effective - threshold, 0 when OK>,
-     "usage_pct": <effective / threshold * 100>
-   }
-   ```
-
-   Extract fields for decision-making:
-   ```bash
-   status=$(jq -r '.status' {{LOG_MONITOR_STATUS_FILE}})
-   effective=$(jq -r '.effective_bytes' {{LOG_MONITOR_STATUS_FILE}})
-   overage=$(jq -r '.overage_bytes' {{LOG_MONITOR_STATUS_FILE}})
-   usage=$(jq -r '.usage_pct' {{LOG_MONITOR_STATUS_FILE}})
-   ```
-
-3. **On COMPACT_NEEDED** (effective_bytes > {{MAX_LOG_SIZE}} bytes, {{MAX_LOG_SIZE_HUMAN}}):
-   - Check `overage_bytes` to decide urgency:
-     - **Minor overage** (< 512KB): complete the current sub-step, update durable workflow checkpoint artifacts, write baseline, `/compact`
-     - **Major overage** (>= 512KB): update durable workflow checkpoint artifacts, write baseline, `/compact` — do NOT start new work
-   - Write baseline before `/compact`:
-     ```bash
-     wc -c < {{SESSION_LOG_PATH}} > {{LOG_MONITOR_BASELINE_FILE}}
-     ```
-   - Execute `/compact`
-   - Continue the workflow after `/compact`; re-read this status file before the next major phase
-
-### How the Baseline Prevents Infinite Compaction Loops
-
-- Before the first `/compact`: baseline = 0, effective = full log size → triggers when log exceeds threshold
-- After `/compact`: baseline = current log size, effective ≈ 0 → status resets to OK
-- The monitor only triggers again when **new** log growth since the last compact exceeds the threshold
-- Each `/compact` resets the baseline, breaking the infinite loop
+- `/compact` may help when a human is manually operating an interactive Claude
+  Code session.
+- `/compact` is optional interactive convenience only. It must not be required
+  for headless recovery and must not be delegated to a background helper.
 
 ### Log Growth Reduction Tips
 
-- **Re-read context-snapshot.md instead of source files** — already in context
-- **Filter command output** — pipe to `tail -20` or `grep`, never full output
-- **Limit subagent prompts** — shorter, focused prompts = shorter transcripts
-- **Checkpoint often** — update durable workflow checkpoint artifacts before `/compact`
-
-### What Survives
-
-- All git commits are permanent
-- The workflow checkpoint is preserved and auto-resumed
-- `/compact` compresses context without losing progress
+- Reuse context-snapshot.md instead of re-reading files already summarized there.
+- Filter command output before loading it into context.
+- Keep agent prompts focused and avoid unnecessary transcript expansion.
+- Checkpoint often so automatic continuation can resume from durable state.

package/bundled/dev-pipeline/templates/session-status-schema.json

@@ -15,7 +15,7 @@
     },
     "status": {
       "type": "string",
-      "enum": ["success", "partial", "failed", "commit_missing", "docs_missing", "merge_conflict"]
+      "enum": ["success", "partial", "failed", "commit_missing", "docs_missing", "merge_conflict", "context_overflow"]
     },
     "completed_phases": {
       "type": "array",

package/bundled/dev-pipeline/tests/conftest.py

@@ -24,5 +24,6 @@ def _load_hyphenated_module(module_name, filename):
 # Register hyphenated script files so tests can import them with underscores.
 _load_hyphenated_module("generate_bootstrap_prompt", "generate-bootstrap-prompt.py")
 _load_hyphenated_module("generate_bugfix_prompt", "generate-bugfix-prompt.py")
+_load_hyphenated_module("generate_refactor_prompt", "generate-refactor-prompt.py")
 _load_hyphenated_module("prizmkit_test_gate", "prizmkit-test-gate.py")
 _load_hyphenated_module("update_feature_status", "update-feature-status.py")