[DM-085] Reconcile the merged V0 RC boundaries

.github/workflows/tests.yml

@@ -108,7 +108,7 @@ jobs:
       - uses: actions/checkout@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09 # v5
         with:
           repository: nicoechaniz/hermes-agent
-          ref: 0db1912911fafa384aa5ee0145929658a9d1dd33
+          ref: 5c8870c1625761956a56fd2b225720dbe9083e45
           path: .hermes-contract
       - name: Verify real Hermes plugin discovery and turn composition
         env:

CURRENT-STATE.md

@@ -1,23 +1,33 @@
 # Current state
 
-## Release-candidate checkpoint — 2026-08-16
+## Release-candidate checkpoint — 2026-08-18
 
-The integrated Matrix V0 baseline is merged at commit
-`75b34804f8d013d348129946c0cd541a4448e71d`, tree
-`38f3edb002ac52aac2d51fbf533cb58c38b813c5`. The package is being prepared as
+The qualified Matrix V0 functional boundary is merged at commit
+`09414d6edd9586f539be8272c4979d0b36c86b87`, tree
+`d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad` (PR #121). The package version is
 `0.1.0rc1`. No current deployment or live-host state is asserted.
 
-The merged code passed 600 tests with 37 intentional skips and 1,414
-parameterized subtests, plus the Python 3.11–3.14 CI matrix. The closed
-conformance registry currently contains 102 scenarios. Exact evidence and the
-pre-version-bump artifact hashes are recorded in
-[`docs/verification/v0-rc-qualification.md`](docs/verification/v0-rc-qualification.md).
-Because package metadata is part of each distribution, the RC artifacts must
-be rebuilt and receive new hashes. The V7/V3-only successor has now been
-qualified locally with 619 unittest cases (22 intentional skips) and two
-byte-identical offline builds; exact hashes are recorded in
+The exact boundary ran 640 tests, including 22 declared skips, with zero
+failures, plus the Python 3.11–3.14 CI matrix. The closed conformance registry
+contains 102 scenarios.
+Two offline builds were byte-identical: wheel SHA-256
+`5896ae31813b7b9e1224ada14b7f9da9745790404c5a1eee9043079572f20089`
+and sdist SHA-256
+`f0ba76eb6650647a8b808f8648d04ef6d35806fcafd2f271d140c4fa5f9e96a1`.
+Exact evidence is recorded in
 [`docs/verification/v0-rc-qualification.md`](docs/verification/v0-rc-qualification.md).
 
+The prepared Matrix closeout successor also repairs the Hermes CI source pin.
+The former merge commit is no longer advertised by the Hermes remote; public
+PR head `5c8870c1625761956a56fd2b225720dbe9083e45` has the identical audited tree
+`ac7dec02ca029e895963402788bd1cdc3afb36f8` and identical contract bytes. Its
+unprefixed git-archive SHA-256 is
+`09789981423142fec1a26239d5209f96c41453078ff73e2fc4a11e1d45728660`.
+Two isolated builds after this repin were byte-identical: wheel SHA-256
+`11ef77b2b4c743cfa25d6652e9cad3594e41223cb73f558d5ead8f47bd43609d`
+and sdist SHA-256
+`b23d66004039dc9d454c1bf4382b87a381c538fe8194a3c262440425ffa6de69`.
+
 ## Implemented Matrix boundary
 
 The package provides:
@@ -54,6 +64,13 @@ native encrypted peer and semantic-receipt path, but Tribe removal still needs
 explicit migration evidence and repository-owner authorization. No legacy
 dual-write or ambiguous compatibility path is part of the RC plan.
 
+Its final software successor is merged at
+`294e1194db6cd60d9349a2d43938475bbd1c8c20`, tree
+`bcba9989a38519df87ecbb6c87a33a2f9740b85d` (PR #65), after exact-head
+independent approval and 148 tests with zero failures on Python 3.10–3.13.
+This is software evidence, not evidence of live provisioning, key rotation,
+service changes or cutover.
+
 The external Matrix.org protocol is unrelated and is not a dependency.
 
 ## Evidence classification
@@ -66,13 +83,11 @@ supersedes their operational-state claims.
 
 ## Remaining release work
 
-- freeze the V7-only runtime-bundle and V3-only client surface now that the
-  never-deployed compatibility paths are removed;
-- finish exact cross-repository pins and manifests;
-- rebuild `0.1.0rc1` twice and record byte-identical artifact hashes;
-- perform clean artifact installation and the complete supported-Python suite;
-- pass disposable end-to-end backup/export, restore, recovery/rebirth,
-  disaster rebuild, rollback and concurrent-launch tests;
-- obtain independent review of each final content-addressed candidate;
+- merge the prepared Matrix boundary successor and repin Cluster to that exact
+  Matrix commit;
+- reconcile final Cluster/Tribe metadata without treating documentation-only
+  commits as new functional authority;
+- regenerate the final three-repository manifest and repeat artifact-only
+  installation against the resulting exact default-branch heads;
 - leave publication and every physical or participant-facing action behind its
   explicit human gate.

RESUME.md

@@ -4,22 +4,40 @@ Status: the integrated V0 Matrix baseline is merged and release-candidate
 qualification is active. No current deployment, host state, service state or
 operator access is assumed by this checkpoint.
 
-Last reconciled: 2026-08-16.
+Last reconciled: 2026-08-18.
 
-## Exact Matrix baseline
+## Exact qualified boundaries
 
-- Commit: `75b34804f8d013d348129946c0cd541a4448e71d`
-- Tree: `38f3edb002ac52aac2d51fbf533cb58c38b813c5`
-- Merge: PR #119, which includes the distributed-custody and least-authority
-  host-capability work through `c773029`.
-- Qualification: 600 passed, 37 skipped, 1,414 parameterized subtests; CI was
-  green on Python 3.11 through 3.14. See
+- Matrix functional merge: `09414d6edd9586f539be8272c4979d0b36c86b87`,
+  tree `d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad`, PR #121.
+- Cluster functional merge: `820e3792a227b1848681a3421b113e8822c8d08a`,
+  tree `4f62eb4f6eff1dfafbd477339a86fa7d5e70a5d8`, PR #93. It pins the
+  exact Matrix functional merge.
+- Tribe protected merge: `294e1194db6cd60d9349a2d43938475bbd1c8c20`,
+  tree `bcba9989a38519df87ecbb6c87a33a2f9740b85d`, PR #65. Its reviewed
+  head ran 148 tests with zero failures on Python 3.10 through 3.13; its
+  post-merge `main` workflow is green.
+- Matrix qualification: 640 tests run, including 22 declared skips, with zero
+  failures; CI is green on Python 3.11 through 3.14. See
   [`docs/verification/v0-rc-qualification.md`](docs/verification/v0-rc-qualification.md).
 
-The package version is now `0.1.0rc1`. Artifact hashes recorded for the merged
-pre-version-bump tree are historical qualification evidence, not hashes for
-this RC metadata successor. Rebuild and record the final hashes before freezing
-or publishing the candidate.
+The package version is `0.1.0rc1`. Two clean offline builds of the exact Matrix
+functional merge were byte-identical: wheel SHA-256
+`5896ae31813b7b9e1224ada14b7f9da9745790404c5a1eee9043079572f20089`
+and sdist SHA-256
+`f0ba76eb6650647a8b808f8648d04ef6d35806fcafd2f271d140c4fa5f9e96a1`.
+The final integrated manifest must be regenerated after every documentation or
+pin successor because the repository heads and source archives change.
+
+The Matrix closeout successor replaces the now-unreachable Hermes merge pin
+with public PR head `5c8870c1625761956a56fd2b225720dbe9083e45`. It has the same
+audited tree `ac7dec02ca029e895963402788bd1cdc3afb36f8` and contract bytes;
+its unprefixed git-archive SHA-256 is
+`09789981423142fec1a26239d5209f96c41453078ff73e2fc4a11e1d45728660`.
+The repinned package built twice byte-identically as wheel
+`11ef77b2b4c743cfa25d6652e9cad3594e41223cb73f558d5ead8f47bd43609d`
+and sdist
+`b23d66004039dc9d454c1bf4382b87a381c538fe8194a3c262440425ffa6de69`.
 
 ## Current architecture
 
@@ -36,14 +54,16 @@ or publishing the candidate.
 
 ## Resume order
 
-1. Regenerate and independently qualify reproducible `0.1.0rc1` artifacts; the
-   operational surface is now runtime-bundle V7 and client-config V3 only.
-2. Pin the exact Matrix, Cluster and Tribe candidate commits and dependency
-   hashes in their release manifests.
-3. Run clean-install and disposable end-to-end backup, restore,
-   recovery/rebirth, rollback and double-launch rejection suites.
-4. Reconcile cross-repository documentation and tracking to those exact heads.
-5. Prepare a content-addressed physical preflight, but do not execute it.
+1. Merge this Matrix boundary successor and repin Cluster's exact Matrix
+   dependency to the resulting commit without changing the reviewed identity,
+   custody or runtime behavior.
+2. Reconcile Cluster and Tribe metadata to those protected merges, keeping
+   executable dependency pins distinct from documentation-only repository heads.
+3. Regenerate the content-addressed integrated manifest and repeat clean
+   artifact installation from those exact heads. The latest pre-merge freezer
+   proof is superseded and remains historical evidence only.
+4. Close automated tracking only after the three default branches and final
+   manifest agree. Keep the physical preflight prepared but unexecuted.
 
 ## Human and external gates
 

ROADMAP.md

@@ -6,17 +6,20 @@ The V0 Matrix baseline is merged. The nearest milestone is a reproducible,
 cross-repository `0.1.0rc1` candidate proved entirely with clean local/CI and
 disposable end-to-end evidence. No infrastructure is presumed active.
 
-1. Freeze exact cross-repository dependency pins on the V7-only runtime and
-   V3-only client surface.
-2. Rebuild artifacts twice, verify their closed contents, install them into
-   empty environments and run Python 3.11–3.14 qualification.
-3. Complete disposable backup/export, restore, recovery/rebirth, rollback,
-   crash/restart, revocation and concurrent-launch rejection journeys.
-4. Consolidate provenance, limitations, operator instructions and exact
-   hashes, then obtain independent review of the final heads.
-5. Prepare—but do not execute—a content-addressed physical trial plan.
-6. Publish/cut over only after the corresponding human authorization.
-7. Retire Tribe only after native replacement evidence and its separate owner
+Completed software milestones: V7/V3-only Matrix, separated recovery holders,
+shared Cluster admission/fencing, fresh-embodiment recovery, disposable
+backup/restore/rebirth/rollback journeys, reproducible Matrix artifacts and a
+non-executing content-addressed physical preflight.
+
+1. Merge the prepared Matrix boundary successor, including the reachable
+   byte-equivalent Hermes contract pin, through normal review and pin Cluster
+   to that exact Matrix dependency.
+2. Reconcile Cluster/Tribe metadata and distinguish reviewed functional
+   boundaries from documentation-only repository heads.
+3. Regenerate and independently verify the integrated content-addressed
+   manifest plus clean artifact installations.
+4. Publish/cut over only after the corresponding human authorization.
+5. Retire Tribe only after native replacement evidence and its separate owner
    gate.
 
 ## Release invariants

docs/dm041-hermes-body.md

@@ -28,9 +28,9 @@ CompAII profile, account, credential, deployment or memory migration.
 ## Exact compatibility boundary
 
 The only supported Hermes payload is public commit
-`0db1912911fafa384aa5ee0145929658a9d1dd33`, version `0.19.0`, tree
+`5c8870c1625761956a56fd2b225720dbe9083e45`, version `0.19.0`, tree
 `ac7dec02ca029e895963402788bd1cdc3afb36f8`. The audited git-archive SHA-256 is
-`860a664f622e1099a095cb6cf06b04bcfe78b2fd3affc7192da9cf7ccefcdd63`.
+`09789981423142fec1a26239d5209f96c41453078ff73e2fc4a11e1d45728660`.
 The exact source-file digests are in
 `provenance/hermes-agent-0.19.0.json` and cover configuration, CLI parsing,
 plugin discovery/LLM access, memory provider/manager, prompt composition,

docs/verification/v0-rc-qualification.md

@@ -1,27 +1,24 @@
 # V0 release-candidate qualification receipt
 
-Status: accepted baseline evidence plus local V7/V3-only candidate
-qualification. Publication and cross-repository qualification remain separate.
+Status: accepted V7/V3-only functional qualification. Matrix, Cluster and
+Tribe functional successors are merged; the final integrated manifest remains
+pending documentation-only exact-head repins and artifact requalification.
 
 ## Subject
 
 - Repository: `AlterMundi/daimon-matrix`
-- Commit: `75b34804f8d013d348129946c0cd541a4448e71d`
-- Tree: `38f3edb002ac52aac2d51fbf533cb58c38b813c5`
-- Integrated merge: PR #119
+- Commit: `09414d6edd9586f539be8272c4979d0b36c86b87`
+- Tree: `d7146e291ae3f8313dc0b3d3c3a0b5e5f94d33ad`
+- Integrated merge: PR #121
 
 ## Recorded qualification
 
-- Test result: 600 passed, 37 skipped.
-- Parameterized evidence: 1,414 subtests.
+- Test result: 640 tests run, including 22 declared skips, zero failures.
 - Supported CI interpreters: Python 3.11, 3.12, 3.13 and 3.14.
-- Pre-version-bump wheel SHA-256:
-  `df96015fe2bea750c97dc994cdfaccb96ef1d775cd4de315454b6edf540d1548`.
-- Pre-version-bump sdist SHA-256:
-  `ba89a1d77ac8f664fdac3be177d7778d004fb0045d65a44b62289176f4b9c879`.
-
-Those two digests identify the historical pre-version-bump distributions and
-must not be published as RC artifacts.
+- Wheel SHA-256:
+  `5896ae31813b7b9e1224ada14b7f9da9745790404c5a1eee9043079572f20089`.
+- Sdist SHA-256:
+  `f0ba76eb6650647a8b808f8648d04ef6d35806fcafd2f271d140c4fa5f9e96a1`.
 
 ## V7/V3-only candidate qualification
 
@@ -30,20 +27,52 @@ must not be published as RC artifacts.
   or custody opens.
 - Operational client config: V3 only; V1/V2 and retired-server response
   fallback reject closed.
-- Source-isolated unittest result: 619 tests run, 22 intentionally skipped and
-  zero test failures. Python 3.13 still emitted known temporary-directory
-  cleanup diagnostics at interpreter shutdown; they did not alter the result
-  and are not represented here as warning-free evidence.
+- Source-isolated unittest result: 640 tests run, 22 declared skips and zero
+  failures.
 - Ruff formatting/lint and strict mypy: pass for the release workflow surface.
 - Current vector generators, offline lock validation and byte comparison: pass.
-- Wheel SHA-256: `5ed4b034c0f5d7e74f2755562d5fa9d13776d5b4b9a44de2ac3f1ce05511f7ad`.
-- Sdist SHA-256: `5e232f47d4477afb2018d97395fc1a9a8b01442f6fcb4441a7b0129dfa7a821b`.
+- Wheel SHA-256: `5896ae31813b7b9e1224ada14b7f9da9745790404c5a1eee9043079572f20089`.
+- Sdist SHA-256: `f0ba76eb6650647a8b808f8648d04ef6d35806fcafd2f271d140c4fa5f9e96a1`.
 
-The two artifacts were built twice offline with `SOURCE_DATE_EPOCH=946684800`;
+The artifacts were built twice offline with `SOURCE_DATE_EPOCH=946684800`;
 each pair was byte-identical, passed the closed distribution allowlist and
-passed the packaged-secret scan. Their exact source commit/tree is recorded in
-the candidate handoff rather than embedded here, avoiding a self-referential
-commit identifier.
+passed the packaged-secret scan. Any later documentation/pin successor changes
+the repository source archive and must produce a new integrated manifest.
+
+## Prepared Hermes reachability successor
+
+The Hermes 0.19.0 compatibility bytes remain tree
+`ac7dec02ca029e895963402788bd1cdc3afb36f8`, but the former merge commit is no
+longer advertised by the source remote. The closeout successor therefore pins
+reachable public PR head `5c8870c1625761956a56fd2b225720dbe9083e45`, whose
+tree and every audited contract digest are identical. The replacement
+unprefixed git archive is SHA-256
+`09789981423142fec1a26239d5209f96c41453078ff73e2fc4a11e1d45728660`.
+
+The repinned source produced two byte-identical isolated builds with
+`SOURCE_DATE_EPOCH=946684800`:
+
+- Wheel SHA-256: `11ef77b2b4c743cfa25d6652e9cad3594e41223cb73f558d5ead8f47bd43609d`.
+- Sdist SHA-256: `b23d66004039dc9d454c1bf4382b87a381c538fe8194a3c262440425ffa6de69`.
+
+These hashes supersede the functional-merge package hashes for the prepared
+Matrix successor. The final integrated manifest must still bind the actual
+merged default-branch commit and exact copied artifacts.
+
+## Cross-repository checkpoint
+
+- Cluster merge: `820e3792a227b1848681a3421b113e8822c8d08a`, tree
+  `4f62eb4f6eff1dfafbd477339a86fa7d5e70a5d8`.
+- Tribe protected merge: `294e1194db6cd60d9349a2d43938475bbd1c8c20`,
+  tree `bcba9989a38519df87ecbb6c87a33a2f9740b85d`; exact reviewed head
+  `e81c5da0b96d0ac29f7a3bdeacb1f0e7c860ec3c` has the same tree and ran
+  148 tests with zero failures on Python 3.10 through 3.13.
+- Provisional three-repository freezer proof: SHA-256
+  `d3ac479d4ff581e0f1dfb82a1a41f15d25ad3e45eb03723065e865d037cc8fd5`.
+  Its exact subject was Matrix `09414d6`, Cluster `820e379` and Tribe
+  `42d637245864fcd431198a570d19d7a6dd042924` (tree `5145f6446f3ec3013347509477a262f98825ebfa`).
+  It is superseded historical method evidence because it predates the Tribe
+  merge and the final documentation/pin successors.
 
 ## Scope