| .. | ||
| attempt-r2-preflight | ||
| attempt-r4-access | ||
| attempt-r4-stream | ||
| native-r2 | ||
| native-r3 | ||
| native-r4 | ||
| native-r5 | ||
| consistency-confirmation.json | ||
| consistency-receipt.json | ||
| final-tip-verification.json | ||
| forge-metadata-proposal.json | ||
| native-approval-pending.json | ||
| native-preflight-proposal.json | ||
| native-preflight.py | ||
| native-r3-approval.json | ||
| native-r4-approval.json | ||
| native-r5-approval.json | ||
| projected-tasks.json | ||
| proposal.json | ||
| rapp-blocked-object-candidate-check.json | ||
| read-only-preflight-outcome.json | ||
| read-only-preflight-proposal.json | ||
| read-only-preflight.py | ||
| README.md | ||
| remaining-findings.json | ||
| scanner-json-digest.patch | ||
| smtp-return-file-checks.json | ||
| smtp-return-finding.json | ||
| social-consistency-receipt.json | ||
| social-source-checkpoint.json | ||
| source-changes.json | ||
| sync-closeout-receipt.json | ||
JSON filename/SHA256 scanner candidate
Proposal SYNC-SCANNER-JSON-DIGEST-20261101, revision 1. This is a source candidate and review evidence, not a native activation receipt.
The existing reviewed YAML filename/digest exception rejects the equivalent JSON shape in the RApp source-pin and Custodian construction manifests. The candidate extends precisely that shape to a quoted JSON key/value, using the identical rule in both adapters. It does not allow ordinary secret keys, prefixed provider tokens, uppercase or extended-length values. Existing rule defaults, history traversal, scanner pin, time/size limits, inline-suppression refusal and fail-closed outcomes remain unchanged.
source-changes.json pins original and candidate source hashes. scanner-json-digest.patch includes both implementations and regression tests. proposal.json pins the built candidate and states verification/rollback and unapproved native status. Candidate build and ephemeral test checkouts are in /tmp/sync-scanner-candidate.
Validation: 12 local real-Gitleaks tests passed (37 unrelated tests deselected); full receiver FORGE_TEST_GITLEAKS=... go test -count=1 ./... passed in 150.087s. A prior Go invocation without that environment passed only scanner-independent tests and was superseded by this real-scanner run.
The founder returned the read-only artifact/config/guard/headroom receipt on 2026-11-02. It verifies the expected deployment, pod, node, old adapter, hook and pinned Gitleaks. CPU requests are 68%, memory requests 76%, and Forgejo uses Recreate. The original failed/refined metadata attempts remain recorded; the successful read-only execution grants no mutation authority.
The exact native preparation is now revision 2, under the same proposal ID; revision 1 remains unchanged. Approval packet SHA256: d22b1f555af96c203b7d68efd25e80815ce18ca4e3bf0dd3ab96b6f699d50237. It includes guarded stage/rollout/rollback, both scanner source changes and Apps source followthrough. Thirteen isolated filesystem/real receive cases and five controller tests passed. The initial missing temporary dispatcher fixture was retained as an unverified preparation attempt and replaced with an explicit offline fixture; native probes separately copy the live dispatcher. Live server dry-run, diff, probes and activation remain mandatory execution checks and have not run yet.
Native activation awaits exact founder approval under docs/agent-autonomy-decision.md ("The supervisor approves that proposal or performs it through the privileged execution path."). The agent must not borrow the founder admin kubeconfig. The prepared founder launcher is /tmp/forge-scanner-rollout.sh. Its sealed runner refuses unknown initial identity/guard/hook/source state and any packet drift.
The staged scanner in repo-manager and live receiver have not been altered by this candidate. Independent clean-file commits continue under the original policy.
Current execution outcome, 2026-11-02
The founder ran the exact revision-2 launcher. It failed during preflight with a suppressed Kubernetes command error, before staging or native mutation (native_mutation: false, no events). The exact failed read is not yet identified. Failure evidence is preserved in attempt-r2-preflight/; the reviewed packet is unchanged. A separate read-only diagnostic labels each check and outputs fixed failure categories; three tests passed, including raw-diagnostic suppression and receipt preservation. Founder invocation: bash /tmp/forge-scanner-diagnose.sh. Do not retry the old apply while this failure is unresolved; its existing receipt prevents an unreviewed retry.
The first diagnostic was returned: node/deployment/pod identity, readiness, old public hook and artifact guard all passed; existing repository hook inventory failed with remote exit1. Its selected receipt is preserved in attempt-r2-preflight/diagnostic-receipt.json. The pending request is now bash /tmp/forge-scanner-inventory-diagnose.sh to identify the specific filesystem condition without reading out hook contents. Five diagnostic tests pass, including real disposable filesystem cases.
Current proposed recovery, revision3
The founder's condition report found exactly one missing scanner fragment among171 repositories, at coulomb/markitect-main.git. This explains the safe revision2 refusal. Revision3, packet SHA256 df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34, restores only that old-policy fragment, verifies its dispatcher and all171 active hook sets, preserves the failed receipt, then reuses the sealed unchanged JSON rollout and six source changes. Seven controller and six real filesystem cases passed; the original scanner accepts this preparation and all source preimages remain unchanged. Await exact founder review/execution via /tmp/forge-scanner-recover-and-rollout.sh. This new repair is not covered by an inferred retry permission; it is concretely included in the reviewed revision3 action. Repair protection remains installed on later JSON rollback. Existing-history admission and the cause of missing adoption are not established by this repair.
Founder approval received for exact revision3 packet df1cb48259ec5411a3f8cd24d436078daf09d241c39448454526f0a796798c34 (User: Approve exact revision 3; request_user_input_async call_d07a070d30a54a538c872888bd5b0e30 item0, 2026-11-02). Attended execution is pending via bash /tmp/forge-scanner-recover-and-rollout.sh; the approval receipt is native-r3-approval.json. No new review is requested within this approved scope.
Revision3 result and proposed revision4
The founder executed approved revision3: the missing-fragment repair and171-repository coverage verification succeeded; candidate receiver probes passed; hook migration failed before deployment patch. The old policy/template/probes and protected metadata were verified by rollback. The repair remains installed. Exact failed receipts are preserved in native-r4/. The pinned Forgejo userspace reproduces the unsupported chmod --reference defect; workstation tests had missed it.
Revision4, packet SHA256 64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd, corrects numeric mode handling and exact known group-write restoration, reuses the existing verified immutable ConfigMap, and has a fresh execution/source gate. Eight shell image cases, a four-case171-repository/1539-hook controller run, three controller checks and runtime self-test passed. Candidate scanner/profile and six owner source hashes are unchanged. Await exact revision4 review; no native revision4 action has run. The proposed founder launcher is /tmp/forge-scanner-rollout-r4.sh.
Founder approval recorded for exact revision4 packet 64c73100f2347470fda1b8b3194dbf6a8009291d9d80223af463b3c5ecab52fd via User: Approve exact revision4; request_user_input_async call_f68b7e7de81a4c089e8864b3d66773a9 item0,2026-11-02. Attended execution pending at /tmp/forge-scanner-rollout-r4.sh; approval receipt docs/changes/2026-11-01-scanner-json-digest/native-r4-approval.json. Earlier failures and exact approvals remain preserved; no execution success is inferred from approval.
Current revision4 execution attempt failed at first get:nodes, before mutation. Packet/approval are unchanged and its failed receipt is preserved in attempt-r4-access/. The local bridge/API transport responds, public server certificate is not expired, and a tested read-only access classifier is ready at bash /tmp/forge-scanner-access-diagnose.sh. Await selected founder-context status before any unchanged retry; no renewed approval is requested.
Current revision5 proposal
Revision4's first access failure was followed by successful expected-node/admin diagnostics; the failed receipt was preserved before an unchanged approved retry. That retry passed preflight/dry-run/live tool self-test but cached staging timed out. Old-policy rollback/probes/metadata verified across171. Read-only native tests isolated unread input: empty input completed, full-input cached verification reached success but clients stalled on both protocols, and consuming/counting the full input completed both.
Revision5, packet SHA256 95c2724ea65ee3f4ce42b96bbb2b839b02169d62faa4c0a9a6c320cf65754643, adds only cached-stage input consumption/counting and a fresh receipt/source gate while reusing all sealed revision4 controls. Four pinned-image staging cases and two envelope tests passed; live read-only drain controls passed both protocols. Same binary/profile and six source hashes. Native revision5 awaits exact review via /tmp/forge-scanner-rollout-r5.sh; no new source/detector exception or deployment-field change.
Exact revision5 packet 95c2724ea65ee3f4ce42b96bbb2b839b02169d62faa4c0a9a6c320cf65754643 approved by founder via User: Approve exact revision5; request_user_input_async call_dc0f52ef1e344100916de075e794e113 item0,2026-11-02. Approval receipt: docs/changes/2026-11-01-scanner-json-digest/native-r5-approval.json; ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED. Native execution pending at /tmp/forge-scanner-rollout-r5.sh. All earlier failed outcomes remain preserved; approval is not verified success.