prizmkit 1.1.140 → 1.1.142

package/bundled/skills/prizmkit-test/references/test-report-template.md

@@ -1,87 +1,172 @@
-# Derived Test Evidence Report Template
+# Test Report Template
 
-Generate this report solely from the structured, hashed evidence package. It is not independently editable authority. Any change to this file or another linked artifact without manifest regeneration causes deterministic validation failure.
+Create one human-readable report for every terminal result. Replace an older report for the same invocation context; do not append duplicate final-result sections. Use the exact `## Final Result` heading and `- Result: <TEST_*>` marker shown below. Do not rename this machine-read contract to `Terminal Result`, `Final Decision`, or another heading.
 
 ```markdown
-# Test Evidence Report
-
-Derived from structured evidence. Authoritative package: `{evidence_dir}`
-
-## Evidence
-- Evidence ID: {64-character evidence_id}
-- Protocol Version: {protocol_version}
-- Classification: {behavior / lightweight}
-- Working Diff SHA-256: {working_diff_sha256}
-- Sensitivity: sensitivity=project-controlled
-- Environment Claim: mocked-code-level-only
-
-The evidence package preserves complete command, environment, stdout, stderr, patch, hash, and execution-history values without automatic redaction. The project owns access control, retention, and upload policy. Production credentials, production services, and destructive real-data operations are prohibited.
-
-Mocked code-level evidence does not verify a real deployed environment.
-
-## Scope
-- Affected Module: {name} ({explicit / cohesion-derived})
-- Primary Scope: {count and pointers}
-- Regression Ring: {count and pointers}
-- Verdict-capable Unresolved Edges: {count}
-
-## Behavior-Risk Completeness
-- Observable Behaviors: {count}
-- Applicable Risk Cells: {count}
-- Proven/Mapped Risk Cells: {count}
-- Unresolved Risk Cells: {count}
-- Diagnostic Coverage Signals: {values or not collected; never the completion basis}
-- Matrix: `behavior-risk-matrix.json`
-
-## Risk-Adaptive Test Plan
-| Layer | Required | Rationale | Tests | Selected Execution IDs |
-|-------|----------|-----------|-------|------------------------|
-| focused | {yes/no} | {...} | {...} | {...} |
-| module-component | {yes/no} | {...} | {...} | {...} |
-| contract-integration | {yes/no} | {...} | {...} | {...} |
-| affected-module-regression | {yes/no} | {...} | {...} | {...} |
-| regression-ring | {yes/no} | {...} | {...} | {...} |
-
-## Infrastructure and Contracts
-- Native Runner/Conventions: {...}
-- Infrastructure Changes: `infrastructure-changes.json`
-- Contract Snapshots: `contracts/`
-- Production Resources Used: no
-
-## Current-State Execution Evidence
-
-- Selected Receipts: {execution_receipts}
-- Evidence: `executions.json`, `receipts/`, and `raw/`
-
-## Executions
-- Attempts Preserved: {count}
-- Selected Required Executions: {IDs in order}
-- Complete History: `executions.json`
-- Raw Outputs: `raw/`
-
-## Deterministic Validation
-- Command: `python3 ${SKILL_DIR}/scripts/validate_test_evidence.py --evidence-dir {evidence_dir} --project-root {target_project_root}`
-- Result: {passed / failed}
-- Validation Record: `validation.json`
-
-## Verdict
-Verdict: TEST_PASS | TEST_FAIL | TEST_BLOCKED
-
-## Responsibility Boundary
-- Testing-domain verdict only: yes
-- Overall code-quality or broad Spec verdict: no
-- Business defects repaired by this skill: no
-- Commit/release authorized: no
+# Test Report
+
+## Final Result
+
+- Result: TEST_PASS | TEST_NEEDS_FIXES | TEST_BLOCKED
+- Summary: <concise testing-domain conclusion>
+
+## Change Scope
+
+- Scope: <this-change / module / feature / full-project>
+- Production paths: <paths or none>
+- Test paths: <existing, added, and modified paths>
+- Requirement source: <specification, acceptance criteria, caller request, or none>
+
+## Affected Business Module
+
+- Boundary: <explicit module or cohesion-derived responsibility>
+- Public entry points: <entries>
+- Scope rationale: <why this is the complete affected boundary>
+
+## Observable Business Behaviors
+
+| Behavior | Truth Source | Tests | Result |
+|---|---|---|---|
+| <behavior> | <spec/contract/acceptance/test/caller> | <test paths or cases> | passed / needs-fixes / blocked |
+
+## Boundary and Risk Coverage
+
+| Behavior | Applicable Risks | Coverage | Material Omission Reason |
+|---|---|---|---|
+| <behavior> | <functional, boundary, error, state, side-effect, permission, concurrency, idempotency, time, dependency, consumer> | <tests and layers> | <none or behavior-specific reason> |
+
+Coverage metrics, when available: <diagnostic values or not collected>. Percentages are not the completion basis.
+
+## Regression Ring
+
+| Caller / Consumer / Contract / State | Coupling | Verification | Result |
+|---|---|---|---|
+| <edge> | <observable dependency> | <test or command> | passed / needs-fixes / blocked |
+
+- Unresolved verdict-capable edges: <none or list>
+
+## Tests Added or Updated
+
+| Path | Layer | Behaviors and Risks | Change |
+|---|---|---|---|
+| <path> | focused / module / contract / integration / E2E / regression | <coverage> | added / updated / existing |
+
+- Existing native framework reused: <yes/no and framework>
+- Infrastructure changes: <none or concise list>
+- Testability seams: <none or behavior-preserving changes>
+
+## Native Test Execution
+
+| Command | Working Directory | Scope / Layer | Result | Key Output |
+|---|---|---|---|---|
+| <native command> | <cwd> | <tests or layer> | passed / failed / blocked | <concise output or log pointer> |
+
+- Required affected-module regression complete: yes / no
+- Required Regression Ring verification complete: yes / no
+- Project-wide regression required: yes / no
+- Project-wide regression result: passed / failed / not-required / blocked
+
+## Main-Agent Review
+
+- Rounds: <0..10>
+- Accepted findings: <count>
+- Fixed findings: <count>
+- Rejected findings: <count with concise evidence pointers>
+- Unresolved findings: <count and list>
+- Converged on exact final state: yes / no
+
+## Independent Test Review
+
+- Status: completed / downgraded / not_applicable
+- Responses: <0..5>
+- Capability gate or downgrade reason: <reason or none>
+- Corrections and Main-Agent adjudication: <summary or none>
+- Exact final state independently rechecked: yes / no
+
+## Repairs Performed
+
+| Round | Failure Classification | Repair | Focused Verification | Required Regression |
+|---|---|---|---|---|
+| <1..3> | test-defect / local-production-defect / high-risk-production-defect / environment-unavailable / truth-unresolved / flaky-or-unreliable | <change or none> | <result> | <result> |
+
+- Repair rounds used: <0..3>
+- Assertions or scope weakened to obtain green output: no
+
+## Production Repair Risk
+
+- Production changed during test: yes / no
+- Repair locality: <local / high-risk / none>
+- Delta Code Review required: yes / no
+- Review scope: delta / none
+- Rationale: <contract and risk analysis>
+
+## External Contracts and Mocks
+
+| Dependency | Contract Source | Test Double / Isolation | Variants | Remaining Risk |
+|---|---|---|---|---|
+| <dependency> | <project path or public official source/version> | <mock/fake/server/container/isolated service> | <success/boundary/failure variants> | <none or risk> |
+
+- Production credentials or resources used: no
 - Real deployed environment validated: no
 
-## Compatibility
-The formal lifecycle consumes validated authoritative `TEST_*` evidence through workflow state and structured evidence pointers. `test-report.md` is a derived compatibility view and must not be interpreted as a review, retrospective, commit, or release verdict.
+## Remaining Risks and Unresolved Items
+
+- <none, or every known correction/blocker with concrete target and next required fact>
 ```
 
