Record approved scanner revision 5 and verified cached-stream correction

workplans/CUST-WP-0083-fleet-sync-and-scanner-remediation.md

@@ -59,17 +59,17 @@ status: progress
 decision_id: "5410707c-ce73-4f80-9c03-805102c31c58"
 priority: high
 needs_human: true
-intervention_note: "Approved unchanged revision4 failed at first get:nodes before mutation. Run bash /tmp/forge-scanner-access-diagnose.sh in the founder terminal and return selected access status. Bridge/API transport responds; actual credentials/configuration failure not yet classified. Existing approval is retained."
+intervention_note: "Founder approved exact revision5 packet 95c2724ea65ee3f4ce42b96bbb2b839b02169d62faa4c0a9a6c320cf65754643. Run bash /tmp/forge-scanner-rollout-r5.sh in the founder terminal and return sanitized result. Cached-input fix only; all prior controls and six source postimages remain unchanged."
 state_hub_task_id: "589e1a54-9a4e-5f90-bd29-5c61a6cf8081"
 ```
 
-Human-lane checkpoint, current 2026-11-02: approved revision3 repaired the missing markitect-main fragment and verified171 active old-policy scanner fragments plus unchanged protected metadata. Its native JSON candidate probe passed. Hook migration then failed before deployment patch; rollback verified the old template/policy, all171 fragments and old-policy probes. The repair and original failed receipts remain intact. Same-image reproduction identified an unsupported `chmod --reference` command that workstation tests missed.
+Human-lane checkpoint, current 2026-11-02: the missing markitect-main old-policy fragment is repaired and171-fragment coverage/metadata/probes verified. Exact approved revision4 first failed at an initial access read before mutation. A subsequent founder probe verified expected node/admin identity, and that zero-mutation receipt was preserved before the unchanged authorized retry.
 
-Revision4 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r4/PLAN.md`, packet SHA256 `64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd`. It uses portable numeric mode copying, restores only known group-write additions to unchanged/owned hook inodes after pod recreation, verifies/reuses the already-created immutable ConfigMap, and uses a fresh native/source receipt gate. Same scanner/profile, two deployment fields and six source candidates; prior packets/receipts are unchanged. Eight pinned-image shell cases, four full-controller cases across171 repositories/1539 hooks, three controller checks and the runtime self-test passed. The six owner-source preimages remain unchanged. The founder explicitly approved exact revision4 via User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02. Attended native execution is pending at `bash /tmp/forge-scanner-rollout-r4.sh`; no additional approval is requested within that scope. Source activation awaits verified native outcome. The verified failed revision3 is recorded as failed, with the earlier unscored revision2 preserved in the same trial.
+The retry passed preflight/server dry-run/live tool self-test but cached staging timed out before any deployment patch. Rollback verified old policy/template, all171 fragments, exact hook metadata and real receiver probes. The artifacts themselves are valid: empty-input cache verification completed; both full-input nonconsuming commands reported remote verification but client-timeout; consuming/counting all3437906 bytes completed on both transports. Failure/diagnosis/earlier approval evidence is preserved in `attempt-r4-access/` and `attempt-r4-stream/`.
 
-Execution update, 2026-11-02: the founder ran approved revision4, which failed at the first `get:nodes` read. Receipt records no native mutation. Preserve it in `docs/changes/2026-11-01-scanner-json-digest/attempt-r4-access/`; no code/scope revision or renewed approval is requested. The bridge reports connected, the API answers anonymously401, and its public server certificate is valid until2027-03-10. These are transport checks, not authenticated target proof. A separate read-only diagnostic safely distinguishes access errors; three tests passed. Await `bash /tmp/forge-scanner-access-diagnose.sh` from the founder. Retry only after access and zero-mutation receipt are reviewed/preserved; original packet stays unchanged.
+Revision5 is prepared at `docs/changes/2026-11-01-scanner-json-digest/native-r5/PLAN.md`, packet SHA256 `95c2724ea65ee3f4ce42b96bbb2b839b02169d62faa4c0a9a6c320cf65754643`. It adds only cached-stage input consumption/counting, preserves fresh staging and all revision4 control behavior, and uses fresh native/source receipt gates. Four pinned-image stage cases and two envelope tests passed; native read-only input-completion controls passed both protocols. Same candidate/profile, deployment fields and six source postimages. The founder explicitly approved exact revision5 via User: Approve exact revision5; request_user_input_async call_dc0f52ef1e344100916de075e794e113 item0,2026-11-02. Attended execution is pending at `bash /tmp/forge-scanner-rollout-r5.sh`; no further approval is requested for this exact scope. No revision5 native action or six-source application has run; earlier failures remain one preserved trial.
 
-Installing the repaired fragment does not retroactively admit existing history or establish why adoption missed this repository. Preserve historical/lifecycle coverage limits and source-owner class-level followup in T03 and the final audit.
+Carry the native-image and exec-stream testing lessons into T03's class-level prevention guidance. Historical admission, why adoption missed one repository and full Forgejo lifecycle coverage remain unproved by fragment repair.
 
 ## Verify complete remote publication and report exceptions