@phi-code-admin/phi-code 0.93.1 → 0.93.2

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [0.93.2] - 2026-07-12
+
+### Fixed
+
+- /fix: a single shot that changed NOTHING (text-only reply, zero edits — a
+  measured 91s failure mode) no longer ends UNVERIFIED; in a git repo with a
+  clean tree it ESCALATES to the full pipeline (nothing to verify = the work
+  was not done). The shot instruction now states that acting with tools is
+  mandatory and a textual plan forfeits the attempt. +1 integration test.
+
 ## [0.93.1] - 2026-07-12
 
 ### Fixed

package/extensions/phi/orchestrator.ts

@@ -1364,6 +1364,20 @@ Tag the note with relevant keywords for vector search.
 			fixContext.state.failingTest?.trim() || fixContext.state.reproCommand?.trim() || fixContext.reproFromShot;
 		const suiteCmd = sandbox.recipe.test?.trim();
 
+		// A shot that changed NOTHING has nothing to verify — "UNVERIFIED" would be
+		// a lie of omission (measured: a text-only 91s shot ended UNVERIFIED with
+		// zero edits). In a git repo with a clean diff, escalate to the full
+		// pipeline instead: the work simply was not done.
+		const inGitRepo = passed(runCommand("git rev-parse --is-inside-work-tree", { cwd, timeoutMs: 15_000 }));
+		if (inGitRepo && !gitIn(cwd, "diff").trim() && !gitIn(cwd, "status --porcelain").trim()) {
+			ctx.ui.notify(
+				`\n🔺 **/fix escalating: the single shot made NO changes** — nothing to verify, the full /debug pipeline takes over.`,
+				"warning",
+			);
+			phaseQueue.push(...buildDebugPhases(fixContext.state));
+			return false; // dispatch REPRODUCE
+		}
+
 		if (!sandbox.available() && (reproCmd || suiteCmd)) {
 			ctx.ui.notify(
 				`\n⚠️ **/fix oracle: sandbox unavailable** (${sandbox.reason}) — the single shot cannot be verified. Treating it as UNVERIFIED.`,

package/extensions/phi/providers/debug-build-commands.ts

@@ -126,6 +126,8 @@ export function singleShotInstruction(state: FailingState): string {
 **The problem:**
 ${failing}
 
+**You must ACT in this turn — call the read/edit/write tools and actually change the code. A textual plan or analysis with no edits counts as a FAILED shot (measured failure mode) and forfeits your attempt to the full pipeline.**
+
 **Do exactly this:**
 1. Read the relevant code and locate the root cause.
 2. Make the smallest change that addresses it. Do NOT edit tests. Every added guard/branch is a liability.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@phi-code-admin/phi-code",
-	"version": "0.93.1",
+	"version": "0.93.2",
 	"description": "Coding agent CLI with persistent memory, sub-agents, intelligent routing, and orchestration",
 	"type": "module",
 	"piConfig": {