prizmkit 1.1.130 → 1.1.134

package/bundled/skills/recovery-workflow/references/detection.md

@@ -1,67 +1,43 @@
-# Recovery Phase Detection
+# Interrupted Task Branch Detection
 
-Detection uses priority-ordered signals, but no single signal is authoritative. Prefer a conservative recovery phase when signals disagree.
+Recovery uses the runtime's durable task checkout identity rather than reconstructing lifecycle phases from branches, diffs, plans, or historical artifacts.
 
-## Signature Priority
+## Authoritative Records
 
-1. Current branch starts with `fix/` -> likely `bug-fix-workflow`.
-2. `.prizmkit/state/bugfix/` or `.prizmkit/plans/bug-fix-list.json` has relevant failed/in-progress state -> likely bugfix pipeline.
-3. `.prizmkit/bugfix/` has optional bugfix artifacts -> possible `bug-fix-workflow`.
-4. Current branch starts with `refactor/` -> likely `refactor-workflow`.
-5. `.prizmkit/plans/refactor-list.json` or `.prizmkit/state/refactor/` exists -> likely refactor pipeline.
-6. Current branch starts with `feat/` -> likely `feature-workflow`.
-7. `.prizmkit/plans/feature-list.json` or `.prizmkit/state/features/` exists -> likely feature pipeline.
-8. `spec.md` or `plan.md` exists without family-specific signals -> current-workspace Fast Path; ask which workflow it belongs to.
-9. None of the above -> no workflow detected.
-
-Bug-fix signals are prioritized because interactive bug recovery benefits most from preserving local diagnosis and fix work.
+```text
+.prizmkit/state/features/<F-NNN>/checkout.json
+.prizmkit/state/bugfix/<B-NNN>/checkout.json
+.prizmkit/state/refactor/<R-NNN>/checkout.json
+```
 
-## Optional vs Required Artifacts
+A record is resumable only when:
 
-`fix-plan.md` and `fix-report.md` are optional bug recovery signals. They are useful when present, but bug-fix recovery must also infer from branch, diff, `spec.md`, `plan.md`, review artifacts, commits, and bug-list entries.
+1. `state` equals `active`.
+2. `task_id` matches the directory family.
+3. `active_dev_branch` is non-empty.
+4. `refs/heads/<active_dev_branch>` exists locally.
 
-## If No Workflow Is Detected
+Ignore records whose state is `completed` or `reset`. Also ignore session logs, plan lists, artifact directories, and checkpoint files when no active checkout record exists. Those files may remain after completed or historical work and are not evidence of an interrupted task.
 
-Show guidance and exit:
+## Runtime Continuation Contract
 
-```markdown
-No interrupted workflow was detected in this workspace.
+The item-specific foreground command reloads the active checkout record and reuses its branch or linked worktree:
 
-Start a new workflow:
-- /feature-workflow — build features from idea to code
-- /bug-fix-workflow — fix a specific bug interactively
-- /refactor-workflow — restructure code while preserving behavior
+```bash
+python3 ./.prizmkit/dev-pipeline/cli.py feature run <F-NNN>
+python3 ./.prizmkit/dev-pipeline/cli.py bugfix run <B-NNN>
+python3 ./.prizmkit/dev-pipeline/cli.py refactor run <R-NNN>
 ```
 
-## Phase Inference Tables
-
-### Bug-Fix Recovery
-
-| Detected state | Resume from | Actions |
-|---|---|---|
-| `fix/*` branch, no implementation artifacts | Diagnosis / triage | Restore bug context, confirm understanding, choose next action |
-| `spec.md` or `plan.md`, no code changes | Fix | Read plan and implement the root-cause fix |
-| Optional `fix-plan.md`, no code changes | Fix | Read fix plan and implement the fix |
-| Code/test changes, no review artifact | Review | Run tests if safe, then invoke `/prizmkit-code-review` |
-| Review artifact or optional `fix-report.md` | User verification | Ask user whether to verify manually before commit |
-| Commit ahead on fix branch | Merge decision | Ask merge / keep branch / decide later |
-
-Bug-fix diagnosis, triage, and reproduction do not always create durable artifacts. If interrupted before code changes or a plan artifact, restart from diagnosis rather than guessing.
+The command does not need an explicit branch argument. Do not prepend `git checkout`, because the runtime owns checkout identity and branch/worktree reuse.
 
-### Feature Recovery
+## Selection Rules
 
-| Detected state | Resume from | Actions |
-|---|---|---|
-| No feature list and no Fast Path artifacts | Route selection | Clarify whether to plan, implement Fast Path, or start app planning |
-| `spec.md` or `plan.md` with feature context | Fast Path continuation | Continue implementation, review, retrospective, or commit based on diff |
-| `.prizmkit/plans/feature-list.json`, no pipeline state | Launch | Invoke `feature-pipeline-launcher` |
-| Feature list plus `.prizmkit/state/features/` | Monitor/recover | Check launcher status or run recovery script |
+- One active record: return its command directly.
+- Multiple active records: ask the user to select a task by family, task ID, and branch.
+- No active record: report `NO_INTERRUPTED_TASK_FOUND`; do not infer a target from newest timestamps or branch names.
+- Missing recorded branch: omit that record and report it as invalid only when the user explicitly asks for detector diagnostics.
 
-### Refactor Recovery
+## Safety
 
-| Detected state | Resume from | Actions |
-|---|---|---|
-| No refactor list and no Fast Path artifacts | Route selection | Clarify behavior-preserving refactor goal |
-| `spec.md` or `plan.md` with refactor context | Fast Path continuation | Continue implementation, behavior checks, review, retrospective, or commit |
-| `.prizmkit/plans/refactor-list.json`, no pipeline state | Launch | Invoke `refactor-pipeline-launcher` |
-| Refactor list plus `.prizmkit/state/refactor/` | Monitor/recover | Check launcher status or run recovery script |
+Recovery only reports a command. It does not execute the command, reset state, delete artifacts, remove worktrees, switch branches, commit, merge, or push.