-## Verdict Rendering Rules
+## Result Rendering Rules
+
+Render `TEST_PASS` only when:
+
+- mandatory Main-Agent review converged;
+- independent review converged or was visibly downgraded under its strict capability gate;
+- all required native tests pass on the exact final state;
+- no accepted or unresolved finding remains;
+- no high-risk production repair awaits delta Code Review;
+- no mutation occurred after final applicable review and execution.
+
+Render `TEST_NEEDS_FIXES` for a known remaining correction, exhausted review/repair budget with known work, or a completed high-risk repair requiring delta Code Review.
+
+Render `TEST_BLOCKED` when truth, required input, safe environment, execution reliability, external-target safety, or required Reviewer input prevents a safe verdict.
+
+No conditional pass, commit authorization, release authorization, runtime classification, target hash, manifest, attestation, or package lifecycle belongs in the report.
+
+## Terminal Machine Projection
+
+Write `test-result.json` together with the report:
+
+```json
+{
+  "schema_version": 1,
+  "result": "TEST_PASS",
+  "report": "test-report.md",
+  "main_review_rounds": 1,
+  "independent_review": {
+    "status": "downgraded",
+    "responses": 0,
+    "downgrade_reason": "required read-only continuation capability is unavailable",
+    "final_state_rechecked": false
+  },
+  "repair_rounds": 0,
+  "production_changed": false,
+  "review_required": false,
+  "review_scope": null,
+  "unresolved_items": []
+}
+```
 
