the-custodian/docs/changes/netkingdom-target-2026-10-16/browser-checker-artifact-next

Exact offline checker artifact candidate

Prepared for NK-WP-0048-T16. This replaces the synthetic executable only in disposable adapter tests. It does not change canonical adapters, type/case bytes, source pins, credentials, cluster state or any native admission.

The existing KeyCape build target is src/cmd/keycape, selected from published clean source revision 3c71226a1a7b8a2bdb710e9c497e1a1f7f8a3987, source tree f0010b9cab17dbc3a787628a29657d98b900320f. The existing source Makefile and Dockerfile build this same command. Its early check-config dispatch uses config validation and placeholder secret lookup, with no key-file or upstream access. This is inspection of owner source, not owner endorsement.

build_checker.py archives that exact source into /tmp, uses the already cached Go 1.23.0 toolchain with CGO disabled and fixed Linux/amd64 v1 target, -trimpath, -buildvcs=false, read-only module selection, and no proxy/checksum network access. All environment inputs are explicitly retained. Complete file hashes cover 108 source files, 9876 toolchain files and the ten module source directories used by the actual package dependency graph. The resulting static checker is 13633409 bytes, SHA256 be37738fe1c08259fb4f9ca0daf0f9301bfffc237e5bb38435525dfbf11ccff5. Three separately located isolated builds produced identical artifact hashes.

test_real_checker_adapter.py runs eight checks with this exact executable and complete synthetic configuration. No config-checker stub remains. The checks cover actual helper byte-preserving add/removal, actual Warden pinned producer admission/run/rollback, lost-readback uncertainty/replay refusal, rollback drift, stale CAS, substituted checker refusal, invalid startup config and missing secret-env refusal. Owner evidence/session trust and Kubernetes objects remain synthetic. The attended registration procedure remains unexercised.

Retained failures matter: the first closure command (go list -m all) required unused lazy-module graph metadata absent offline; the second package-list command omitted the build's -buildvcs=false flag and failed on the archived tree. Both builds succeeded; closure collection was corrected without downloading modules. Their scripts/receipts remain in closure-collection-r1/ and r2/. minimal-fixture-refusal.json records the real checker rejecting the original incomplete synthetic fixture; only the new disposable fixture was completed.

Review dependencies remain concrete: KeyCape owns endorsement of this exact source/checker behavior; NetKingdom owns selection of its exact executable and new descriptor composition; Warden owns global evidence and parent-session revocation admission. Host storage/executable custody, per-attempt native callbacks, full descriptor step set, acknowledged type/version integration, structural/mint/delivery and consumer login/group acceptance remain separate. The new proposed-descriptor.json is an artifact-bound source proposal only.

Reproduction uses no production input:

PYTHONPATH=/home/worsch/ops-warden/src python3 docs/changes/netkingdom-target-2026-10-16/browser-checker-artifact-next/test_real_checker_adapter.py

The default test artifact is /tmp/nk-checker-artifact-next-r3/keycape; build reproduction requires a fresh isolated output directory and the pinned cached module/toolchain sources. See the exact retained build script/receipt, closure manifest and artifact build information. No production checker installation or execution is authorized by these receipts.