docs(release): bind 0.1.35 CI evidence

Author: misunders2d

PUBLIC_RELEASE_STATUS.md

@@ -113,10 +113,13 @@ regression passes (`103 passed`); the full source lane, direct verifier, and
 both independently installed npm-tarball generations each pass with `1621
 passed, 16 expected skips`; the frozen wheel and sdist are byte-identical across
 two builds. The final local npm tarball has shasum
-`3b7dcc0d853b95089ec24c28d31b8c2bb1d1937e` and integrity
-`sha512-m65KdZWhGA1izkYhJAJAC0+6CPGjubzWaMYNEzkJG/XjC3cHHYeJlbuBzD/H87ItSni3cA6aUFNG7aaJz+jtpg==`;
-those are local package facts, not registry publication evidence. Fresh
-same-commit CI, publication, Hub recovery, the live owner
+`c70bdfdb5b8184c55f46c18c9cda16754d130a4f` and integrity
+`sha512-Eo+o7cP0PtsQfGVALJ0nqDB2XP7qWsUcrc3eLtsMmKEZF8aQKR8ZVagr1TSjZL0GPrFoBlHB6L3Ea0H2+R83jQ==`;
+those are local package facts, not registry publication evidence. On commit
+`c463de92c82e3ff2915df7b6af2dcf32a07988cb`, cross-platform/package run
+`30693899336`, clean ordinary-server setup run `30693899319`, and real
+0.1.31-to-0.1.33-failed-to-0.1.35 upgrade recovery run `30693899330` all
+passed. Publication, Hub recovery, the live owner
 ceremony, fresh enrollment, and the first native message remain pending.
 
 ## Release and gate posture

evidence/local/2026-08-01-v0.1.35/manifest.json

