the-custodian/docs/changes/netkingdom-target-2026-10-16/browser-acceptance-next
codex 5a50901d9a
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Reject generated-only commits / generated-commit-guard (push) Successful in 8s
Record installed inert consumer and canonical runtime proof
2026-10-16 21:32:07 +02:00
..
coordinator-review.json Record installed inert consumer and canonical runtime proof 2026-10-16 21:32:07 +02:00
README.md Record installed inert consumer and canonical runtime proof 2026-10-16 21:32:07 +02:00
validation.json Record installed inert consumer and canonical runtime proof 2026-10-16 21:32:07 +02:00

Browser acceptance dependency checkpoint

NK-WP-0048 source repair, 16 October 2026. Source commit 015694e.

The current owner-local blocker was a contract mismatch: Warden's existing execution_descriptors map was forbidden by NetKingdom's closed JSON schema, while NetKingdom's Python validator silently accepted malformed map values. That would prevent valid future descriptor source integration and could crash the evidence compatibility path. The repair adds the optional bounded exact-byte pin map to the schema and semantic validation, binds keys to declared steps, and makes the direct evidence API refuse malformed maps. It supplies no descriptors, owner acknowledgment, admission callback or execution authority.

Validation: 21 new contract checks; all 127 affected tests pass in an isolated checkout and canonical owner source. The canonical run reports two read-only pytest cache warnings. Focused diff whitespace checking passes. The normal Git scanner accepted all six committed files. Existing staged brief and unrelated changes are preserved. Exact base/file hashes and preserved type/case hashes are in validation.json; implementation.patch retains the source repair.

The workplan now records completed checker source (T10), completed pin-contract repair (T11), and the independently actionable next source task: NetKingdom-owned attended registration/config/env/group adapters or receipt-only steps (T12). T06 retains native acceptance and T07 remains dependent. This records outcomes without counting fixtures as operational proof.

The first browser case still lacks exact independently admitted owner descriptors and adapters, authenticated native structural/status-binding receipts for all six 1.2 objects, exact broker/case source reconciliation, separately authorized mint/delivery, attended registry/group execution, real human sign-in and denied groups, revocation and created-only rollback. Canonical 1.1 remains acknowledged with its historical accepted case; 1.2 remains acknowledged with a proposed case. Ordinary admission refuses both unimplemented types. TSA-04 and TSA-05 remain open. No credentials, live security changes or other owner's assent were requested.