prizmkit 1.0.110 → 1.0.112

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.110",
-  "bundledAt": "2026-03-26T02:24:41.453Z",
-  "bundledFrom": "9b18d27"
+  "frameworkVersion": "1.0.112",
+  "bundledAt": "2026-03-26T06:44:08.682Z",
+  "bundledFrom": "a59fa27"
 }

package/bundled/dev-pipeline/run.sh

@@ -218,7 +218,7 @@ spawn_and_wait_session() {
             uncommitted=$(git -C "$project_root" status --porcelain 2>/dev/null | head -1 || true)
             if [[ -n "$uncommitted" ]]; then
                 log_warn "Session exited cleanly but produced no commits (uncommitted changes found) — auto-committing..."
-                git -C "$project_root" add -A 2>/dev/null || true
+                git -C "$project_root" add -u 2>/dev/null || true
                 if git -C "$project_root" commit --no-verify -m "chore($feature_id): auto-commit session work" 2>/dev/null; then
                     log_info "Auto-commit succeeded"
                     session_status="success"
@@ -241,7 +241,7 @@ spawn_and_wait_session() {
             dirty_files=$(git -C "$project_root" status --porcelain 2>/dev/null || true)
             if [[ -n "$dirty_files" ]]; then
                 log_info "Auto-committing remaining session artifacts..."
-                git -C "$project_root" add -A 2>/dev/null || true
+                git -C "$project_root" add -u 2>/dev/null || true
                 git -C "$project_root" commit --no-verify --amend --no-edit -a 2>/dev/null \
                     || git -C "$project_root" commit --no-verify -m "chore($feature_id): include remaining session artifacts" 2>/dev/null \
                     || true
@@ -314,6 +314,12 @@ sys.exit(1)
         log_error "feature-list.json may be out of sync. Manual intervention needed."
     }
 
+    # Commit feature status update (pipeline management commit)
+    if ! git -C "$project_root" diff --quiet feature-list.json 2>/dev/null; then
+        git -C "$project_root" add feature-list.json
+        git -C "$project_root" commit --no-verify -m "chore($feature_id): update feature status" 2>/dev/null || true
+    fi
+
     # Return status via global variable (avoids $() swallowing stdout)
     _SPAWN_RESULT="$session_status"
 }

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

@@ -40,7 +40,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 3. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
 4. **One task at a time** — In Phase 3 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
-6. **Incremental commits when possible** — If a feature has multiple independent tasks, commit after each completed task rather than one big commit at the end.
+6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-3. All changes are committed once at the end in Phase 4 via `/prizmkit-committer`.
 7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
@@ -109,6 +109,13 @@ If plan.md missing, write it directly:
 
 ### Phase 3: Implement + Test
 
+**Build artifacts**: After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary or build directory is in `.gitignore`:
+```bash
+# Example for Go
+grep -q '^/binary-name$' .gitignore || echo '/binary-name' >> .gitignore
+```
+Never commit compiled binaries, build output, or generated artifacts.
+
 **Before starting**: detect the test command and record baseline:
 ```bash
 # Try in order, use first that exits 0
@@ -140,33 +147,31 @@ Files changed/created: [list]
 Key decisions: [list]
 ```
 
-### Phase 4: Architecture Sync & Commit
+### Phase 4: Architecture Sync & Commit (SINGLE COMMIT)
 
 **4a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):
 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. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizm-docs/`
-3. Stage all doc changes: `git add .prizm-docs/`
+3. Stage doc changes: `git add .prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
 
-Doc maintenance pass condition (pipeline-enforced): `.prizm-docs/` changed in the final commit.
+**4b.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```bash
+git add <specific-files-created-or-modified>
+git add .prizm-docs/
+```
 
-**4b. Commit** — Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+**4c.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .prizm-docs/ updates. 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.
 
-**4c. Final Clean Check** — Verify repository is clean:
-
+**4d.** Final verification:
 ```bash
 git status --short
 ```
-
-**Note**: The pipeline runner will auto-commit any remaining dirty files after your session exits. You do NOT need to manually commit pipeline state files (`dev-pipeline/state/`) or runtime logs — just focus on committing your feature code via `/prizmkit-committer`.
-
-If any feature-related source files remain uncommitted, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
-
-```bash
-git add <specific-file-1> <specific-file-2>
-git commit -m "chore({{FEATURE_ID}}): include session artifacts"
-```
+Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file> && git commit --amend --no-edit`, do NOT create a separate commit.
 
 ## Critical Paths
 
@@ -204,5 +209,6 @@ rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
 - MANDATORY skills: `/prizmkit-retrospective`, `/prizmkit-committer` — never skip these
 - Build context-snapshot.md FIRST; use it throughout instead of re-reading files
 - `/prizmkit-committer` is mandatory — do NOT skip the commit phase, and do NOT replace it with manual git commit commands
-- Before exiting, commit your feature code via `/prizmkit-committer` — the pipeline runner auto-commits any remaining files after session exit
-- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`
+- Do NOT run `git add`/`git commit` during Phase 1-3 — all changes are committed once in Phase 4
+- If any files remain after the commit, amend the existing commit — do NOT create a follow-up commit
+- When staging files, always use explicit file names — NEVER use `git add -A` or `git add .`

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

