pi-better-harness 0.3.10 → 0.3.11

package/node_modules/pi-better-goal/README.md

@@ -25,12 +25,12 @@ Skills that own execution and their own task plan can opt in through `SKILL.md`
 
 ```yaml
 metadata:
-  pi-better-plan-workflow: coordinator
+  workflow-role: coordinator
 ```
 
 Invoke the skill with Pi's `/skill:name` command. The goal extension checks Pi's skill-command provenance, persists the owner on the session branch, and restores its instructions on resumed turns. It does not infer ownership from ordinary text or skill names. A goal such as `/goal /skill:name task` is rejected; invoke `/skill:name task` directly and use `/goal` only for a plain-language objective. Legacy slash-shaped goals pause on resume rather than running without the skill. `/workflow` shows the owner; call `release_workflow` after the workflow's completion audit (or use `/workflow clear` to release it manually). Completing an active goal also releases ownership.
 
-When `pi-better-plan` is installed, it defers its prompt, checklist, and `update_plan` tool to a skill-owned task plan. Skills without this metadata retain normal goal and plan behavior. The skill itself owns its planning format and worker policy; the harness does not enumerate skills or impose a shared workflow schema.
+When `pi-better-plan` is installed, it defers its prompt, checklist, and `update_plan` tool to a skill-owned task plan. Skills without this metadata retain normal goal and plan behavior. The skill itself owns its planning format and worker policy; the harness does not enumerate skills or impose a shared workflow schema. The former `pi-better-plan-workflow: coordinator` metadata remains supported for installed skills.
 
 ## Install
 

package/node_modules/pi-better-goal/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-better-goal",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Pi extension for goal tracking with background-aware continuation.",
   "license": "MIT",
   "type": "module",

package/node_modules/pi-better-goal/src/workflow.ts

@@ -25,14 +25,17 @@ export function workflowOwnerFromSkill(name: string, path: string): WorkflowOwne
   const metadata = (frontmatter as { metadata?: unknown }).metadata;
   if (!metadata || typeof metadata !== "object") return null;
   const fields = metadata as Record<string, unknown>;
-  if (fields["pi-better-plan-workflow"] === undefined) {
+  const role = fields["workflow-role"];
+  const legacyRole = fields["pi-better-plan-workflow"];
+  if (role === undefined && legacyRole === undefined) {
     if (fields["pi-better-workflow-role"] !== undefined || fields["pi-better-plan-owner"] !== undefined) {
-      throw new Error(`Outdated workflow metadata in ${path}. Use pi-better-plan-workflow: coordinator.`);
+      throw new Error(`Outdated workflow metadata in ${path}. Use workflow-role: coordinator.`);
     }
     return null;
   }
-  if (fields["pi-better-plan-workflow"] !== "coordinator") {
-    throw new Error(`Invalid workflow metadata in ${path}. Expected pi-better-plan-workflow: coordinator.`);
+  if ((role !== undefined && role !== "coordinator") ||
+      (legacyRole !== undefined && legacyRole !== "coordinator")) {
+    throw new Error(`Invalid workflow metadata in ${path}. Expected workflow-role: coordinator.`);
   }
   return { name, path, role: "coordinator", planOwner: "workflow" };
 }

package/node_modules/pi-better-plan/README.md

@@ -23,7 +23,7 @@ Independent foreground and delegated milestones may both be `in_progress`. Use s
 
 For a DAG, assign stable ids to prerequisite steps and list those ids in dependent steps' `dependsOn`. Dependencies must exist in the same plan; cycles and starting or completing a step before its prerequisites are complete are rejected. `get_plan` reports pending steps whose prerequisites are complete as ready. Plans without edges keep their existing behavior.
 
-When an explicitly invoked skill declares `pi-better-plan-workflow: coordinator` in its metadata, that skill's task plan takes precedence. The generic checklist stays persisted but is hidden, and `update_plan` refuses competing updates until workflow ownership is released. Rush-style workflows can use their own dependency graph without copying it into this plan.
+When an explicitly invoked skill declares `workflow-role: coordinator` in its metadata, that skill's task plan takes precedence. The generic checklist stays persisted but is hidden, and `update_plan` refuses competing updates until workflow ownership is released. Rush-style workflows can use their own dependency graph without copying it into this plan.
 
 ## Install
 

package/node_modules/pi-better-plan/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-better-plan",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Structured execution plans with persistent progress for Pi.",
   "license": "MIT",
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-better-harness",
-  "version": "0.3.10",
+  "version": "0.3.11",
   "description": "Pi extension bundle for a write sandbox, subagents, background tasks, SSH, goals, and structured plans.",
   "license": "MIT",
   "type": "module",
@@ -51,8 +51,8 @@
   },
   "dependencies": {
     "pi-better-background-tasks": "0.2.13",
-    "pi-better-goal": "0.3.0",
-    "pi-better-plan": "0.2.0",
+    "pi-better-goal": "0.3.1",
+    "pi-better-plan": "0.2.1",
     "pi-better-sandbox": "0.3.0",
     "pi-better-ssh": "0.1.1",
     "pi-better-subagents": "0.1.29",