fix: recover canonical onboarding authority

Author: misunders2d

PUBLIC_RELEASE_STATUS.md

@@ -11,32 +11,37 @@ requirements, gate ledgers, or accountable-owner evidence.
 Reads of the public npm registry and immutable Git tag returned:
 
 - package: `@misunders2d/agentnet`
-- latest published version: `0.1.45`
-- published source commit: `e8a49671481767078551f677599f51af051c3d5a`
-- immutable tag: `v0.1.45`
-- registry shasum: `06f4775ecf63097068e1f3583fe84a2c66c64096`
+- latest published version: `0.1.50`
+- published source commit: `c7c5659055884b3a6fa4ad05f1e43b7e7e844436`
+- immutable tag: `v0.1.50`
+- registry shasum: `4875fd0e37b8a12689a6a50772b89e118931e7d7`
 - provenance: SLSA statement signed by the trusted GitHub Actions publisher and
   approved by the accountable npm owner
 
-`0.1.45` is a **fresh-install-only** release. In-place upgrade from `0.1.44` is
-not a supported path: the packaged upgrade and rollback lane is preserved as
-non-green, so operators must install `0.1.45` on a clean host and re-enroll the
-server and each harness. Publication is gated on the ordinary-server
-clean-install lane, which is the exact path operators follow.
+`0.1.50` is the published setup-usability release. It supports the exact
+allowlisted schema-v7 five-unit upgrade paths documented by that immutable
+package. Publication does not prove installed-host convergence, production
+durability, or any must-not-ship gate.
 
 Package availability does not authorize deployment and does not establish
 production readiness. No must-not-ship gate is promoted by publication.
 
-## Setup-usability `0.1.50` candidate
+## Corrective `0.1.51` candidate
+
+Candidate `0.1.51` retains the published `0.1.50` setup and laptop protocols
+and adds package-owned convergence for the exact ordinary-onboarding
+placeholder Approval owner and for a committed communication scope missing
+its schema-v7 collaboration projection. The target owner is derived from
+enrolled Core identity plus Approval's pinned OIDC binding; signer and Core
+policy cutover is journaled and resumable. New scope activation writes its
+projection atomically, and legacy repair derives it from the existing
+committed scope without replacing authority.
+
+The candidate accepts only exact five-unit schema-v7 markers from v0.1.45
+through v0.1.50. Ambiguous, drifted, incomplete, or unsupported state fails
+closed. Package, installed-host, dedicated-PostgreSQL, and live two-machine
+validation remain pending; no production or gate claim is made.
 
-Candidate `0.1.50` wraps the existing strict server and laptop protocols in
-one resumable command per machine. It adds authenticated discovery defaults,
-content-free named phases, bounded deadlines, exact blocker/recovery output,
-and direct allowlisted upgrades from exact v0.1.45–v0.1.49 schema-v7 five-unit
-markers. Packed-package verification requires an installed separate-process
-message/obligation roundtrip. Release artifacts, complete validation, fresh CI,
-and publication remain pending. This local implementation does not promote a
-requirement, production claim, or must-not-ship gate.
 
 ## Corrective `0.1.49` candidate
 

README.md

