feat: integrate durable authorization audit and runtime composition

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e747-8f27-7242-8df8-8bc44f88c929

workplans/HUB-WP-0012-netkingdom-platform-root-access.md

@@ -272,6 +272,36 @@ themselves as `test`, since production no longer permits anonymous durable ports
 
 Validation results are recorded in [implementation evidence](../docs/evidence/hub-wp-0012-source-20260928.md).
 
+## Owner integration continuation — 2026-09-28
+
+Committed and synced the initial foundation as `3e38614`. The follow-up
+[owner integration review](../docs/owner-access-integration.md) documents source
+contracts and delivers a real Audit Core sender plus explicit runtime composition.
+The sender verifies operational durable custody and exact receiver acknowledgements,
+rereads its own credential, and blocks execution on lost receipts or rejection.
+Signed decisions survive archive serialization for independent verification.
+The runtime owns the composed HTTP client's lifecycle; configuration alone cannot
+activate missing authority adapters.
+
+Owner-source tests exercise the actual Audit Core receiver/storage, a complete
+fixture JWT→policy→audit→Hub write, and grant withdrawal denial. Their local SQLite
+operational-readiness override is explicitly synthetic, not a live custody claim.
+
+Two T01/T02 contract gaps now have concrete source evidence: User Engine's
+`platform:root` requires an explicit mapping to canonical `tenant:platform`, and
+`GET /api/v1/me` may provision an unknown account. It must not be used as Hub's
+read-only account/entitlement oracle. Tenant Engine's live role endpoint also
+needs an admitted authenticated Hub caller, not just an asserted actor query.
+The existing `audit-core-senders` routing entry points to ops-mason/OpenBao and
+is unresolved; no Hub sender credential was minted or retrieved.
+
+Validation: **304 full-suite tests pass**, plus the final seven owner/denial checks;
+wheel build and inventory validation pass.
+[Continuation evidence](../docs/evidence/hub-wp-0012-owner-integration-20260928.md).
+
+T01–T04 remain `progress`; live owner acceptance and the later milestones remain
+open. No production deployment, entitlement or public listener changed.
+
 ## Acceptance checkpoints
 
 - [x] Architecture/source/runtime review captured; new implementation owner is hub-core