the-custodian/docs/changes/netkingdom-target-2026-10-16/browser-case/README.md

Browser-case source implementation — NK-WP-0048-T06

Implemented in isolated /tmp/netkingdom-browser-target-20261016 from NetKingdom HEAD 994d11c869daf9624ac6da2adfdaeb86d8cdf537; canonical owner checkout untouched. implementation.patch changes only owner source, tool documentation, integration tests and the existing NK-WP-0048 workplan. The separate dirty-baseline patch retains the two pre-existing generated tracked diffs and is not part of the implementation; no untracked owner files or credentials were copied.

The existing validator now offers check-evidence, using the same declarations, composer, explicit type-version selection and normal admission. It checks real Mason structural Request source/projection/inventory and reads real Warden SQLite journal rows with read-only mode and bounded metadata. Exact descriptor pins, owner, latest outcome, creation scope, attempt and revocation fingerprints must agree. Unknown fields, forged native flags, stale source and missing proof fingerprints refuse. The 19 new integration checks call real Mason.prepare and Warden.Journal.save; final full scoped result is 103 passed. validation.json records the check details and isolated sibling-layout fix for existing suites.

This is a compatibility preflight, not authenticated completion. Existing owner artifacts cannot carry portable authenticated native receipts: Mason Request is source-only and Warden journal preserves fingerprints. The checker therefore never claims native complete or permits execution, even with matching artifacts. Exit 0 means supplied source artifacts match; it is not an admission token. Normal 1.1 and 1.2 commands still reject acknowledged/unimplemented types. The saved preflight JSONs use explicit --allow-unimplemented source preparation.

Reachable next owner implementation

1. Warden must adapt browser metadata admission before a native attempt. Its src/warden/case_run.py:421 loop currently accepts only public/operational case parameters. Actual 1.1 redirect_uris, allowed_scopes, client_type and mfa_required, plus 1.2 consumer_namespace, are security_sensitive. An actual Executor.admit test with the existing Warden fixture and only its parameter sensitivity changed to this actual classification returns unknown, fixed or secret-sensitivity case parameter. Test evidence is warden-admission-mismatch.json. No dispatch occurs. The owner fix should reuse NetKingdom's exact-version validator to validate the complete case, distinguish security-sensitive metadata from credential material, and project only the descriptor's accepted target fields. Do not widen the journal to raw parameters or weaken credential/unknown/fixed-value checks. This source work belongs to WARDEN-WP-0044-T03; this worker has not edited Warden.
2. Warden/Mason/Platform need an actual authenticated owner-evidence admission mechanism that binds source, target, actor/lane, attempt, creation ownership and current native observations. The existing injected fake test verifiers and unsigned JSON are not that mechanism. NetKingdom's checker deliberately has no trust=True callback or native admission flag.
3. Owner-accepted exact machine descriptors must be pinned through a reviewed type revision; current 1.1/1.2 descriptive types have none. Do not hand-edit them into acknowledged history. Mason still needs explicit 1.2 source-root adoption and a regenerated six-object request/bundle; its current legacy bundle is 1.1 and has a known incorrect consumer workload target. Integration tests correct a copied fixture only, preserving the historical source.

Native gates retained

Native six-object structure/CCR42 claims and created-versus-preexisting receipts; accepted-case to materialized-case exact raw-hash binding; installed broker and case/type/source reconciliation; separately authorized mint and two deliveries; attended groups/env/registry and consumer configuration; actual sign-in and consumer group denial; distinct broker-grant and parent-session revocation; created-only rollback with UID/ownership checks and issued-token revocation or expiry. 1.2 remains proposed-case/acknowledged-type source. T06 remains wait and T07 retains its first-case dependency. No live or implemented-type claim follows.

The withheld knowledge orientation was inspected: emergent-security package 0.2.6, digest 8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02. Current NetKingdom INTENT/SCOPE/Security Companion and actual owner source seams were read directly. No owner approvals or supervision promotion were authored. Canonical integration, State Hub reconciliation and aggregate session progress remain with the parent Custodian session after patch acceptance/publication.