@@ -441,7 +441,7 @@ always-on deployment—see the [implementation guide](docs/implementation-guide.
 ## Project status
 
 AgentNet is an early public implementation; the latest published package is
-`0.1.45`. Its publication does not promote any requirement or gate.
+`0.1.50`. Its publication does not promote any requirement or gate.
 Published `0.1.29` repaired owner/enrollment OIDC callback parsing after real
 Google owner login exposed rejection of valid unique response extensions;
 published `0.1.30` repaired installed-verifier package custody; published
@@ -543,6 +543,20 @@ addition to the existing installed journey. These are local and CI evidence,
 not production certification, and no requirement or must-not-ship gate is
 promoted.
 
+Candidate `0.1.51` adds the package-owned corrective recovery path for the
+exact ordinary-onboarding state where Approval still names the setup
+placeholder owner after Core enrolled the canonical human. Managed setup
+derives the target only from the enrolled Core identity and Approval's pinned
+OIDC binding, rotates current Approval signing authority to that principal,
+and journals resumable Core policy replacement. It rejects identity, domain,
+OIDC, signer, database, configuration, or journal ambiguity. New communication
+activation writes its complete schema-v7 collaboration projection in the same
+transaction; an already committed scope missing that projection is repaired
+from its immutable scope rows without replacing the scope or minting broader
+authority. Exact five-unit schema-v7 markers from v0.1.45 through published
+v0.1.50 may upgrade directly to v0.1.51.
+
+
 Git tag `v0.1.23` reached the staging workflow, but CI stopped before npm
 staging because one hermetic interruption test mocked `/usr/bin/useradd` on a
 runner where that path did not exist. No `0.1.23` package was staged or

RELEASE_MANIFEST.json

@@ -218,7 +218,7 @@
     "path": "uv.lock",
     "pyproject": {
       "path": "pyproject.toml",
-      "sha256": "95c9effe37951f5ab012aa00743ecc52b44ca0ac0b62ab08eddafa3ab7559e7a"
+      "sha256": "6aebcdea17d2715c3136c2b6b3179a424a3eed990f54d65a4cccbf67c715c5da"
     },
     "resolution": {
       "a2a-sdk": "1.1.0",
@@ -285,7 +285,7 @@
       "webauthn": "3.0.0"
     },
     "revision": 3,
-    "sha256": "afffa3558290939ca4f3efae1b04559db3299084f4a62c0d93ccdd4ab66e69c8"
+    "sha256": "c971fdea8d3782a9d7349b5723f4e036740d314f19f7c3553dc6ba1780c9f84d"
   },
   "external_release_evidence": {
     "installer_lifecycle": {
@@ -529,20 +529,20 @@
   "release": {
     "name": "agentnet",
     "production_ready": false,
-    "profile": "setup_usability_candidate",
+    "profile": "canonical_owner_recovery_candidate",
     "reason": "All 19 must-not-ship gates remain non-PASSED; local implementation evidence is partial and required external, privileged, production-topology, or owner evidence remains absent.",
     "ship_eligible": false,
     "status": "BLOCKED",
-    "version": "0.1.50"
+    "version": "0.1.51"
   },
   "release_inputs": {
     "README.md": {
       "path": "README.md",
-      "sha256": "f6839282457daeeb8cad2b76621b384725cb6caac15e92ad3e09f72633fcbbe3"
+      "sha256": "f594836e220538cac9c41da74a7a02dcaaebc05534a2fa0bae1302b19ee21a26"
     },
     "REQUIREMENTS_STATUS.md": {
       "path": "REQUIREMENTS_STATUS.md",
-      "sha256": "59491a96c8697c41c47d29756144768f5b62da0df04c3d75c9579dc762dae0d8"
+      "sha256": "18c34a4e0224e68ccc68e71a970b398fc1e1bc1547c4ce4b00a43554b6887340"
     },
     "deploy/Dockerfile": {
       "path": "deploy/Dockerfile",
@@ -562,11 +562,11 @@
     },
     "docs/GATE_EVIDENCE.md": {
       "path": "docs/GATE_EVIDENCE.md",
-      "sha256": "1d690b65756169e1954c1a37c0436bc3dc053e903e61dd4a647a0a0f786be6e2"
+      "sha256": "83e5178c205b2808f9155ff245469a6234abf616cefac36f604badabbaa4419f"
     },
     "docs/RELEASE_MANIFEST.md": {
       "path": "docs/RELEASE_MANIFEST.md",
-      "sha256": "99fb7ad44dfb05766c59ac69c1decb1df9e951984c7196acb53c37179d2d99ad"
+      "sha256": "5953a7a3d47c10f145243ba82db76457f09fb7326f1d4373175a29087e776cd5"
     },
     "evidence/gates/G01/2026-07-13-installed-harnesses/manifest.json": {
       "path": "evidence/gates/G01/2026-07-13-installed-harnesses/manifest.json",
@@ -602,13 +602,13 @@
     },
     "scripts/verify_release.py": {
       "path": "scripts/verify_release.py",
-      "sha256": "b559a98eb5050f54a9d4d222ef83e2b6bda16af5c79860699d0eace2c1661d00"
+      "sha256": "612baa0e73b836f7411cc8f76f5698d750bfd5a77cbad8f94c70d6ac9f59bb01"
     }
   },
   "release_source_tree": {
     "algorithm": "sha256(path NUL bytes NUL)",
     "path": "src",
-    "sha256": "740adfb28e27641c3ec0bab470036c4690fde2c70a53ab0568fde644aecddb7e"
+    "sha256": "0906475b88bb57673fa2ab4ea793803d9931fad36e97a00519d52f7bb39685ea"
   },
   "runtime": {
     "implementation": "CPython",
@@ -746,5 +746,5 @@
     },
     "version": "1.0"
   },
-  "snapshot_date": "2026-08-07"
+  "snapshot_date": "2026-08-09"
 }