@@ -40,7 +40,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 3. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
 4. **One task at a time** — In Phase 3 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
-6. **Incremental commits when possible** — If a feature has multiple independent tasks, commit after each completed task rather than one big commit at the end.
+6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-4. All changes are committed once at the end in Phase 5 via `/prizmkit-committer`.
 7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
@@ -130,6 +130,8 @@ If either missing, write them yourself:
 
 ### Phase 3: Implement — Dev Subagent
 
+**Build artifacts rule** (passed to Dev): After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary or build directory is in `.gitignore`. Never commit compiled binaries, build output, or generated artifacts.
+
 Spawn Dev subagent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false).
 
 Prompt:
@@ -187,33 +189,31 @@ If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write the '#
 
 **CP-2**: Tests pass, verdict is not NEEDS_FIXES.
 
-### Phase 5: Architecture Sync & Commit
+### Phase 5: Architecture Sync & Commit (SINGLE COMMIT)
 
 **5a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):
 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. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizm-docs/`
-3. Stage all doc changes: `git add .prizm-docs/`
+3. Stage doc changes: `git add .prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
 
-Doc maintenance pass condition (pipeline-enforced): `.prizm-docs/` changed in the final commit.
+**5b.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```bash
+git add <specific-files-created-or-modified>
+git add .prizm-docs/
+```
 
-**5b. Commit** — Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
+**5c.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .prizm-docs/ updates. 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. Final Clean Check** — Verify repository is clean:
-
+**5d.** Final verification:
 ```bash
 git status --short
 ```
-
-**Note**: The pipeline runner will auto-commit any remaining dirty files after your session exits. You do NOT need to manually commit pipeline state files (`dev-pipeline/state/`) or runtime logs — just focus on committing your feature code via `/prizmkit-committer`.
-
-If any feature-related source files remain uncommitted, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
-
-```bash
-git add <specific-file-1> <specific-file-2>
-git commit -m "chore({{FEATURE_ID}}): include session artifacts"
-```
+Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file> && git commit --amend --no-edit`, do NOT create a separate commit.
 
 ## Critical Paths
 
@@ -255,6 +255,7 @@ rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
 - Gate checks enforce Implementation Log and Review Notes are written before proceeding
 - Do NOT use `run_in_background=true` when spawning subagents
 - `/prizmkit-committer` is mandatory, and must not be replaced with manual git commit commands
-- Before exiting, commit your feature code via `/prizmkit-committer` — the pipeline runner auto-commits any remaining files after session exit
-- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`
+- Do NOT run `git add`/`git commit` during Phase 1-4 — all changes are committed once in Phase 5
+- If any files remain after the commit, amend the existing commit — do NOT create a follow-up commit
+- When staging files, always use explicit file names — NEVER use `git add -A` or `git add .`
 - On timeout: check snapshot + git diff HEAD → model:lite → remaining steps only → max 2 retries per phase → orchestrator fallback

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

@@ -72,7 +72,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 3. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
 4. **One task at a time** — In Phase 4 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
-6. **Incremental commits when possible** — If a feature has multiple independent tasks, commit after each completed task rather than one big commit at the end.
+6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-5. All changes are committed once at the end in Phase 6 via `/prizmkit-committer`.
 7. **Batch independent operations** — Issue multiple independent `Write`/`Read` calls in a single message turn when they have no dependencies. Combine multiple `mkdir -p` into one command. Never run `npm test` twice just to apply a different grep filter — capture output to `/tmp/test-out.txt` once and grep the file.
 
 ---
@@ -231,6 +231,8 @@ Wait for Reviewer to return.
 
 ### Phase 4: Implement — Dev Agent
 
+**Build artifacts rule** (passed to Dev): After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary or build directory is in `.gitignore`. Never commit compiled binaries, build output, or generated artifacts.
+
 Before spawning Dev, check plan.md Tasks section:
 ```bash
 grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || echo 0
@@ -339,7 +341,7 @@ If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write the '#
 **CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.
 
 
-### Phase 6: Retrospective & Commit — DO NOT SKIP
+### Phase 6: Retrospective & Commit (SINGLE COMMIT) — DO NOT SKIP
 
 {{IF_MODE_SELF_EVOLVE}}
 **Framework Validation Gate (self-evolve mode)**:
@@ -361,37 +363,33 @@ bash {{VALIDATOR_SCRIPTS_DIR}}/validate-framework.sh
 ```bash
 git log --oneline | grep "{{FEATURE_ID}}" | head -3
 ```
-- If a commit for `{{FEATURE_ID}}` already exists → **skip 6c** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to Final Clean Check.
-- If no existing commit → proceed normally with 6a–6c.
+- If a commit for `{{FEATURE_ID}}` already exists → **skip 6d** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to 6e Final verification.
+- If no existing commit → proceed normally with 6b–6d.
 
 **6b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizm-docs/` architecture index):
 - **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
 - **Architecture knowledge** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work into `.prizm-docs/`
