13 lines
2.1 KiB
Markdown
13 lines
2.1 KiB
Markdown
# 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.
|
|
|
|
Native preparation is pending read-only inventory. Current Kubernetes identity `ops-mason-builder` cannot list nodes, deployments or pods in `forgejo`. Do not borrow the founder's admin kubeconfig. The prepared `forge-metadata-proposal.json` uses gated-executor's exact-action format for only names, UIDs and images. Its digest is `sha256:0fceb2dc3c1963a16f40a0221b2eb6cb5384b91e2fe8607bb0121afe47a5d2e1`. The founder was asked to return this metadata or provide the supervised execution result. A native update needs its own exact inspected rollout proposal and supervisor approval under `docs/agent-autonomy-decision.md` and environment-orientation §4.
|
|
|
|
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.
|