REQUIREMENTS_STATUS.md

@@ -1,6 +1,6 @@
 # Requirements Status
 
-Snapshot: 2026-08-07. This is an implementation/evidence ledger, not a release
+Snapshot: 2026-08-09. This is an implementation/evidence ledger, not a release
 certificate. It contains the exact 85 stable requirement IDs from the preserved
 requirements reference. PD-001 through PD-011 are listed separately because
 they are accountable policy decisions, not additional requirements.
@@ -428,6 +428,31 @@ published and historical release evidence:
   `UX-001`, `UX-002`, `SEC-003`, `SEC-005`, `OPS-003`, and `OPS-006`. No
   requirement or must-not-ship gate is promoted.
 
+- Corrective v0.1.51 work replaces the manually demonstrated live recovery
+  with a package-owned, bounded path for the exact ordinary-onboarding
+  placeholder-owner state. Approval owner/passkey custody and current signer
+  authority converge to the enrolled Core principal only when exact domain,
+  OIDC, credential, row-shape, configuration, and journal evidence agrees.
+  Setup journals the corresponding Core policy cutover and resumes exact
+  partial writes; unsupported or ambiguous state fails closed. Communication
+  activation now materializes the complete schema-v7 collaboration projection
+  atomically with scope commitment, while a committed legacy scope is repaired
+  idempotently from its server-held source rows without replacement or generic
+  entitlement minting. The focused recovery lane reports **347 passed**; the
+  broad releasable-source lane reports **2204 passed and 22 expected
+  platform/dedicated-PostgreSQL skips**; and source plus two recursive packed
+  generations each report **2231 passed and 22 expected skips**. Two independent
+  builds are byte-identical, packaged local message/obligation processing
+  reaches `recipient_committed`, and a fresh installed npm package passes exact
+  endpoint routing with zero sibling reactions or residue. Dedicated
+  PostgreSQL, installed-host setup/upgrade, same-commit CI, and live two-machine
+  evidence remain pending. Affected IDs are `ID-001`, `ID-002`, `ID-005`,
+  `ID-006`, `AUTH-001`, `AUTH-002`, `AUTH-003`, `AUTH-004`, `AUTH-005`,
+  `COM-001`, `COM-002`, `COM-009`, `AVL-003`, `AVL-005`, `SEC-003`, `SEC-005`,
+  `SEC-007`, `OPS-003`, and `OPS-006`. No requirement or must-not-ship gate is
+  promoted.
+
+
 
 
 - S5/S6 directly exercise `ID-006`, `AUTH-001`, `AUTH-002`, `AUTH-003`,

docs/ARCHITECTURE.md

@@ -895,4 +895,24 @@ revalidated before commit. Packed-package verification additionally executes
 the separate-process local message/obligation roundtrip; it remains H/L local
 evidence and does not prove production durability.
 