-- Render `TEST_PASS` only after deterministic validation passes and all required evidence is proven.
-- Render `TEST_FAIL` only with reliable reproduced failure execution pointers.
-- Render `TEST_BLOCKED` with explicit blocker pointers.
-- Never render `PASS`, `NEEDS_FIXES`, conditional pass, “ready for commit,” or release authorization.
-- A lightweight `TEST_PASS` must say it proves only the deterministic lightweight claim, not runtime behavior.
+Constraints:
+
+- `schema_version` is `1`.
+- `result` is `TEST_PASS`, `TEST_NEEDS_FIXES`, or `TEST_BLOCKED`.
+- `report` is the sibling report filename `test-report.md`.
+- `main_review_rounds` is an integer from `0` through `10`; `0` is valid only when early blocking prevents a complete review round.
+- `independent_review.status` is `completed`, `downgraded`, or `not_applicable`.
+- `completed` requires `responses` from `1` through `5`, `downgrade_reason=null`, and `final_state_rechecked=true`.
+- `downgraded` requires `responses=0`, a non-empty `downgrade_reason`, and `final_state_rechecked=false`.
+- `not_applicable` requires `responses=0`, `downgrade_reason=null`, and `final_state_rechecked=false`.
+- `independent_review.responses` is otherwise bounded from `0` through `5`.
+- `review_scope` is `delta` exactly when `review_required=true`; otherwise it is null.
+- `unresolved_items` contains concise strings and agrees with the report.
+- Report and JSON agree on final result and production-review requirement.
+- The JSON is terminal output only and is never updated as an internal checkpoint.

package/bundled/skills/prizmkit-workflow/SKILL.md

@@ -92,12 +92,12 @@ Expected transitions:
 
 | Stage | Required success | Next stage |
 |---|---|---|
