Correct historical navigation and checkpoint scratch guidance

doc/agent-files.md

@@ -39,8 +39,10 @@ workspace sync, Git staging, or task deliverables.
 
 Sandbox transfer scratch lives separately under
 `.paperclip-runtime/paperclip-runner/agent-file-transfers/<agent>/<run>/`.
-Both native sync and the command fallback keep transfer files outside
-`AGENT_HOME`, including recovery after controller restart. Cleanup removes
+Workspace-staging transfer scratch stays outside `AGENT_HOME`, including
+recovery after controller restart. Remote warm Codex checkpoints may temporarily
+stage changed-file payloads under `AGENT_HOME/.paperclip-runtime/checkpoint-*`;
+these are checkpoint scratch, not managed personal files. Cleanup removes
 only the original materialization's agent directory and transfer scratch
 through its owned lease. A later warm turn keeps that original materialization
 identity; it does not grant collection or cleanup of another run's files.

doc/architecture/runner-rich-acp-capabilities.md

@@ -38,7 +38,7 @@ seeded test control plane. That protocol case does not qualify the Product UI.
 File validation, pending-input controller restart, and three-turn warm
 continuation remain failed and unregraded. Assertion repairs and an actual
 SDK/wrapper replay now cover the identified boundaries; fresh live proof is
-still required. See the [historical Pi checkpoint](runner-pi-capabilities.md#profile-13-qualification-checkpoint-2026-10-02)
+still required. See the [historical Pi checkpoint](runner-pi-capabilities.md#historical-profile-13-qualification-checkpoint-2026-10-02)
 for the request-stream diagnosis and remaining platform gates.
 
 Copilot's declaration hashes the shared sidecar, sidecar protocol, direct driver,
@@ -109,7 +109,7 @@ paid case at a time, and usage monitoring. The $5 reservation is counted once
 within the combined $100 campaign budget. Native price estimates are never
 substituted for provider bills.
 
-The [Pi capability inventory](runner-pi-capabilities.md#pi-10-candidate-2026-10-02-profile-v13)
+The [Pi capability inventory](runner-pi-capabilities.md#historical-pi-10-candidate-2026-10-02-profile-v13)
 records native interfaces, ACP mappings, user surfaces, and explicit gaps.
 The comparison below remains the supported-surface map; old observations retain
 their exact historical profile identities. Final source checks and profile-13
@@ -308,7 +308,7 @@ The [prior evidence checkpoint](runner-rich-acp-validation-2026-09-30-current.js
 | Pi v9 | Obtain an enforced provider spending bound, then run the unchanged required local/Daytona cases against the exact model and final runtime. Historical controls, question and hello passes do not qualify v9. |
 | All providers | Bind every required case to exact controller/runtime/profile and platform evidence, retain failures, complete source/dependency/pack end audits and owned cleanup, and reconcile actual spend within the $100 ceiling. CI and packaging do not substitute for this paid evidence; native Cursor/Copilot per-run USD remains unknown. |
 
-The field inventories and [prioritized follow-ups](#explicit-gaps-and-follow-ups) distinguish native SDK/RPC capability, ACP exposure and Paperclip projection. Image inputs, structured tool diffs/media/raw arguments, secondary locations and typed exit codes remain partial or unused in the common path. Cursor's richer child details and discovery/configuration fields, Copilot's session-scoped files/assets and uncorrelated native notices, and Pi's queue-delivery/configuration fields remain explicit follow-ups. These optional surfaces are not silently claimed as supported or treated as new blockers for unrelated declared cases. Copilot native steering/fork/ask-user APIs do not imply ACP responders; Pi native fork/clone/export likewise have no mapped runner controls. Pi confirm reports `negative_or_cancelled` because No and dismissal are indistinguishable; accepted empty or whitespace-only input/editor responses are not representable by the current canonical form.
+The field inventories and [prioritized follow-ups](#historical-gaps-and-follow-ups--october-2-2026) distinguish native SDK/RPC capability, ACP exposure and Paperclip projection. Image inputs, structured tool diffs/media/raw arguments, secondary locations and typed exit codes remain partial or unused in the common path. Cursor's richer child details and discovery/configuration fields, Copilot's session-scoped files/assets and uncorrelated native notices, and Pi's queue-delivery/configuration fields remain explicit follow-ups. These optional surfaces are not silently claimed as supported or treated as new blockers for unrelated declared cases. Copilot native steering/fork/ask-user APIs do not imply ACP responders; Pi native fork/clone/export likewise have no mapped runner controls. Pi confirm reports `negative_or_cancelled` because No and dismissal are indistinguishable; accepted empty or whitespace-only input/editor responses are not representable by the current canonical form.
 
 | Retained paid observation | Outcome and limit |
 | --- | --- |