+The corrective v0.1.51 recovery remains inside this composition root. After an
+exact supported upgrade has established the enrolled Core identity, setup may
+classify only the known placeholder-owner, partial-repair, live-repair, or
+already-converged Approval shapes. A service-private command adopts the
+canonical owner and replacement P-256 receipt signer under Approval's OS
+identity. Setup then replaces the corresponding Core OIDC and approver policy
+through the existing root-owned upgrade journal. Exact journal phases make an
+interruption resumable; mismatched identity, OIDC subject, domain, signer,
+configuration, database shape, revision, or digest blocks startup.
+
+Communication-scope completion and legacy-scope repair share one schema-v7
+single-scope materializer. Completion invokes it inside the transaction that
+commits the scope, entitlements, revoke powers, members, audit record, and
+idempotent result. Repair derives the same projection only from committed
+server-held scope rows. Existing exact rows are a no-op; partial, extra, or
+conflicting rows roll back. Thus no success can expose a terminal active scope
+without its canonical collaboration authority, and recovery never replaces
+the active scope or grants generic access.
+
+
 `agentnet server-agent reset` is destructive server-manager-only package recovery. It acquires the same permanent root-only setup lock before inventory, rejects state without pre-existing lock custody, stops/disables and proves all five managed units inactive, removes only allowlisted package deployment units/state, and preserves the lock/root so a concurrent or later setup cannot lock a different inode. It always reloads systemd, including exact response-loss retry, and retains PostgreSQL, runtimes, package installation, proxy/TLS/DNS/firewall inputs, and locked service identities. Reset is not a browser action, onboarding step, or secret-rotation path. Exact AgentNet database/role reinitialization is a separate destructive operator boundary requiring sanitized target inventory, explicit named approval, an explicit backup/rollback decision, and redacted audit evidence; unrelated/shared/valuable targets fail closed.

docs/GATE_EVIDENCE.md

@@ -1,6 +1,6 @@
 # Must-Not-Ship Gate Evidence Ledger
 
-Current ledger update: 2026-08-07. Overall release posture: **blocked**. Older
+Current ledger update: 2026-08-09. Overall release posture: **blocked**. Older
 rows retain their exact run dates and remain historical evidence. This ledger
 separates checked-in historical release evidence from an explicitly labeled
 uncommitted worktree candidate, records only commands actually run for the stated
@@ -84,6 +84,8 @@ Gate statuses used here:
 | Candidate npm `0.1.48` canonical post-C0 credential correction | Completed-C0 terminal credentials now resolve through the exact domain/principal-bound harness plus credential epoch; unknown or mismatched identity state remains fail-closed. Adds only the exact forward-only `0.1.47→0.1.48` five-unit marker edge and no database migration. | Focused lane: `547 passed, 5 skipped`; broad releasable-source lane: `2155 passed, 21 skipped`; recursive packed-package and installed-host upgrade evidence pending. | H-only correction evidence; no gate promotion. Affected IDs: `ID-006`, `ID-009`, `SEC-007`, `OPS-003`. |
 | Candidate npm `0.1.49` completed-C0 communication recovery | Permanent communication activation resolves the exact completed C0 pair; only the authenticated ordinary server harness may advance to its current active credential, while the C0 peer remains pinned to its enrolled credential absent separately verified succession. Terminal pre-commit retries converge without replacing committed authority. Signed message send, inbox, and acknowledgement requests bind the exact collaboration scope. Adds only the forward-only `0.1.48→0.1.49` five-unit marker edge and no database migration. | Focused lane: `645 passed, 5 skipped`; broad releasable-source lane: `2166 passed, 21 skipped`; recursive packed-package and installed-host upgrade evidence pending. | H-only correction evidence; no gate promotion. Affected IDs: `ID-001`, `ID-002`, `ID-004`, `ID-006`, `AUTH-001`, `AUTH-002`, `AUTH-003`, `AUTH-004`, `AUTH-007`, `AUTH-009`, `COM-001`, `COM-002`, `COM-003`, `COM-006`, `COM-009`, `COM-011`, `AVL-003`, `AVL-005`, `AVL-006`, `SEC-003`, `SEC-005`. |
 | Candidate npm `0.1.50` setup-usability, direct-upgrade, and communication-scope approval path | One guided server command over the strict request/plan/apply protocol; one server-origin-only guided laptop command with authenticated discovery defaults; content-free named phases; ten-minute server and five-minute laptop bounds; resumable blocker output; exact direct allowlist from v0.1.45–v0.1.49 schema-v7 five-unit markers; installed separate-process local communication/obligation roundtrip added to packed verification; explicit one-hour Approval request ceiling limited to `authorization.communication_scope.approve`, with all other approvals retaining the five-minute ceiling and short-lived WebAuthn challenges | Focused release lane: `681 passed, 5 skipped`; broad releasable-source lane: `2180 passed, 21 skipped`; source and two recursive packed generations: `2207 passed, 21 skipped` each; two byte-identical release builds; release manifest verifier passed; installed tarball journey passed from an unrelated prefix; installed-host, fresh-machine, and same-commit CI evidence pending | H/L-shaped local candidate evidence only. No production, owner-policy, external, privileged-host, or gate promotion. Affected IDs: `ID-006`, `AUTH-004`, `AUTH-007`, `COM-001`, `COM-002`, `COM-003`, `COM-006`, `COM-009`, `AVL-003`, `AVL-005`, `AVL-006`, `UX-001`, `UX-002`, `SEC-003`, `SEC-005`, `OPS-003`, `OPS-006`. |