-| `prizmkit-plan` | `PLAN_READY` | `prizmkit-implement` |
-| `prizmkit-implement` | `IMPLEMENTED` | `prizmkit-code-review` |
-| `prizmkit-code-review` | `REVIEW_PASS` | `prizmkit-test` |
-| `prizmkit-test` | `TEST_PASS` | `prizmkit-retrospective` |
-| `prizmkit-retrospective` | `status=RETRO_COMPLETE` with result `DOCS_UPDATED` or `NO_DOC_CHANGE` | `prizmkit-committer` |
-| `prizmkit-committer` | explicit interactive confirmation, then `COMMITTED` | end |
+| `prizmkit-plan` | `status=completed`, `stage_result=PLAN_READY` | `prizmkit-implement` |
+| `prizmkit-implement` | `status=completed`, `stage_result=IMPLEMENTED` | `prizmkit-code-review` |
+| `prizmkit-code-review` | `status=completed`, `stage_result=REVIEW_PASS` | `prizmkit-test` |
+| `prizmkit-test` | `status=completed`, `stage_result=TEST_PASS` | `prizmkit-retrospective` |
+| `prizmkit-retrospective` | `status=completed`, `stage_result=RETRO_COMPLETE`, with artifact result `DOCS_UPDATED` or `NO_DOC_CHANGE` | `prizmkit-committer` |
+| `prizmkit-committer` | explicit interactive confirmation, then `status=completed` with `stage_result=COMMITTED` | end |
 
 `TEST_NOT_APPLICABLE` is not a valid lifecycle success. Lightweight changes must execute deterministic verification and return `TEST_PASS`.
 
@@ -107,8 +107,8 @@ The composite must not:
 
 - reinterpret a plan as implementation;
 - repair production code outside `prizmkit-implement` or the Main-Agent review loop;
-- claim tests passed without validated authoritative test evidence;
-- treat a derived Markdown report as the test source of truth;
+- claim tests passed without a consistent `test-report.md` and terminal `test-result.json`;
+- reinterpret testing-domain results as runtime/session outcomes;
 - perform retrospective documentation changes itself;
 - stage or commit before `prizmkit-committer` applies the current execution's authorization boundary;
 - invoke `prizmkit-deploy` as a hidden seventh stage.
@@ -129,34 +129,26 @@ prizmkit-implement
 
 The Main-Agent review skill owns its internal review repairs and its internal ten-round limit before returning its terminal result. The outer workflow repair counter is separate.
 
-### Test Failure
+### Test Non-Pass
 
-`TEST_FAIL` must come from the validated authoritative evidence verdict and include `repair_scope`:
-
-TEST_FAIL affecting only tests, fixtures, test-runner configuration, or evidence infrastructure uses `repair_scope=test-infrastructure`:
+`prizmkit-test` already performs bounded test construction, execution-failure repair, mandatory Main-Agent review, and optional independent review before returning. The composite consumes its terminal artifacts without recreating those loops.
 
 ```text
-TEST_FAIL with repair_scope=test-infrastructure
-  → prizmkit-implement
-  → prizmkit-test
-```
-
-Test infrastructure includes tests, fixtures, test-runner configuration, and evidence infrastructure only.
-
-TEST_FAIL affecting production code, runtime configuration, schema, dependencies, or public interfaces uses the matching production-family scope:
+TEST_NEEDS_FIXES
+  → preserve test-report.md and test-result.json
+  → stop with the known remaining correction or delta-review requirement
+  → caller owns any later review/retest decision
 
-```text
-TEST_FAIL with repair_scope=production | runtime | schema | dependency | public-interface
-  → prizmkit-implement
-  → prizmkit-code-review
-  → prizmkit-test
+TEST_BLOCKED
+  → preserve test-report.md and test-result.json
+  → stop with the unresolved truth, input, safety, environment, or reliability blocker
 ```
 
-Production-affecting repair after `REVIEW_PASS` must receive another review. A test-infrastructure-only repair may return directly to testing. Unknown scope uses the conservative production route only when safe; otherwise the workflow is blocked.
+The composite must not invoke implementation or Code Review automatically from inside the returned testing result unless its own explicitly authorized outer policy defines a new invocation. It must never treat either result as an AI CLI crash.
 
 ### Environment Block
 
-`TEST_BLOCKED` means trustworthy evidence is unavailable because of environment, permission, dependency, external-service, scope, evidence, reliability, cleanup, or budget problems.
+`TEST_BLOCKED` means a safe testing verdict is unavailable because truth, required input, environment, permission, external-target safety, execution reliability, or required review input remains unresolved.
 
 Interactive behavior:
 
@@ -180,7 +172,7 @@ repair_round: 0 → 1 → 2 → 3
 When the limit is reached:
 
 - set workflow status to `WORKFLOW_BLOCKED`;
