@mediadatafusion/pi-workflow-suite 0.0.20 → 0.0.21

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable public releases will be documented in this file.
 
+## [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.21`
 
 ## Overview
 
@@ -1055,8 +1055,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.21
+pi install -l npm:@mediadatafusion/pi-workflow-suite@0.0.21
 ```
 
 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>`.
@@ -1262,10 +1262,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.21`. Version information is intentionally aligned across:
 
-- `VERSION` (`v0.0.20`),
-- `package.json` (`0.0.20`),
+- `VERSION` (`v0.0.21`),
+- `package.json` (`0.0.21`),
 - `package-lock.json`,
 - this README,
 - Workflow Suite settings/about output.

package/VERSION

@@ -1 +1 @@
-v0.0.20
+v0.0.21

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.