@@ -1,14 +1,14 @@
 {
   "run_id": "2026-08-01-v0.1.35",
-  "evaluated_at": "2026-08-01T12:26:13+03:00",
+  "evaluated_at": "2026-08-01T12:37:21+03:00",
   "scope": "v0_1_35_atomic_upgrade_journal_and_identity_preserving_reconciliation_candidate",
   "verification_status": "PASS",
   "release_certified": false,
   "source_revision_kind": "release_source_tree_sha256",
   "release_source_tree_sha256": "ff3b37a9f27bb62a3c89d80a873af5caa933d3d7e3ebcaa7d171a1f2b7760d8b",
   "prior_runtime_evidence": "evidence/local/2026-08-01-v0.1.33/manifest.json",
   "supersedes_package_evidence": "evidence/local/2026-08-01-v0.1.33/manifest.json",
-  "change_boundary": "Exact public 0.1.34 failed before marker or PostgreSQL advance while succeeding in unlinking the retained committed 0.1.31-to-0.1.33 journal, then failed before writing the separately approved next-edge journal. Version 0.1.35 closes that package-owned crash window: after exact marker/config/unit provenance revalidation, the old journal remains byte-exactly durable until the new 0.1.33-to-0.1.35 journal atomically replaces it. An in-place regression reproduces the prior marker-0.1.33-plus-missing-journal result under injected next-edge write failure and proves the corrected old journal remains byte-exact. The existing identity-preserving failed-unit reconciliation and root-only pre-C0 expired-credential reauthorization remain unchanged: Approval has the same successful SIGTERM contract as Core, exact managed failed latches are cleared only after bounded stop/disable, strict inactive/PID checks remain, and same-key possession plus fresh owner WebAuthn Approval retires the old expired row and creates one finite next epoch without authority grant or restart. No guard is relaxed, no reset or manual marker/database edit is introduced. Every failed 0.1.33/0.1.34 Hub attempt remains BOUNDED NON-GREEN and unwaived. Same-commit CI, exact public 0.1.35 publication, Hub recovery, live owner approval, five-unit readiness, fresh-laptop enrollment, native message/ACK, completion, and revocation evidence remain pending until separately recorded.",
+  "change_boundary": "Exact public 0.1.34 failed before marker or PostgreSQL advance while succeeding in unlinking the retained committed 0.1.31-to-0.1.33 journal, then failed before writing the separately approved next-edge journal. Version 0.1.35 closes that package-owned crash window: after exact marker/config/unit provenance revalidation, the old journal remains byte-exactly durable until the new 0.1.33-to-0.1.35 journal atomically replaces it. An in-place regression reproduces the prior marker-0.1.33-plus-missing-journal result under injected next-edge write failure and proves the corrected old journal remains byte-exact. The existing identity-preserving failed-unit reconciliation and root-only pre-C0 expired-credential reauthorization remain unchanged: Approval has the same successful SIGTERM contract as Core, exact managed failed latches are cleared only after bounded stop/disable, strict inactive/PID checks remain, and same-key possession plus fresh owner WebAuthn Approval retires the old expired row and creates one finite next epoch without authority grant or restart. No guard is relaxed, no reset or manual marker/database edit is introduced. Every failed 0.1.33/0.1.34 Hub attempt remains BOUNDED NON-GREEN and unwaived. Same-commit cross-platform, clean ordinary-server setup, and real released-upgrade recovery CI passed at c463de92c82e3ff2915df7b6af2dcf32a07988cb. Exact public 0.1.35 publication, Hub recovery, live owner approval, five-unit readiness, fresh-laptop enrollment, native message/ACK, completion, and revocation evidence remain pending until separately recorded.",
   "execution_context": {
     "source": "ordinary local user in the AgentNet repository; no live service or external system mutation",
     "packed_generations": "PASS: source plus two clean recursive npm installation generations each report 1621 passed and 16 expected skips, complete package-tree digest equality, and no named verification residue",
@@ -25,7 +25,7 @@
     "public_v0_1_33_status": "Published on npm; exact Hub transition exposed the retained systemd failed-latch recovery defect after the forward-only marker boundary",
     "hub_v0_1_33_apply": "BOUNDED NON-GREEN: Approval ActiveState=failed versus required inactive; marker, five unit bytes, PostgreSQL, identity, config, and credentials were preserved; repeated unchanged 0.1.33 apply is not a recovery",
     "public_v0_1_34_status": "Published on npm; exact Hub apply exposed the non-atomic journal-succession crash window before marker or PostgreSQL advance and remains BOUNDED NON-GREEN",
-    "v0_1_35_candidate": "LOCAL FROZEN, EXTERNAL PENDING: atomic retained-journal succession, identity-preserving failed-unit reconciliation, and owner-approved pre-C0 expired-credential reauthorization are implemented; deterministic artifacts are frozen while same-commit CI, publication, and external runtime proof remain required",
+    "v0_1_35_candidate": "LOCAL FROZEN, SAME-COMMIT CI PASS, PUBLICATION PENDING: atomic retained-journal succession, identity-preserving failed-unit reconciliation, and owner-approved pre-C0 expired-credential reauthorization are implemented; deterministic artifacts are frozen and exact-commit cross-platform, clean-setup, and released-upgrade recovery workflows passed, while publication and external runtime proof remain required",
     "release_posture": "BLOCKED; production_ready=false; ship_eligible=false; no must-not-ship gate is promoted"
   },
   "commands": [
@@ -71,7 +71,7 @@
     },
     {
       "command": "GitHub cross-platform and ordinary-server setup workflows",
-      "result": "NOT RUN ON THE UNCOMMITTED CANDIDATE: the corrected 0.1.35 commit requires fresh same-commit cross-platform, ordinary-server setup, and real upgrade-path evidence before tagging; no prior run is reclassified or waived"
+      "result": "PASS ON c463de92c82e3ff2915df7b6af2dcf32a07988cb: cross-platform/package run 30693899336, clean ordinary-server setup run 30693899319, and real 0.1.31-to-0.1.33-failed-to-0.1.35 upgrade recovery run 30693899330 completed successfully; no prior non-green run is reclassified or waived"
     }
   ],
   "review_results": [