-- preserve the latest authoritative failure evidence;
+- preserve the latest reports and terminal results;
 - report completed rounds and unresolved cause;
 - report the exact skill, `artifact_dir`, and state path from which a user may resume after resolving the cause or explicitly authorizing another attempt;
 - do not claim the requirement is complete.
@@ -225,7 +217,7 @@ On resume:
 
 1. Read the workflow state specified by `resume` or discover the target project's active workflow state.
 2. Read `${SKILL_DIR}/references/workflow-state-protocol.md`.
-3. Verify `spec.md`, `plan.md`, review report, authoritative test evidence, retrospective result, and current workspace against state.
+3. Verify `spec.md`, `plan.md`, review report, test report/result pair, retrospective result, and current workspace against state.
 4. If state is missing or stale, reconstruct the safest recoverable predecessor and report the reconstruction.
 5. Continue from the first incomplete stage; never bypass a required gate based only on stale state.
 6. Preserve the same `artifact_dir` and repair-round count.
@@ -239,18 +231,18 @@ At successful completion, report:
 WORKFLOW_COMPLETE
 artifact_dir: <path>
 stages:
-  - PLAN_READY
-  - IMPLEMENTED
-  - REVIEW_PASS
-  - TEST_PASS
-  - RETRO_COMPLETE (DOCS_UPDATED | NO_DOC_CHANGE)
-  - COMMITTED
+  - status=completed, stage_result=PLAN_READY
+  - status=completed, stage_result=IMPLEMENTED
+  - status=completed, stage_result=REVIEW_PASS
+  - status=completed, stage_result=TEST_PASS
+  - status=completed, stage_result=RETRO_COMPLETE (result=DOCS_UPDATED | NO_DOC_CHANGE)
+  - status=completed, stage_result=COMMITTED
 commit: <hash>
 push: not performed automatically
 next_action: invoke /prizmkit-deploy separately if deployment is needed
 ```
 
-If the user declines interactive commit confirmation, report `COMMIT_PENDING` rather than `WORKFLOW_COMPLETE` and provide the exact `/prizmkit-committer` resume entry.
+If the user declines interactive commit confirmation, report `status=in_progress`, `stage_result=COMMIT_PENDING` rather than `WORKFLOW_COMPLETE` and provide the exact `/prizmkit-committer` resume entry.
 
 If blocked, report:
 

package/bundled/skills/prizmkit-workflow/references/workflow-state-protocol.md

@@ -1,6 +1,6 @@
 # PrizmKit Workflow State Protocol
 
-`workflow-state.json` is lifecycle runtime metadata for one formal requirement. It preserves stage handoff, repair routing, orchestrator ownership, and resume information without replacing authoritative artifacts or any host-owned execution checkpoint.
+`workflow-state.json` is lifecycle metadata for one formal requirement. It preserves stage handoff, orchestrator ownership, and resume information without replacing skill-owned artifacts or any host-owned execution checkpoint.
 
 ## Location and Identity
 
@@ -8,7 +8,7 @@
 .prizmkit/state/workflows/<requirement-slug>.json
 ```
 
-The state file is created only when a lifecycle runs. The active `artifact_dir` is the generic requirement artifact root and must be preserved exactly across every stage:
+The active `artifact_dir` is preserved exactly across every stage:
 
 ```text
 .prizmkit/specs/<requirement-slug>/
@@ -16,7 +16,7 @@ The state file is created only when a lifecycle runs. The active `artifact_dir`
 .prizmkit/refactor/<refactor-id>/
 ```
 
-Never select a different most-recent plan when resuming or handing off. Any execution checkpoint maintained by an external host remains separate from this lifecycle state. Never merge, substitute, or infer one schema from the other. The target project controls whether generated `.prizmkit/` files are committed, ignored, or shared.
+Never select another recent plan when resuming. Any external execution checkpoint remains separate from this state. Never merge, substitute, or infer one schema from the other.
 
 ## Authority
 
