feat(toolintent): stale-write gate

Block writing a file whose on-disk content changed since the session read it — a concurrent/external edit the agent's view doesn't reflect. file_read records a content hash on whole-file reads; the orchestrator's completion path now carries the tool's structuredOutput (it previously dropped it, unlike SandboxedToolExecutor — the two paths were inconsistent), so SessionContext.readHashes folds it. StaleWriteRule compares the current hash (WorldProbe.contentHash) against the read-time hash and BLOCKs a mismatch, telling the agent to re-read first. Files the session wrote itself are excluded, so its own edits never look stale; partial reads set no baseline. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 06:15:15 +00:00
parent 4159361690
commit 6a779861c2
8 changed files with 183 additions and 1 deletions
@@ -1289,6 +1289,10 @@ abstract class SessionOrchestrator(
                            toolName = toolCall.function.name,
                            exitCode = result.exitCode,
                            outputSummary = result.output.take(OUTPUT_SUMMARY_LIMIT),
+                            // Carry the tool's structured metadata (e.g. file_read's contentHash) so
+                            // session projections can read it — matching SandboxedToolExecutor, which
+                            // already does this; the two completion paths were inconsistent.
+                            structuredOutput = result.metadata,
                            affectedEntities = affected.map { it.toString() },
                            durationMs = 0,
                            tier = tier,