-- Stage all doc changes: `git add .prizm-docs/`
+- Stage doc changes: `git add .prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
 - **For bug-fix sessions**: structural sync only, skip knowledge injection unless a genuinely new pitfall was discovered
 
-**6c.** Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
-
-**6d.** MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
-
-**6e.** Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
-
-### Final Clean Check (before exit)
-
-Verify repository is clean:
-
+**6c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
-git status --short
+git add <specific-files-created-or-modified>
+git add .prizm-docs/
 ```
 
-**Note**: The pipeline runner will auto-commit any remaining dirty files after your session exits. You do NOT need to manually commit pipeline state files (`dev-pipeline/state/`) or runtime logs — just focus on committing your feature code via `/prizmkit-committer`.
-
-If any feature-related source files remain uncommitted, stage them **explicitly by name** (do NOT use `git add -A`) and create a follow-up commit:
+**6d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .prizm-docs/ updates. 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.
 
+**6e.** Final verification:
 ```bash
-git add <specific-file-1> <specific-file-2>
-git commit -m "chore({{FEATURE_ID}}): include session artifacts"
+git status --short
 ```
+Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file> && git commit --amend --no-edit`, do NOT create a separate commit.
 
 ## Critical Paths
 
@@ -434,6 +432,7 @@ rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
 - Gate checks enforce Implementation Log and Review Notes are written before proceeding
 - Do NOT use `run_in_background=true` when spawning agents
 - Commit phase must use `/prizmkit-committer`; do NOT replace with manual git commit commands
-- Before exiting, commit your feature code via `/prizmkit-committer` — the pipeline runner auto-commits any remaining files after session exit
-- When staging leftover files in the final clean check, always use explicit file names — NEVER use `git add -A`
+- Do NOT run `git add`/`git commit` during Phase 1-5 — all changes are committed once in Phase 6
+- If any files remain after the commit, amend the existing commit — do NOT create a follow-up commit
+- When staging files, always use explicit file names — NEVER use `git add -A` or `git add .`
 - On timeout: check snapshot → model:lite → remaining steps only → max 2 retries → orchestrator fallback

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.110",
+  "version": "1.0.112",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/app-planner/SKILL.md

@@ -130,6 +130,55 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 
 **Resume Detection**: See §Resume Support for checkpoint-based resumption.
 
+## Architecture Decision Capture
+
+During planning, key **framework-level** architectural decisions may emerge. When they do, capture them in the project instruction file so all future AI sessions have this context.
+
+### What Qualifies (ALL must apply)
+
+Only capture decisions that are **framework-shaping** — NOT individual feature details. Qualifying categories:
+
+| Category | Examples |
+|----------|----------|
+| Tech stack choices | PostgreSQL over MongoDB, React over Vue, Node.js runtime |
+| Communication patterns | REST vs GraphQL, WebSocket vs SSE vs polling |
+| Architectural patterns | Monorepo, microservices, monolith, event-driven |
+| Data model strategies | Relational vs document, event sourcing, CQRS |
+| Security architecture | JWT vs session, OAuth provider, RBAC model |
+
+**Do NOT capture**: individual feature implementation details, UI component choices, specific API endpoint designs, or anything scoped to a single feature.
+
+**This is conditional** — most planning sessions will NOT produce architecture decisions. Only capture when genuinely impactful decisions are made during the discussion.
+
+### When to Capture
+
+After Phase 5 (DAG verification), before Phase 6 (JSON generation). At this point decisions are settled.
+
+### How to Capture
+
+1. **Detect platform** — determine which project instruction file to update:
+   - `.claude/` directory exists → append to `CLAUDE.md`
+   - `.codebuddy/` directory exists → append to `CODEBUDDY.md`
+   - Both exist → append to both
+   - Neither exists → skip (no project instruction file)
+
+2. **Check for existing section** — read the target file and look for `### Architecture Decisions` heading:
+   - If heading exists → append new entries below it (avoid duplicates with existing entries)
+   - If heading does not exist → create it at the end of the file
+
+3. **Format** — one line per decision, no feature IDs:
+   ```markdown
+   ### Architecture Decisions
+   - WebSocket for real-time: sub-second latency required for collaboration features
+   - PostgreSQL: relational data model with complex queries, ACID compliance needed
+   - Monorepo structure: shared types between frontend and backend
+   ```
+
+4. **User confirmation** — before writing, show the collected decisions and ask:
+   > "These architecture decisions were identified during planning. Record them to [CLAUDE.md / CODEBUDDY.md]? (Y/n)"
+
+   If user declines, skip without further prompting.
+
 ## Fast Path — Incremental Shortcuts
 
 For simple incremental planning, skip detailed Phase 2-3 analysis to accelerate delivery:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.110",
+  "version": "1.0.112",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {