@janvitos/pi-plan-build 0.1.34 → 0.1.36

package/README.md

@@ -93,7 +93,7 @@ When Pi uses `"tuiMode": "fullscreen"` and the saved plan contains top-level `-
 
 The passive 64-column right panel reserves terminal columns, so the transcript and editor reflow instead of being covered. Long step instructions wrap across aligned continuation rows rather than being clipped. It never accepts focus or keyboard input and collapses below 132 terminal columns. The panel is a visual status aid only; all control happens through ordinary prompts. The agent interprets intent contextually, so these are examples rather than required commands:
 
-- “Implement the next step” or “Start step 2.”
+- “Implement the next step,” “Start step 2,” or simply “Approved” / “Go ahead.”
 - “Step 1 is complete,” “I verified that one,” or “I already handled this.”
 - “Change step 3 to …” or “Skip this step.”
 - “Pause the plan,” “hide the plan,” or “show the plan.”

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@janvitos/pi-plan-build",
-  "version": "0.1.34",
+  "version": "0.1.36",
   "description": "Plan safely, approve explicitly, then implement here or in a clean session.",
   "type": "module",
   "license": "MIT",

package/plan-panel.ts

@@ -67,7 +67,6 @@ export class PlanPanel implements Component {
 		if (this.state.status === "completed") lines.push(pad(this.theme.fg("success", "Plan complete")));
 		else if (this.state.status === "paused") lines.push(pad("Tell the agent to resume, cancel, or hide the plan."));
 		else if (current?.status === "ready") lines.push(pad("Tell the agent to implement, complete, edit, skip, cancel, or hide this step."));
-		else lines.push(pad("Plan progress updates automatically from your prompts."));
 		lines.push(border(`╰${"─".repeat(inner)}╯`));
 		return lines.map((line) => truncateToWidth(line, safeWidth, ""));
 	}

package/prompts.ts

@@ -71,7 +71,7 @@ Step-by-step execution is waiting for the user's natural-language instruction. N
 Current progress:
 ${progress}
 
-Interpret the user's intent contextually rather than requiring exact phrases. Clear statements, confirmations, and feedback may request a state transition even when phrased non-imperatively. For example, a statement that a ready step is finished can use the complete action. If multiple materially different actions are plausible, ask a brief clarification. Cancellation is always available when the user clearly wants to stop. Do not advance based on hypothetical, uncertain, or unrelated discussion. The sidebar is a passive visual aid and cannot receive input.
+Interpret the user's intent contextually rather than requiring exact phrases. In this waiting state, a clear approval or proceed statement such as “Approved,” “Go ahead,” or “Proceed” starts the current ready step. A statement that a ready step is already finished can use the complete action instead. If multiple materially different actions are plausible, ask a brief clarification. Cancellation is always available when the user clearly wants to stop. Do not advance based on hypothetical, uncertain, or unrelated discussion. The sidebar is a passive visual aid and cannot receive input.
 </system-reminder>`;
 }