Record verified signer image and simpler maintenance ownership

docs/netkingdom-target-implementation.md

@@ -230,8 +230,12 @@ receipt parsing because the runner lacks Python. Public package metadata and the
 run's push/pull evidence identify the published digest and exact revision; the
 failed run remains failed. Access `84c78e0` replaces that parser with existing
 Bash/Docker facilities, verifies the pulled revision label, and records the local
-package reference. Three independent publisher tests pass. Normal source publication and synchronization passed; successor CI is being
-observed. No deployment follows automatically.
+package reference. Three independent publisher tests pass. Normal source publication
+and synchronization passed. Ordinary publisher run402 and both smoke jobs in run401
+succeeded for exact `84c78e0`; independent public package metadata confirms image
+`sha256:09a83b273740133518cc7e7915fb211381e06545d347d2dd1974042525ac981f`
+and its revision label. The [independent image review](changes/netkingdom-target-2026-10-16/access-native-admission/image-84c78e0/coordinator-review.json)
+retains this evidence separately from failed run400. No deployment follows automatically.
 
 Audit `64509d2` defines the first pin's admission and complete-ledger reconciliation
 using existing receiver APIs. Independent root checks passed 17 tests plus the
@@ -266,6 +270,35 @@ The [source wave receipt](changes/netkingdom-target-2026-10-16/source-wave-statu
 records exact publication and synchronization results. Temporary review checkouts
 and agent handles remain preparation artifacts, not runtime deployments.
 
+Two preparation dependencies are now simplified in published source. Access
+`dc04202` permits exactly zero or one outbox writer through the ordinary Helm
+chart, removing the separate hand-derived stopped manifest. Both charts reject
+unsafe replica values; 86 actual Helm render cases and the existing outbox suite
+pass. The chart successor explicitly retains the independently verified `84c78e0`
+image; chart and binary revisions remain distinct.
+
+Platform `84c529f` replaces the conflated cluster/GitOps reviewer with the exact
+runtime/storage owner. Access owns workload and Helm release changes; Platform
+owns existing GitOps Applications and their sync/freeze integration; cluster
+owns runtime, headroom and storage review. Enablement participates if an actual
+controller installation change is proposed. Independent checks passed 45 native
+preparation tests and 54 overlapping cluster custody tests. The focused CCR
+validates but remains proposed with unconfirmed claims. A normal scanner refusal
+on ambiguous public image references was corrected with complete typed OCI
+references; the unchanged scanner then accepted all six files. The full CCR
+validator retains unrelated baseline CCR0035 errors.
+
+Both commits have verified publication and normal synchronization receipts.
+Cluster's own review record was published as `RCLUSTER-WP-0017`. Its source-only
+review accepts the exact Platform role correction. The sync prefix warning is a
+reporting defect: ADR-007 explicitly assigns `RCLUSTER-WP`, while the checker
+infers the retired prefix from the historical file majority. Existing identifiers
+and UUIDs remain correct and unchanged. This review grants no native action.
+Frozen rollout R1 and custody P2 remain historical preparation;
+their successors must bind the new source revisions and distinct owner scopes.
+The [coordinator checks](changes/netkingdom-target-2026-10-16/source-wave10-coordinator-review.json)
+retain the source proofs separately from deployment acceptance.
+
 ## Dependency and residual handling
 
 The current implementation demand selects necessary target dependencies for