@mediadatafusion/pi-workflow-suite 0.0.21 → 0.0.22

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 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

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.21`
+**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.21
-pi install -l npm:@mediadatafusion/pi-workflow-suite@0.0.21
+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.21`. Version information is intentionally aligned across:
+The current preparation version is `v0.0.22`. Version information is intentionally aligned across:
 
-- `VERSION` (`v0.0.21`),
-- `package.json` (`0.0.21`),
+- `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.21
+v0.0.22

package/extensions/workflow-modes.ts

@@ -4920,7 +4920,7 @@ function standardPrompt(state: WorkflowState, settings: ReturnType<typeof loadWo
   const todoMode = standardTodoMode(settings);
   const standardModelRole = effectiveStandardModelRole(settings);
   const standardSubagentPolicyBlock = standardSubagentsAllowed(settings)
-    ? `Standard sub-agent policy:\n- active phase: ${state.standardActivePhase ?? "Planning"}${state.standardWorkKind ? ` (${state.standardWorkKind})` : ""}\n- agentScope: ${settings.standard.subagentScope ?? "user"}\n- planning/research: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Planning"), standardWorkerCount(settings, "Planning"))}\n- execution: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Execution"), standardWorkerCount(settings, "Execution"))}\n- repair: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Repair"), standardWorkerCount(settings, "Repair"))}\n- review: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Review"), standardWorkerCount(settings, "Review"))}\n- validation: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Validation"), standardWorkerCount(settings, "Validation"))}\nUse any configured package, user, or project agent that fits the task. When calling subagent in Standard Mode, pass agentScope=${settings.standard.subagentScope ?? "user"} and workflowPhase=planning, execution, repair, review, or validation. Do not launch execution sub-agents merely for read-only summaries, status updates, action-item reports, or docs/repo inspection; use execution sub-agents only before actual mutation or execution-class bash. If the active Standard phase is execution or repair and that phase policy is forced, satisfy the required sub-agent usage before edit/write/unsafe bash.`
+    ? `Standard sub-agent policy:\n- current worker bucket: ${state.standardActivePhase ?? "Planning"}${state.standardWorkKind ? ` (${state.standardWorkKind})` : ""}\n- agentScope: ${settings.standard.subagentScope ?? "user"}\n- planning/research: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Planning"), standardWorkerCount(settings, "Planning"))}\n- execution: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Execution"), standardWorkerCount(settings, "Execution"))}\n- repair: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Repair"), standardWorkerCount(settings, "Repair"))}\n- review: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Review"), standardWorkerCount(settings, "Review"))}\n- validation: ${activeWorkerTargetLabel(standardPhasePolicy(settings, "Validation"), standardWorkerCount(settings, "Validation"))}\nUse any configured package, user, or project agent that fits the task. When calling subagent in Standard Mode, pass agentScope=${settings.standard.subagentScope ?? "user"} and workflowPhase=planning, execution, repair, review, or validation. These workflowPhase labels are Standard worker buckets only; they do not move Standard into Plan/Mission review or validation UI. Do not launch execution sub-agents merely for read-only summaries, status updates, action-item reports, or docs/repo inspection; use execution sub-agents only before actual mutation or execution-class bash. If the active Standard worker bucket is execution or repair and that bucket policy is forced, satisfy the required sub-agent usage before edit/write/unsafe bash.`
     : "Standard Mode sub-agent delegation is disabled by settings.";
   const standardSubagentDecisionInstruction = standardSubagentsAllowed(settings)
     ? "For Standard auto/deep/maximum sub-agent policies, internally decide delegate or skip. Delegate for non-trivial parallelizable research, validation, repair, or implementation prep. Skip for trivial read-only/status work or when no useful parallel worker exists. Do not print internal sub-agent policy deliberation; if no worker runs, give only a concise user-facing skip reason when a Sub-Agent Usage Summary is naturally relevant."
@@ -16804,6 +16804,7 @@ Pi Version: v${VERSION}
         if (standardForcedSubagentSafeBash(command)) return;
       }
       if (event.toolName === "edit" || event.toolName === "write" || event.toolName === "bash") phase = "Execution";
+      else if (event.toolName === "subagent" && isRecord(event.input)) phase = parseSubagentWorkflowPhase(event.input.workflowPhase) ?? phase;
     }
     if (event.toolName === WORKFLOW_EXECUTION_RESULT_TOOL || event.toolName === MISSION_MILESTONE_RESULT_TOOL) phase = "Execution";
     if (event.toolName === WORKFLOW_REPAIR_RESULT_TOOL) phase = "Repair";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mediadatafusion/pi-workflow-suite",
-  "version": "0.0.21",
+  "version": "0.0.22",
   "description": "Multi-agent workflow suite for Pi with Idle, Standard, Plan, Mission, approval gates, reviewer/validator roles, sub-agents, model routing, web search/fetch, browser checks, diagrams, compaction, presets, settings, themes, widgets, and Repo Lock.",
   "license": "Apache-2.0",
   "repository": {