gsd-pi 2.78.1-dev.b6a389b66 → 2.78.1-dev.e9d88a536

package/dist/resources/.managed-resources-content-hash

@@ -1 +1 @@
-cc8431019a2c8873
+d371193140538b9c

package/dist/resources/extensions/gsd/guided-flow.js

@@ -19,7 +19,7 @@ import { assessInterruptedSession, formatInterruptedSessionRunningMessage, forma
 import { listUnitRuntimeRecords, clearUnitRuntimeRecord } from "./unit-runtime.js";
 import { resolveExpectedArtifactPath } from "./auto.js";
 import { gsdHome } from "./gsd-home.js";
-import { gsdRoot, milestonesDir, resolveMilestoneFile, resolveMilestonePath, resolveSliceFile, resolveSlicePath, resolveGsdRootFile, relGsdRootFile, relMilestoneFile, relSliceFile, } from "./paths.js";
+import { gsdRoot, milestonesDir, resolveMilestoneFile, resolveMilestonePath, resolveSliceFile, resolveSlicePath, resolveGsdRootFile, relGsdRootFile, relMilestoneFile, relSliceFile, clearPathCache, } from "./paths.js";
 import { join } from "node:path";
 import { readFileSync, existsSync, mkdirSync, readdirSync, rmSync, unlinkSync } from "node:fs";
 import { readSessionLockData, isSessionLockProcessAlive } from "./session-lock.js";
@@ -486,6 +486,12 @@ export function maybeHandleReadyPhraseWithoutFiles(event) {
     const text = extractAssistantText(lastMsg);
     if (!READY_PHRASE_RE.test(text))
         return false;
+    // Bust paths.ts cached dir listings before checking for fresh writes. The
+    // LLM's Write tool calls do not invalidate paths.ts caches, so a stale
+    // listing taken before the milestone dir or its CONTEXT/ROADMAP files
+    // existed would falsely report the artifacts as missing and trigger the
+    // 3-strike "ready without files" abort even though the writes succeeded.
+    clearPathCache();
     // Gate: artifacts must still be missing — if they exist, the happy path
     // already fired and we have nothing to do.
     const contextFile = resolveMilestoneFile(basePath, milestoneId, "CONTEXT");