prizmkit 1.1.141 → 1.1.143

package/bundled/skills/prizmkit/SKILL.md

@@ -69,12 +69,12 @@ Typos, pure formatting, small documentation edits, and other explicitly low-risk
 
 | Stage | Responsibility | Success handoff |
 |---|---|---|
-| `prizmkit-plan` | Clarify the requirement and create/review `spec.md` and `plan.md`. | `PLAN_READY` → `prizmkit-implement` |
-| `prizmkit-implement` | Execute the plan tasks and record completion. | `IMPLEMENTED` → `prizmkit-code-review` |
-| `prizmkit-code-review` | Main Agent reviews, repairs, verifies, and loops until convergence. | `REVIEW_PASS` → `prizmkit-test` |
-| `prizmkit-test` | Validate the final reviewed workspace with project-native tests and a consistent terminal report/result pair. | `TEST_PASS` → `prizmkit-retrospective` |
-| `prizmkit-retrospective` | Synchronize durable project documentation or record no documentation change. | `RETRO_COMPLETE` → `prizmkit-committer` |
-| `prizmkit-committer` | Verify gates, request commit confirmation, and create the local commit. | `COMMITTED` |
+| `prizmkit-plan` | Clarify the requirement and create/review `spec.md` and `plan.md`. | `status=completed`, `stage_result=PLAN_READY` → `prizmkit-implement` |
+| `prizmkit-implement` | Execute the plan tasks and record completion. | `status=completed`, `stage_result=IMPLEMENTED` → `prizmkit-code-review` |
+| `prizmkit-code-review` | Main Agent reviews, repairs, verifies, and loops until convergence. | `status=completed`, `stage_result=REVIEW_PASS` → `prizmkit-test` |
+| `prizmkit-test` | Validate the final reviewed workspace with project-native tests and a consistent terminal report/result pair. | `status=completed`, `stage_result=TEST_PASS` → `prizmkit-retrospective` |
+| `prizmkit-retrospective` | Synchronize durable project documentation or record no documentation change. | `status=completed`, `stage_result=RETRO_COMPLETE` → `prizmkit-committer` |
+| `prizmkit-committer` | Verify gates, request commit confirmation, and create the local commit. | `status=completed`, `stage_result=COMMITTED` |
 
 ### `prizmkit-workflow`
 

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

package/bundled/skills/prizmkit-code-review/SKILL.md

