@mediadatafusion/pi-workflow-suite 0.0.20 → 0.0.22

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable public releases will be documented in this file.
 
+## [0.0.22] - 2026-06-14
+
+### Improved
+
+- Refined Standard Mode sub-agent worker bucket handling.
+- Refreshed Plan Mode README commands and recovery notes.
+
+## [0.0.21] - 2026-06-13
+
+### Hardened
+
+- Hardened Mission Mode clarification and execution handoff behavior.
+- Hardened sub-agent policy handling across workflow phases.
+- Refined forced sub-agent exceptions and validation handoff timing.
+- Refined Mission validation repair routing for safer continued progress.
+- Hardened project-aware Plan/Mission resume selection.
+- Hardened Plan Mode continuation behavior for multi-step plans.
+
 ## [0.0.20] - 2026-06-12
 
 ### Improved

package/README.md

@@ -4,7 +4,7 @@
 
 [![Install](https://cdn.jsdelivr.net/npm/@mediadatafusion/pi-workflow-suite@0.0.12/docs/assets/readme-link-install.svg)](#installation) [![Quick Start](https://cdn.jsdelivr.net/npm/@mediadatafusion/pi-workflow-suite@0.0.12/docs/assets/readme-link-quick-start.svg)](#quick-start) [![Commands](https://cdn.jsdelivr.net/npm/@mediadatafusion/pi-workflow-suite@0.0.12/docs/assets/readme-link-commands.svg)](#core-commands) [![Settings](https://cdn.jsdelivr.net/npm/@mediadatafusion/pi-workflow-suite@0.0.12/docs/assets/readme-link-settings.svg)](#settings-reference)
 
-**Workflow Suite Version:** `v0.0.20`
+**Workflow Suite Version:** `v0.0.22`
 
 ## Overview
 
@@ -246,36 +246,63 @@ The reviewer is a pre-execution second opinion on the approved plan and risk pro
 
 Core behavior:
 
-- Plain `/p` enters Plan Mode and waits for your next message.
-- `/p <task>` starts planning immediately.
-- `/plan <task>` provides the same workflow through the full command name.
+- Plain `/p` or `/plan` enters Plan Mode and waits for your next message.
+- `/p <task>` or `/plan <task>` starts planning immediately.
 - The planner must choose either `PLAN_DECISION: clarify` or `PLAN_DECISION: plan`.
 - Clarification questions are generated from the actual task, not static boilerplate.
-- Execution is approval-gated.
-- Execution must follow the approved plan only.
+- Execution is approval-gated and must follow the approved plan only.
+- Plan execution tracks approved steps through `workflow_progress`.
+- Review is a pre-execution second opinion when enabled.
 - Validation is read-only and reports PASS, PARTIAL PASS, FAIL, or UNKNOWN.
-- Plan history can save draft, revised, and approved plans.
+- Repair, retry, and revalidation recover failed or partial validation when safe.
+- Plan history saves draft, revised, approved, completed, and archived plan records.
+- `/plan resume` or `/p resume` restores current or recoverable Plan state and shows the next action or resume menu; it does not auto-run workflow gates.
+- `/plan continue` or `/p continue` advances the current or recovered Plan through the next configured gate, such as review, execution, validation, repair, or final completion.
 
 Common commands:
 
 ```text
+Entry and status:
 /p
+/plan
 /p <task>
+/plan <task>
 /p status
+/plan status
+
+Approval and revision:
 /p approve
-/p revise <feedback>
-/p cancel
-/plan
-/plan <task>
 /plan approve
+/p revise <feedback>
 /plan revise <feedback>
-/plan cancel
+
+Resume and continuation:
+/p resume
+/plan resume
+/p continue
+/plan continue
+
+Validation repair:
+/p repair
+/plan repair
+/p retry
+/plan retry
+/p revalidate
+/plan revalidate
+
+Clarification, execution, and history:
 /clarify questions
 /clarify answer 1A 2C
 /execute
 /validate
 /workflow plans list
 /workflow plans list latest
+/workflow plans list <id>
+/workflow plans cleanup [limit]
+
+Exit:
+/p cancel
+/plan cancel
 ```
 
 ## Mission Mode
@@ -977,6 +1004,11 @@ Plan history can persist workflow plans under Pi runtime state. Saved plans incl
 - clarification questions and answers,
 - final plan,
 - approval status,
+- execution summary and final report,
+- reviewer report and review history,
+- validation verdict and validation report,
+- repair status, repair attempt, and repair history,
+- progress and runtime snapshot,
 - model role usage,
 - sub-agent metadata,
 - save reason.
@@ -1055,8 +1087,8 @@ pi install -l npm:@mediadatafusion/pi-workflow-suite
 ### Installing specific versions
 
 ```bash
-pi install npm:@mediadatafusion/pi-workflow-suite@0.0.20
-pi install -l npm:@mediadatafusion/pi-workflow-suite@0.0.20
+pi install npm:@mediadatafusion/pi-workflow-suite@0.0.22
+pi install -l npm:@mediadatafusion/pi-workflow-suite@0.0.22
 ```
 
 An unversioned install follows normal update behavior: `pi update` and `pi update --extensions` will pick up new package releases. A versioned install pins the package to that version. Pinned package specs are intentionally skipped by Pi's normal package update commands. To move a pinned install to a newer version, reinstall with the desired version. To switch back to latest tracking, use the unversioned install command without `@<version>`.
@@ -1140,6 +1172,8 @@ Choose Mission Mode when you want milestone-based, resumable work:
 | `/workflow status` | List current workflow, Standard, Plan, and Mission state. |
 | `/standard` | Enter Standard Mode for direct active work. |
 | `/p` / `/plan` | Plan a task before editing. |
+| `/plan resume` | Restore current or recoverable Plan state and show the next action. |
+| `/plan continue` | Continue an approved or recovered Plan through the next configured gate. |
 | `/clarify` | Answer Plan Mode clarification questions. |
 | `/execute` | Run an approved plan. |
 | `/validate` | Validate implementation against the approved plan. |
@@ -1262,10 +1296,10 @@ See `docs/TROUBLESHOOTING.md` for detailed diagnostics.
 
 ## Versioning
 
-The current preparation version is `v0.0.20`. Version information is intentionally aligned across:
+The current preparation version is `v0.0.22`. Version information is intentionally aligned across:
 
-- `VERSION` (`v0.0.20`),
-- `package.json` (`0.0.20`),
+- `VERSION` (`v0.0.22`),
+- `package.json` (`0.0.22`),
 - `package-lock.json`,
 - this README,
 - Workflow Suite settings/about output.

package/VERSION

@@ -1 +1 @@
-v0.0.20
+v0.0.22

package/config/prompts/mission-repair.md

@@ -5,6 +5,7 @@ MANDATORY STRUCTURED HANDOFF: call workflow_repair_result before final response
 You are PI MISSION MODE REPAIR EXECUTOR.
 
 Repair concrete validator-identified failures for the current mission milestone and keep going while fixes are in-scope and non-destructive. Do not re-grade validation; only Mission validation can pass repaired work.
+Do not call `workflow_progress` in Mission Mode. Mission repair completion is tracked only by `workflow_repair_result`.
 
 Rules:
 - Only fix concrete issues directly related to the failed milestone validation.

package/config/prompts/mission-run.md

@@ -5,6 +5,7 @@ MANDATORY STRUCTURED HANDOFF: call mission_milestone_result before final respons
 You are PI MISSION MODE EXECUTOR.
 
 Run only the approved current mission milestone. Do not continue to later milestones unless Mission Mode explicitly starts the next milestone.
+Do not call `workflow_progress` in Mission Mode. Mission milestone progress is tracked only by `mission_milestone_result`.
 
 Milestone loop expectation:
 1. Restate the current mission and milestone.