prizmkit 1.1.160 → 1.1.162

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (31) hide show
  1. package/bundled/VERSION.json +3 -3
  2. package/bundled/dev-pipeline/README.md +3 -1
  3. package/bundled/dev-pipeline/prizmkit_runtime/heartbeat.py +9 -6
  4. package/bundled/dev-pipeline/prizmkit_runtime/runners.py +63 -4
  5. package/bundled/dev-pipeline/prizmkit_runtime/runtime_commit.py +268 -110
  6. package/bundled/dev-pipeline/scripts/update-bug-status.py +8 -4
  7. package/bundled/dev-pipeline/scripts/update-feature-status.py +10 -6
  8. package/bundled/dev-pipeline/scripts/update-refactor-status.py +8 -4
  9. package/bundled/dev-pipeline/templates/bootstrap-prompt.md +1 -1
  10. package/bundled/dev-pipeline/templates/bootstrap-tier3.md +2 -2
  11. package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md +1 -1
  12. package/bundled/dev-pipeline/templates/refactor-bootstrap-prompt.md +1 -1
  13. package/bundled/dev-pipeline/templates/sections/runtime-commit-handoff.md +9 -15
  14. package/bundled/dev-pipeline/tests/test_generate_bootstrap_prompt.py +8 -5
  15. package/bundled/dev-pipeline/tests/test_generate_bugfix_prompt.py +4 -2
  16. package/bundled/dev-pipeline/tests/test_generate_refactor_prompt.py +4 -2
  17. package/bundled/dev-pipeline/tests/test_python_runner_parity.py +221 -6
  18. package/bundled/dev-pipeline/tests/test_runtime_commit.py +308 -67
  19. package/bundled/dev-pipeline/tests/test_unified_cli.py +172 -4
  20. package/bundled/rules/prizm/prizm-commit-workflow.md +12 -5
  21. package/bundled/skills/_metadata.json +1 -1
  22. package/bundled/skills/prizmkit-code-review/SKILL.md +5 -5
  23. package/bundled/skills/prizmkit-code-review/references/independent-code-review.md +4 -5
  24. package/bundled/skills/prizmkit-code-review/references/review-report-template.md +4 -6
  25. package/bundled/skills/prizmkit-code-review/scripts/render_review_report.py +1 -4
  26. package/bundled/skills/prizmkit-committer/SKILL.md +47 -63
  27. package/bundled/skills/prizmkit-test/SKILL.md +2 -2
  28. package/bundled/skills/prizmkit-test/references/test-coverage-model.md +1 -1
  29. package/bundled/skills/prizmkit-workflow/SKILL.md +4 -6
  30. package/bundled/skills/prizmkit-workflow/references/workflow-state-protocol.md +10 -8
  31. package/package.json +1 -1
@@ -158,26 +158,28 @@ Any outer repair or continuation policy is independently owned by the caller and
158
158
  Interactive execution:
159
159
 
160
160
  ```text
161
- coordinator assembles exact intended_paths from all final Git-visible requirement paths, including justified `.prizmkit/**` output
162
- + separately labeled explicitly owned host support paths with one-to-one passing support_validation_evidence
163
- → committer validates ordinary task ownership, global Secret safety, and the exact files/message
161
+ coordinator validates final Review, Test, and Retrospective authority for the complete behavior-affecting Git-visible workspace
162
+ → committer inventories and inspects the complete current Git-visible workspace without caller-supplied paths
163
+ → committer applies global correctness, freshness, merge-state, and Secret checks
164
+ → committer previews every visible change and one truthful message
164
165
  → waits for explicit current-user confirmation
165
- → stages exact pathspecs, creates, and verifies the local commit
166
+ → stages the complete workspace, creates, and verifies the local commit
166
167
  ```
167
168
 
168
- The framework directory is not a blanket allowlist or denylist: a Git-visible `.prizmkit/**` path uses the same exact manifest, task justification, staged-set equality, Secret checks, and receipt verification as any other path, with no documentation-specific evidence. Ignored files remain absent and are never force-added. Exact Runtime request/checkpoint/state, installed Runtime/host payloads, sensitive, unknown, and unrelated paths remain excluded or blocking because of their semantic role. User confirmation alone is not host-support validation.
169
+ Git visibility, validated final content, and confirmation determine commit scope; path provenance does not. Correct changes may predate the active requirement or live under `.prizmkit/**`, generated, instruction, lock, or host-support namespaces. Ignored files remain absent, stay local, never block, and are never force-added. If behavior-affecting content appears after final Review/Test, the evidence is stale and the workflow re-enters those gates. Sensitive, conflicted, incorrect, incoherent, unreadable, or unverifiable content blocks on its actual state rather than an unknown-path category. The exact active workflow-state path derived from the artifact basename remains outside the interactive snapshot only because the coordinator finalizes it after Committer returns; it is not a general framework exclusion.
169
170
 
170
171
  Pipeline execution:
171
172
 
172
173
  ```text
173
174
  external coordinator validates its required gates and supplies exact readiness evidence
174
- → committer validates only that evidence and writes an exact runtime-commit-request.json
175
+ → committer validates the complete Git-visible workspace and writes a schema-v2 pathless runtime-commit-request.json without Git mutation
175
176
  → external coordinator maps COMMIT_REQUEST_READY to its checkpoint's in_progress/COMMIT_PENDING state
176
- → Python runtime validates the request, commits, verifies Git, and writes checkpoint completed/COMMITTED
177
+ → Python runtime re-enumerates and stages the complete non-ignored workspace
178
+ → Python runtime verifies the commit, writes its receipt, and finalizes checkpoint completed/COMMITTED
177
179
  → remote publication remains separate
178
180
  ```
179
181
 
180
- The preparation request is data for Runtime validation, not prompt-level authorization. The committer must not stage, commit, or predeclare COMMITTED in preparation mode. Safe Git-visible `.prizmkit/**` task output may appear in Runtime `intended_paths`; ignored paths remain absent, while exact Runtime bookkeeping/support and Secrets remain excluded. Runtime verifies the commit before writing its post-commit receipt/checkpoint and never retroactively inserts those writes into the committed snapshot.
182
+ The preparation request carries artifact identity, base head, and commit message, not path authorization. The committer must not stage, commit, or predeclare COMMITTED in preparation mode. Exact active request/checkpoint and post-commit receipt mutations may remain outside the committed snapshot only because their causal Runtime bookkeeping cannot truthfully precede the commit. Runtime verifies the base, non-empty commit, parent, message, receipt, and checkpoint order before integration; it never retroactively inserts post-commit writes into the snapshot.
181
183
 
182
184
  ## Recovery
183
185
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.1.160",
3
+ "version": "1.1.162",
4
4
  "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
5
5
  "type": "module",
6
6
  "bin": {