@@ -26,16 +26,16 @@ The state file is an index, not the authority for stage completion:
 |---|---|
 | Requirement goals and acceptance criteria | `{artifact_dir}/spec.md` |
 | Implementation tasks and completion | `{artifact_dir}/plan.md` plus current workspace |
-| Review findings and verdict | `{artifact_dir}/review-report.md` final result |
-| Test execution, verdict, and repair scope | Validated evidence package and authoritative `verdict.json` |
-| Test report presentation | `{artifact_dir}/test-report.md` as a derived view only |
-| Retrospective completion and result | `{artifact_dir}/retrospective-result.json` |
+| Review findings and result | `{artifact_dir}/review-report.md` |
+| Test semantics and native execution | `{artifact_dir}/test-report.md` |
+| Terminal testing result | `{artifact_dir}/test-result.json` |
+| Retrospective completion | `{artifact_dir}/retrospective-result.json` |
 | Durable architecture knowledge | `.prizmkit/prizm-docs/` |
 | Local commit | Git history and confirmed or authorized commit identity |
 | Current stage, orchestrator, and resume entry | Workflow state |
-| External orchestration progress | The external host's own checkpoint, never this state |
+| External orchestration progress | External host checkpoint |
 
-Every consumer compares workflow state with authoritative artifacts and the current workspace. Missing or stale state is reconstructed from those sources and is never accepted as success by itself.
+Every consumer compares workflow state with the skill-owned artifacts and current workspace. Missing or stale state is reconstructed from those sources and is never accepted as success by itself.
 
 ## Schema
 
@@ -45,7 +45,7 @@ Every consumer compares workflow state with authoritative artifacts and the curr
   "artifact_dir": ".prizmkit/specs/example",
   "orchestrator": "prizmkit-workflow",
   "stage": "test",
-  "status": "TEST_PASS",
+  "status": "completed",
   "stage_result": "TEST_PASS",
   "completed_stages": ["plan", "implement", "code-review", "test"],
   "repair_scope": null,
@@ -59,88 +59,83 @@ Every consumer compares workflow state with authoritative artifacts and the curr
 
 | Field | Meaning |
 |---|---|
-| `schema_version` | State schema version. Current value is `1`. |
-| `artifact_dir` | The single generic requirement artifact root reused by every stage. |
-| `orchestrator` | `prizmkit-workflow`, another semantic coordinator identifier, or `null` for direct stage use. |
-| `stage` | The stage that most recently wrote state. |
-| `status` | Lifecycle progression status, distinct from the domain `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `schema_version` | State schema version. |
+| `artifact_dir` | Generic requirement artifact root reused by every stage. |
+| `orchestrator` | Semantic coordinator identifier, or null for direct stage use. |
+| `stage` | Stage that most recently wrote state. |
+| `status` | Lifecycle status: `pending`, `in_progress`, `completed`, `failed`, or `skipped`. |
+| `stage_result` | Domain result for the current stage, such as `PLAN_READY`, `IMPLEMENTED`, `REVIEW_PASS`, `REVIEW_NEEDS_FIXES`, `TEST_*`, `RETRO_COMPLETE`, or `COMMITTED`. |
 | `completed_stages` | Ordered stages completed for this requirement. |
-| `repair_scope` | `null`, `test-infrastructure`, `production`, `runtime`, `schema`, `dependency`, `public-interface`, or `unknown`. |
-| `repair_round` | Outer cross-stage repair round, from `0` through `3`. |
-| `next_stage` | Next semantic stage, or `null` after commit. |
-| `resume_from` | Exact atomic skill that can resume, or `null` after commit. |
+| `repair_scope` | Optional caller-owned routing scope. The test skill reports high-risk repairs through `test-result.json` instead of scheduling another stage. |
+| `repair_round` | Optional outer cross-stage repair round, from 0 through 3. It is not a test-internal repair counter. |
+| `next_stage` | Next semantic stage, or null when stopped. |
+| `resume_from` | Exact atomic skill that can resume, or null when none is selected. |
 
-## Lifecycle and Verdict Mappings
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
 
-The mandatory formal lifecycle is:
+## Lifecycle and Result Mappings
 
 ```text
 PLAN_READY