@@ -152,8 +152,8 @@ On `PASS`, update workflow state:
 ```json
 {
   "stage": "code-review",
-  "status": "REVIEW_PASS",
-  "stage_result": "PASS",
+  "status": "completed",
+  "stage_result": "REVIEW_PASS",
   "completed_stages": ["plan", "implement", "code-review"],
   "next_stage": "test",
   "resume_from": "prizmkit-test"
@@ -165,8 +165,8 @@ On `NEEDS_FIXES` caused by code findings, update workflow state:
 ```json
 {
   "stage": "code-review",
-  "status": "REVIEW_NEEDS_FIXES",
-  "stage_result": "NEEDS_FIXES",
+  "status": "failed",
+  "stage_result": "REVIEW_NEEDS_FIXES",
   "repair_scope": "production",
   "next_stage": "implement",
   "resume_from": "prizmkit-implement"

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

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

@@ -24,7 +24,7 @@ It does not decide which formal gates can be omitted. It verifies that all five
 
 ## When to Use
 
-- Workflow state reports `RETRO_COMPLETE` with a valid `retrospective-result.json` for the active formal requirement.
+- Workflow state reports `status=completed` with `stage_result=RETRO_COMPLETE` and a valid `retrospective-result.json` for the active formal requirement.
 - An interactive user confirms they want to create the local commit.
 - A trusted headless execution context authorizes an automatic local commit.
 - User says "commit", "submit", "finish", or "done" after the formal gates have completed.
@@ -49,7 +49,7 @@ For a formal requirement, all gates are mandatory:
 | Implement | All required tasks complete and `IMPLEMENTED` |
 | Code review | Final `review-report.md` result `PASS` |
 | Test | Consistent `TEST_PASS` report/result pair for the final reviewed workspace |
-| Retrospective | `retrospective-result.json` with `status=RETRO_COMPLETE` and `result=DOCS_UPDATED` or `result=NO_DOC_CHANGE` |
+| Retrospective | `retrospective-result.json` with workflow `status=completed`, `stage_result=RETRO_COMPLETE`, and artifact `result=DOCS_UPDATED` or `result=NO_DOC_CHANGE` |
 
 The committer must reject a state that merely claims a gate passed when the underlying artifact or current workspace contradicts it. If workflow state is missing, reconstruct it from authoritative artifacts and report the reconstruction before asking for confirmation.
 
@@ -145,7 +145,7 @@ Before the authorization preview, set or validate:
 ```json
 {
   "stage": "committer",
-  "status": "COMMIT_PENDING",
+  "status": "in_progress",
   "stage_result": "COMMIT_PENDING",
   "completed_stages": ["plan", "implement", "code-review", "test", "retrospective"],
   "next_stage": "committer",
@@ -168,7 +168,8 @@ After a successful local commit, update the runtime state to:
 ```json
 {
   "stage": "committer",
-  "status": "COMMITTED",
+  "status": "completed",
+  "stage_result": "COMMITTED",
   "completed_stages": ["plan", "implement", "code-review", "test", "retrospective", "committer"],
   "next_stage": null,
   "resume_from": null

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

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

@@ -89,7 +89,8 @@ On successful implementation, update `.prizmkit/state/workflows/<requirement-slu
 ```json
 {
   "stage": "implement",
-  "status": "IMPLEMENTED",
+  "status": "completed",
+  "stage_result": "IMPLEMENTED",
   "completed_stages": ["plan", "implement"],
   "repair_round": 0,
   "repair_scope": null,
@@ -98,7 +99,7 @@ On successful implementation, update `.prizmkit/state/workflows/<requirement-slu
 }
 ```
 
-For a repair, increment `repair_round`, set `status` to `IMPLEMENT_REPAIR`, preserve the triggering failure in the state, and select the next stage according to `repair_scope`. The outer workflow permits at most three repair rounds; the implementation stage must return a blocked result rather than start a fourth round.
+For a repair, increment `repair_round`, set `status=failed` and `stage_result=IMPLEMENT_REPAIR`, preserve the triggering failure in the state, and select the next stage according to `repair_scope`. The outer workflow permits at most three repair rounds; the implementation stage must return a blocked result rather than start a fourth round.
 
 ## Output and Handoff
 

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

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

@@ -144,7 +144,8 @@ Follow the bundled protocol. At minimum record:
   "schema_version": 1,
   "artifact_dir": ".prizmkit/specs/001-example",
   "stage": "plan",
-  "status": "PLAN_READY",
+  "status": "completed",
+  "stage_result": "PLAN_READY",
   "completed_stages": ["plan"],
   "repair_round": 0,
   "repair_scope": null,

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

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

@@ -102,7 +102,8 @@ Write `{artifact_dir}/retrospective-result.json` for every formal requirement:
 
 ```json
 {
-  "status": "RETRO_COMPLETE",
+  "status": "completed",
+  "stage_result": "RETRO_COMPLETE",
   "result": "DOCS_UPDATED",
   "reason": "Durable module interfaces and traps changed",
   "review_verdict": "PASS",
@@ -110,7 +111,7 @@ Write `{artifact_dir}/retrospective-result.json` for every formal requirement:
 }
 ```
 
-`status=RETRO_COMPLETE` is the stable completion status. `result` must be exactly `DOCS_UPDATED` or `NO_DOC_CHANGE`; do not use either result as a substitute for completion status. Use `result=NO_DOC_CHANGE` with a concrete reason when no documentation update is warranted. This artifact is the retrospective gate evidence consumed by the committer and external automation; workflow state alone does not prove completion.
+`status=completed` is the stable lifecycle status. `stage_result=RETRO_COMPLETE` marks successful retrospective completion; `result` must be exactly `DOCS_UPDATED` or `NO_DOC_CHANGE`. Use `result=NO_DOC_CHANGE` with a concrete reason when no documentation update is warranted. This artifact is the retrospective gate evidence consumed by the committer and external automation; workflow state alone does not prove completion.
 
 ## Workflow State and Handoff
 
@@ -121,14 +122,15 @@ On successful completion, update `.prizmkit/state/workflows/<requirement-slug>.j
 ```json
 {
   "stage": "retrospective",
-  "status": "RETRO_COMPLETE",
+  "status": "completed",
+  "stage_result": "RETRO_COMPLETE",
   "completed_stages": ["plan", "implement", "code-review", "test", "retrospective"],
   "next_stage": "committer",
   "resume_from": "prizmkit-committer"
 }
 ```
 
-Use `status=RETRO_COMPLETE` for both successful outcomes, with `result=DOCS_UPDATED` when durable docs changed or `result=NO_DOC_CHANGE` when the stage completed without a docs update. Both result values permit the commit stage.
+Use `status=completed` and `stage_result=RETRO_COMPLETE` for both successful outcomes, with `result=DOCS_UPDATED` when durable docs changed or `result=NO_DOC_CHANGE` when the stage completed without a docs update. Both result values permit the commit stage.
 
 If documentation validation or synchronization cannot safely complete, return `RETRO_BLOCKED`, do not commit, and provide the exact recovery entry.
 

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

@@ -45,7 +45,7 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
   "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,
@@ -63,14 +63,16 @@ Every consumer compares workflow state with the skill-owned artifacts and curren
 | `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 progression status, distinct from `stage_result`. |
-| `stage_result` | Domain result such as `PASS`, `NEEDS_FIXES`, `TEST_*`, `DOCS_UPDATED`, or `NO_DOC_CHANGE`. |
+| `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` | 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. |
 
+`status` and `stage_result` are deliberately separate. Lifecycle status values must never be replaced with domain result values.
+
 ## Lifecycle and Result Mappings
 
 ```text
@@ -83,18 +85,28 @@ PLAN_READY
 → COMMITTED
 ```
 
-No formal stage is silently optional. Domain artifacts map as follows:
+No formal stage is silently optional. Domain artifacts map to workflow state as follows:
 
 ```text
-review-report PASS               → status=REVIEW_PASS, stage_result=PASS
-review-report NEEDS_FIXES        → status=REVIEW_NEEDS_FIXES, stage_result=NEEDS_FIXES
-test-result TEST_PASS            → status=TEST_PASS, stage_result=TEST_PASS
-test-result TEST_NEEDS_FIXES     → status=TEST_NEEDS_FIXES, stage_result=TEST_NEEDS_FIXES
-test-result TEST_BLOCKED         → status=TEST_BLOCKED, stage_result=TEST_BLOCKED
-retrospective DOCS_UPDATED       → status=RETRO_COMPLETE, stage_result=DOCS_UPDATED
-retrospective 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
 ```
 
+`DOCS_UPDATED` and `NO_DOC_CHANGE` remain retrospective artifact `result` values. The workflow `stage_result` is the retrospective stage result `RETRO_COMPLETE`.
+
 `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.
 
 ## Non-Pass Results and Routing Boundary

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

@@ -284,7 +284,7 @@ No conditional pass exists.
 
 ## Terminal Report and Result
 
-Read `${SKILL_DIR}/references/test-report-template.md` before finalization. Write `test-report.md` and `test-result.json` together for every terminal outcome.
+Read `${SKILL_DIR}/references/test-report-template.md` before finalization. Write `test-report.md` and `test-result.json` together for every terminal outcome. The report must use the exact canonical `## Final Result` section and `- Result: <TEST_*>` marker from that template; do not rename it to `Terminal Result`, `Final Decision`, or another heading.
 
 `test-result.json` is a terminal projection, not a checkpoint:
 

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

@@ -1,6 +1,6 @@
 # Test Report Template
 
-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.
+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 Report

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`.
 
@@ -231,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: