prizmkit 1.1.148 → 1.1.150

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -51,7 +51,7 @@ Read `${SKILL_DIR}/references/configuration.md` before constructing prerequisite
 | Check status | Daemon status and item-level status commands |
 | Show logs | Recent or follow-log command |
 | Stop | Daemon stop command plus optional status command |
-| Retry one bug | Standard or clean reset-and-run command with safety disclosure |
+| Retry failed bug work | Preserve-runtime, standard, or clean reset plus a separate run command with safety disclosure |
 
 Only the start intent uses the execution-mode and configuration rounds.
 
@@ -151,27 +151,39 @@ Optionally include the daemon status command for the user to run afterward. Do n
 
 ## Retry Command
 
-A reset can discard uncommitted changes when the target task branch is currently checked out. Clean reset additionally deletes the task branch and clears its task history/artifacts. Never hide these effects behind the word “retry.”
+Reset changes state only; it never starts execution and rejects `--run`. Always return reset and run as separate commands.
 
-Use `AskUserQuestion` before constructing a retry command:
+A standard reset can discard uncommitted changes when the target task branch is currently checked out and records a fresh-checkout boundary. Clean reset additionally deletes the task branch and clears task history/artifacts. Preserve-runtime failed recovery instead scans the whole selected list, restores every failed root and its causal `auto_skipped` descendants, and retains valid checkout identity, sessions, checkpoints, artifacts, branches, worktrees, and WIP. If a recorded branch is missing, it creates a replacement from the recorded base, retains old artifacts for reference, and rewinds implementation-and-later checkpoint stages. Never hide these effects behind the word “retry.”
 
-- **Standard retry (Recommended)** — reset task status and rerun while preserving a non-current task branch; warn that an active task branch may still have uncommitted changes discarded by reset.
-- **Clean retry** — perform the standard reset and also delete the task branch and clear task history/artifacts.
-- **Cancel** — return no reset command.
+Use `AskUserQuestion` before constructing retry commands:
+
+- **Preserve failed runtime (Recommended for continuing failed work)** — recover all failed chains in the selected list without cleanup, then run the list; disclose that this is whole-list recovery rather than a single-ID reset.
+- **Standard fresh retry** — reset one bug, then run that bug separately; warn that the active task branch can lose uncommitted changes.
+- **Clean retry** — reset one bug, delete its task branch/history/artifacts, then run it separately.
+- **Cancel** — return no reset or run command.
+
+Preserve-runtime template:
+
+```bash
+python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix --failed --preserve-runtime .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py bugfix run .prizmkit/plans/bug-fix-list.json
+```
 
 Standard template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix B-001 --run .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix B-001 .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py bugfix run B-001 .prizmkit/plans/bug-fix-list.json
 ```
 
 Clean template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix B-001 --clean --run .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix B-001 --clean .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py bugfix run B-001 .prizmkit/plans/bug-fix-list.json
 ```
 
-For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying the command.
+`--preserve-runtime` requires `--failed` and cannot be combined with `--clean`, an ID, a range, or another reset filter. Retry-budget flags such as `--max-retries` and `--max-infra-retries` belong on the run command, never reset. For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying either command.
 
 ## Output Contract
 

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -54,7 +54,7 @@ Classify the request before asking configuration questions:
 | Check status | Daemon status and item-level status commands |
 | Show logs | Recent or follow-log command |
 | Stop | Daemon stop command plus optional status command |
-| Retry one feature | Standard or clean reset-and-run command with safety disclosure |
+| Retry failed feature work | Preserve-runtime, standard, or clean reset plus a separate run command with safety disclosure |
 
 Only the start intent uses the execution-mode and configuration rounds.
 
@@ -169,27 +169,39 @@ Optionally include the daemon status command for the user to run afterward. Do n
 
 ## Retry Command
 
-A reset can discard uncommitted changes when the target task branch is currently checked out. Clean reset additionally deletes the task branch and clears its task history/artifacts. Never hide these effects behind the word “retry.”
+Reset changes state only; it never starts execution and rejects `--run`. Always return reset and run as separate commands.
 
-Use `AskUserQuestion` before constructing a retry command:
+A standard reset can discard uncommitted changes when the target task branch is currently checked out and records a fresh-checkout boundary. Clean reset additionally deletes the task branch and clears task history/artifacts. Preserve-runtime failed recovery instead scans the whole selected list, restores every failed root and its causal `auto_skipped` descendants, and retains valid checkout identity, sessions, checkpoints, artifacts, branches, worktrees, and WIP. If a recorded branch is missing, it creates a replacement from the recorded base, retains old artifacts for reference, and rewinds implementation-and-later checkpoint stages. Never hide these effects behind the word “retry.”
 
-- **Standard retry (Recommended)** — reset task status and rerun while preserving a non-current task branch; warn that an active task branch may still have uncommitted changes discarded by reset.
-- **Clean retry** — perform the standard reset and also delete the task branch and clear task history/artifacts.
-- **Cancel** — return no reset command.
+Use `AskUserQuestion` before constructing retry commands:
+
+- **Preserve failed runtime (Recommended for continuing failed work)** — recover all failed chains in the selected list without cleanup, then run the list; disclose that this is whole-list recovery rather than a single-ID reset.
+- **Standard fresh retry** — reset one feature, then run that feature separately; warn that the active task branch can lose uncommitted changes.
+- **Clean retry** — reset one feature, delete its task branch/history/artifacts, then run it separately.
+- **Cancel** — return no reset or run command.
+
+Preserve-runtime template:
+
+```bash
+python3 ./.prizmkit/dev-pipeline/cli.py reset feature --failed --preserve-runtime .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py feature run .prizmkit/plans/feature-list.json
+```
 
 Standard template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset feature F-001 --run .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset feature F-001 .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py feature run F-001 .prizmkit/plans/feature-list.json
 ```
 
 Clean template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset feature F-001 --clean --run .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset feature F-001 --clean .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py feature run F-001 .prizmkit/plans/feature-list.json
 ```
 
-For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying the command.
+`--preserve-runtime` requires `--failed` and cannot be combined with `--clean`, an ID, a range, or another reset filter. Retry-budget flags such as `--max-retries` and `--max-infra-retries` belong on the run command, never reset. For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying either command.
 
 ## Output Contract
 

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -52,7 +52,7 @@ Read `${SKILL_DIR}/references/configuration.md` before constructing prerequisite
 | Check status | Daemon status and item-level status commands |
 | Show logs | Recent or follow-log command |
 | Stop | Daemon stop command plus optional status command |
-| Retry one refactor | Standard or clean reset-and-run command with safety disclosure |
+| Retry failed refactor work | Preserve-runtime, standard, or clean reset plus a separate run command with safety disclosure |
 
 Only the start intent uses the execution-mode and configuration rounds.
 
@@ -164,27 +164,39 @@ Optionally include the daemon status command for the user to run afterward. Do n
 
 ## Retry Command
 
-A reset can discard uncommitted changes when the target task branch is currently checked out. Clean reset additionally deletes the task branch and clears its task history/artifacts. Never hide these effects behind the word “retry.”
+Reset changes state only; it never starts execution and rejects `--run`. Always return reset and run as separate commands.
 
-Use `AskUserQuestion` before constructing a retry command:
+A standard reset can discard uncommitted changes when the target task branch is currently checked out and records a fresh-checkout boundary. Clean reset additionally deletes the task branch and clears task history/artifacts. Preserve-runtime failed recovery instead scans the whole selected list, restores every failed root and its causal `auto_skipped` descendants, and retains valid checkout identity, sessions, checkpoints, artifacts, branches, worktrees, and WIP. If a recorded branch is missing, it creates a replacement from the recorded base, retains old artifacts for reference, and rewinds implementation-and-later checkpoint stages. Never hide these effects behind the word “retry.”
 
-- **Standard retry (Recommended)** — reset task status and rerun while preserving a non-current task branch; warn that an active task branch may still have uncommitted changes discarded by reset.
-- **Clean retry** — perform the standard reset and also delete the task branch and clear task history/artifacts.
-- **Cancel** — return no reset command.
+Use `AskUserQuestion` before constructing retry commands:
+
+- **Preserve failed runtime (Recommended for continuing failed work)** — recover all failed chains in the selected list without cleanup, then run the list; disclose that this is whole-list recovery rather than a single-ID reset.
+- **Standard fresh retry** — reset one refactor, then run that refactor separately; warn that the active task branch can lose uncommitted changes.
+- **Clean retry** — reset one refactor, delete its task branch/history/artifacts, then run it separately.
+- **Cancel** — return no reset or run command.
+
+Preserve-runtime template:
+
+```bash
+python3 ./.prizmkit/dev-pipeline/cli.py reset refactor --failed --preserve-runtime .prizmkit/plans/refactor-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py refactor run .prizmkit/plans/refactor-list.json
+```
 
 Standard template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset refactor R-001 --run .prizmkit/plans/refactor-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset refactor R-001 .prizmkit/plans/refactor-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py refactor run R-001 .prizmkit/plans/refactor-list.json
 ```
 
 Clean template:
 
 ```bash