-  → IMPLEMENTED
-  → REVIEW_PASS
-  → TEST_PASS
-  → RETRO_COMPLETE
-  → COMMIT_PENDING
-  → COMMITTED
+→ IMPLEMENTED
+→ REVIEW_PASS
+→ TEST_PASS
+→ RETRO_COMPLETE
+→ COMMIT_PENDING
+→ COMMITTED
 ```
 
-No formal stage is silently optional. Domain evidence maps as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report final PASS        → status=REVIEW_PASS, stage_result=PASS
-review-report final NEEDS_FIXES → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-validated verdict TEST_PASS     → status=TEST_PASS, stage_result=TEST_PASS
-validated verdict TEST_FAIL     → status=TEST_FAIL, stage_result=TEST_FAIL
-validated verdict TEST_BLOCKED  → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective result DOCS_UPDATED  → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective result NO_DOC_CHANGE → status=RETRO_COMPLETE, stage_result=NO_DOC_CHANGE
+plan PLAN_READY                  → status=completed,  stage_result=PLAN_READY
+plan PLAN_BLOCKED                → status=failed,     stage_result=PLAN_BLOCKED
+implementation IMPLEMENTED       → status=completed,  stage_result=IMPLEMENTED
+implementation repair/block      → status=failed,     stage_result=IMPLEMENT_REPAIR or IMPLEMENT_BLOCKED
+review-report PASS               → status=completed,  stage_result=REVIEW_PASS
+review-report NEEDS_FIXES        → status=failed,     stage_result=REVIEW_NEEDS_FIXES
+test-result TEST_PASS            → status=completed,  stage_result=TEST_PASS
+test-result TEST_NEEDS_FIXES     → status=failed,     stage_result=TEST_NEEDS_FIXES
+test-result TEST_BLOCKED         → status=failed,     stage_result=TEST_BLOCKED
+retrospective DOCS_UPDATED       → status=completed,  stage_result=RETRO_COMPLETE
+retrospective NO_DOC_CHANGE      → status=completed,  stage_result=RETRO_COMPLETE
+retrospective blocked            → status=failed,     stage_result=RETRO_BLOCKED
+commit authorization pending     → status=in_progress, stage_result=COMMIT_PENDING
+local commit confirmed           → status=completed,  stage_result=COMMITTED
+commit blocked                   → status=failed,     stage_result=COMMIT_BLOCKED
 ```
 
-`RETRO_COMPLETE` is the stable completion status. `DOCS_UPDATED` and `NO_DOC_CHANGE` are mutually exclusive retrospective results, not substitute statuses. A derived Markdown test report never establishes a `TEST_*` status without validated authoritative evidence.
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
 
-## Repair Routing
+`TEST_PASS` requires both `test-report.md` and a consistent `test-result.json`. No manifest, attestation, evidence package, or test-internal checkpoint is part of this contract.
 
-```text
-REVIEW_NEEDS_FIXES
-  → implement
-  → code-review
-  → test
-
-TEST_FAIL with repair_scope=test-infrastructure
-  → implement
-  → test
+## Non-Pass Results and Routing Boundary
 
-TEST_FAIL with repair_scope=production|runtime|schema|dependency|public-interface
-  → implement
-  → code-review
-  → test
+`prizmkit-test` performs its own bounded failure repair and review loops before returning. The test skill never invokes another lifecycle stage.
 
-TEST_FAIL with repair_scope=unknown
-  → conservative production route only when safe
-  → otherwise WORKFLOW_BLOCKED
+```text
+TEST_NEEDS_FIXES
+→ known correction or required delta review remains
+→ caller decides whether and how to arrange another stage
 
 TEST_BLOCKED