+| Corrective v0.1.51 canonical-owner and schema-v7 scope-projection recovery | Exact enrolled-Core plus pinned-Approval-OIDC owner selection; transactional Approval owner/passkey adoption; current receipt-signer replacement; strict resumable signer/config journal; journaled Core OIDC/approver cutover; single-scope schema-v7 projection shared by atomic activation and idempotent legacy repair; ambiguity, tamper, drift, partial-row, and conflicting-row rejection | Focused recovery lane: `347 passed`; broad releasable-source lane: `2204 passed, 22 skipped`; source plus two recursively packed generations: `2231 passed, 22 skipped` each; two byte-identical builds; installed-byte local communication reached `recipient_committed`; fresh installed npm exact-endpoint routing proved zero sibling reactions and no process/capability residue | Current source/package H/L-shaped evidence only. Dedicated PostgreSQL, installed-host setup/upgrade, same-commit CI, and live server/laptop reliability evidence remain pending. No requirement or gate promotion. Affected IDs: `ID-001`, `ID-002`, `ID-005`, `ID-006`, `AUTH-001`, `AUTH-002`, `AUTH-003`, `AUTH-004`, `AUTH-005`, `COM-001`, `COM-002`, `COM-009`, `AVL-003`, `AVL-005`, `SEC-003`, `SEC-005`, `SEC-007`, `OPS-003`, `OPS-006`. |
+
 | OIDC validated-address transport repair | `UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q tests/identity/test_oidc_enrollment.py tests/operations/test_fail_closed_config.py tests/production/test_deployment_config.py` | 53 passed, 0 failed on 2026-07-15 | H only: includes the real `_PinnedHTTPSConnection` socket path under a validation-to-connect DNS-answer change, exact TCP address/SNI/Host assertions, proxy/tunnel and redirect denial, response bounds, unsafe address-class rejection, invalid resolver type handling, private IPv4/IPv6 pins, configuration, and deployment wiring. No real IdP/TLS service or independent approval boundary is claimed. |
 | Independent WebAuthn-UV approval component | `UV_CACHE_DIR=/tmp/uv-cache uv run pytest -q tests/approval`; approval-consumer lane; non-gate full regression below | 12 focused passed; 144 approval/consumer passed; included in 1049-pass broad lane on 2026-07-15 | H only: strict owner-only config/key custody, exact SQLite catalog/tamper rejection, UV-required maintained-library call contract, exact display/digest, bounded duplicate-rejecting HTTP, one-receipt response-loss retry, committed denial/expiry audits, rejection, credential revocation, loopback serving, and non-authorizing provisioning. WebAuthn verification is seam-controlled in hermetic tests; no real authenticator, independent host/device/operator, TLS proxy, rotation/recovery drill, or owner decision is claimed. |
 | Prior `0.1.8` candidate, unfiltered local run | `UV_CACHE_DIR=/tmp/uv-cache uv run --extra test pytest -q` | `1087 passed, 2 failed, 7 expected PostgreSQL skips` on 2026-07-16 | Both failures were preserved environmental G01 gates. This was not a passing unfiltered release run and is not current `0.1.9` evidence. |