fix(grok): settle false file holds through inspected recovery

Preserve stopped-run fences and no-replay while allowing verified new user work. Honor disabled workspace access at the dispatch-failure retention owner.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/grok-bot-agent.md

@@ -82,3 +82,14 @@ to inspect it. Paperclip shows reported activity, not a complete remote transcri
 or computer recording.
 
 The admitted Grok execution contract has no access to the Runner's workspace files. Its managed Runner still keeps durable recovery state, but stopping that session does not require workspace file repair. Inspect the Bot in Grok, clear the connection's recovery hold in the agent's Runtime settings, and verify the routine again before assigning new work. This records inspection without asserting global Grok termination.
+
+Historical stopped Grok runs can have an incorrect workspace-file hold from an
+earlier release. Runtime shows Recovery needed for these runs even when the
+routine is healthy. After inspecting Grok, use Clear recovery hold and verify
+the connection again. Paperclip retires the false file obligation only when the
+original admission denied workspace access, the assignment is fenced, the
+coordinator has settled, and the exact managed Runner leases have stop receipts.
+The inspection preserves the old result, action uncertainty, and no-replay hold.
+Send a new task message to request fresh work. Inspection does not certify global
+Grok termination or delete any previously retained allocation. Such allocations
+still use the existing environment cleanup controls.

doc/plans/2026-10-13-grok-bot-production-readiness.md

@@ -261,3 +261,22 @@ assignment authority. Disconnect completes while storage is pending, and the
 late upload returns 403 with no attachment or publication receipt. Person write
 checks remain in place. The full repository command was interrupted when this
 new review finding arrived; its partial output is not a passing test result.
+
+## October 15 — Stop review follow-up
+
+Review found that hiding the historical file-repair card alone left the stored
+file obligation blocking fresh task input. Runtime inspection now finds these
+holds even after routine recovery. It retires only the false file fields after
+exact run, assignment, coordinator and managed-lease cleanup checks, archives
+the previous evidence, and preserves no-replay. A real authenticated readiness
+exchange and new user input are still required. No global provider-stop claim is
+created. Dot historical recovery controls remain available.
+
+The later dispatch-failure owner also now honors the validated no-workspace
+contract before asking for sandbox retention. Both external providers and the
+writable native path pass the runtime boundary regression. The review follow-up
+passes 128 focused protocol, recovery, cancellation and runtime checks. An initial
+negative assertion saw the earlier readiness gate instead of the revoked-session
+gate; the corrected test checks both before and after re-verification. Server
+typecheck passes after narrowing the native workspace union. Final current-head
+CI, review, deployed historical recovery and fresh Stop are still release gates.