-  → never make speculative production edits
-  → interactive execution stops with a prizmkit-test resume entry
-  → a trusted headless host may perform bounded environment recovery, then records WORKFLOW_BLOCKED if unresolved
-
-RETRO_BLOCKED
-  → WORKFLOW_BLOCKED
-WORKFLOW_BLOCKED
-  → resume only after the recorded blocker is resolved
+→ truth, input, safe environment, or reliable execution prevents a verdict
+→ never make speculative production edits
+→ caller or external host owns recovery policy
 ```
 
-The outer workflow permits at most three automatic repair rounds. These are cross-stage rounds (`repair_round` `0` through `3`). The code-review internal loop permits at most ten completed review rounds and is separate; review-internal repairs do not increment the outer counter.
+A test result is not an AI CLI session classification. `TEST_NEEDS_FIXES` and `TEST_BLOCKED` must not be rewritten as crash or infrastructure failure merely because they stop lifecycle progression.
+
+Any outer repair or continuation policy is independently owned by the caller and cannot alter the test report. The Main-Agent test review limit of ten rounds, independent Test Reviewer limit of five responses, and execution-failure repair limit of three rounds are internal to one test invocation and do not update outer counters.
 
 ## Orchestrator Ownership and Handoff
 
-1. An atomic stage performs only its own stage, writes the truthful terminal result and `next_stage`, and returns control.
-2. When `orchestrator` is non-null, only that orchestrator invokes the next skill. The atomic stage must not auto-invoke it again.
-3. Direct stage use may report one deterministic next invocation but does not claim the next stage ran.
+1. An atomic stage performs only its own stage, writes its truthful result and artifact paths, and returns control.
+2. When `orchestrator` is non-null, only that orchestrator invokes the next skill.
+3. Direct stage use may report a possible next invocation but does not claim it ran.
 4. Every handoff preserves the same `artifact_dir`.
-5. External automation invokes atomic stages directly and does not invoke `prizmkit-workflow` as a nested coordinator.
-6. Workflow state never replaces or absorbs an external host's checkpoint.
+5. External automation invokes atomic stages directly and does not nest the composite workflow.
+6. Workflow state never replaces or absorbs an external host checkpoint.
 
 ## Commit Authorization
 
@@ -148,34 +143,32 @@ Interactive execution:
 
 ```text
 committer previews intended files and message
-→ waits for explicit confirmation from the current user
+→ waits for explicit current-user confirmation
 → creates the local commit
 ```
 
 Trusted headless execution:
 
 ```text
-a trusted host explicitly authorizes the current local task commit
-→ host injects mode=<host-defined-headless-mode>, owner=<trusted-host-identifier>,
-  local_commit_authorized=true
+trusted host explicitly authorizes the current local task commit
 → committer verifies gates and commits automatically
-→ no question or wait is permitted
+→ remote publication remains separate
 ```
 
-A self-declared or otherwise untrusted headless context does not authorize a commit. Remote publication remains a separate host-runtime decision.
+A self-declared or untrusted headless context does not authorize a commit.
 
 ## Recovery
 
 When state is missing, stale, or inconsistent:
 
-1. Read `spec.md` and `plan.md` from `artifact_dir` only when they are not already available in current context.
-2. Inspect task markers and the current workspace.
-3. Read the latest review report and final result when needed to establish review authority.
-4. Validate authoritative test evidence and `repair_scope`.
+1. Reuse current context, then read `spec.md` and `plan.md` only when needed.
+2. Inspect task markers and current workspace.
+3. Read the current review report when needed to establish review authority.
+4. Validate that `test-report.md` and terminal `test-result.json` exist, agree, and reflect the claimed result.
 5. Validate `retrospective-result.json` when retrospective is claimed complete.
 6. Verify the commit when commit is claimed complete.
-7. When an external host is active, let that host validate its own checkpoint independently; never merge the schemas.
+7. Let an active external host validate its own checkpoint independently.
 8. Reconstruct the latest safe predecessor and report the reconstruction.
 9. Continue only from the first incomplete or invalid stage.
 
-Stale state never bypasses review, testing, retrospective, commit authorization, or external host checkpoint enforcement.
+Stale state never bypasses review, testing, retrospective, commit authorization, or external checkpoint enforcement.

package/package.json

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