-python3 ./.prizmkit/dev-pipeline/cli.py reset refactor R-001 --clean --run .prizmkit/plans/refactor-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset refactor R-001 --clean .prizmkit/plans/refactor-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py refactor run R-001 .prizmkit/plans/refactor-list.json
 ```
 
-For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying the command.
+`--preserve-runtime` requires `--failed` and cannot be combined with `--clean`, an ID, a range, or another reset filter. Retry-budget flags such as `--max-retries` and `--max-infra-retries` belong on the run command, never reset. For clean retry, require explicit acknowledgement of branch deletion and possible uncommitted-change loss before displaying either command.
 
 ## Output Contract
 

package/bundled/templates/project-memory-template.md

@@ -32,6 +32,44 @@ This project uses PrizmKit with the Prizm documentation system for AI-optimized
 ### Available Commands
 Run `/prizmkit` to see all available PrizmKit commands.
 
+### Python Runtime CLI Quick Reference
+
+Placeholders: `<family> = feature | bugfix | refactor`; `<task-id> = F-NNN | B-NNN | R-NNN`; `<list>` is optional and defaults by family:
+
+| `<family>` | Default `<list>` |
+|---|---|
+| `feature` | `.prizmkit/plans/feature-list.json` |
+| `bugfix` | `.prizmkit/plans/bug-fix-list.json` |
+| `refactor` | `.prizmkit/plans/refactor-list.json` |
+
+```bash
+# Run/resume the whole list or one task
+python3 ./.prizmkit/dev-pipeline/cli.py <family> run [<list>] [--max-retries N] [--max-infra-retries N]
+python3 ./.prizmkit/dev-pipeline/cli.py <family> run <task-id> [<list>] [--max-retries N] [--max-infra-retries N]
+
+# Inspect or recover task state
+python3 ./.prizmkit/dev-pipeline/cli.py <family> status [<list>]
+python3 ./.prizmkit/dev-pipeline/cli.py <family> unskip [<task-id>] [<list>]
+python3 ./.prizmkit/dev-pipeline/cli.py recovery detect
+
+# Reset state (never starts execution)
+python3 ./.prizmkit/dev-pipeline/cli.py reset <family> <task-id> [<list>]
+python3 ./.prizmkit/dev-pipeline/cli.py reset <family> --failed --preserve-runtime [<list>]
+python3 ./.prizmkit/dev-pipeline/cli.py reset <family> <task-id> --clean [<list>]
+
+# Background operation
+python3 ./.prizmkit/dev-pipeline/cli.py daemon <family> start [<list>]
+python3 ./.prizmkit/dev-pipeline/cli.py daemon <family> status
+python3 ./.prizmkit/dev-pipeline/cli.py daemon <family> logs [--lines N|--follow]
+python3 ./.prizmkit/dev-pipeline/cli.py daemon <family> stop
+```
+
+Runtime boundaries:
+- Reset and run are separate operations; reset rejects `--run`. Retry ceilings belong to `run`, not reset.
+- `--preserve-runtime` requires `--failed`, scans the whole selected list, and cannot be combined with `--clean`, an ID/range, or another reset filter.
+- Preserve-runtime recovery keeps valid checkout identity, sessions, checkpoints, artifacts, branches, worktrees, and WIP. If the recorded branch is missing, it creates a replacement from the recorded base and rewinds implementation-and-later checkpoint stages while retaining old artifacts for reference. Clean reset is destructive.
+- In zsh/Bash multiline commands, `\` must be the final character on the line with no trailing space.
+
 ### Lightweight Planning Path
 Not every change needs the full formal-requirement lifecycle. Use the lightweight path for:
 - Bug fixes with clear root cause, config tweaks, typo fixes, simple refactors

package/package.json

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