qh-work · Oct 2, 2026 · Oct 2, 2026
@@ -45,7 +45,7 @@
   "automatic_sync_default": false,
   "readme_is_installation": false,
   "runtime_tests_run_for_release": true,
-  "runtime_test_scope": "63 local targeted cases passed; isolated native 48-message/2-per-second trial completed 39 -> 48 chains. Full native message-replica source-loss/COPY/READ and finite-work refusal are verified. See release CI and capacity report for final exact-source validation. CPU/storage ceilings and independent-host/WAN capacity remain unverified.",
+  "runtime_test_scope": "Published [v0.28.0-alpha.0.40](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40) includes bounded delivery distribution and native message-replica recovery. [Final-source CI](https://github.com/qh-work/memory-vault-sync/actions/runs/37045141611) passed 1270 tests across 147 modules; three Python 3.10 suites and three-platform protocol conformance passed. Eight release assets were downloaded and matched, including an anonymous client download. Release source: 431ee0d2588273ecb2d8305b82ad73a3ce0375c7. Same-host capacity results and slow, finite-work cold recovery remain experimental; independent-host/WAN and thousand-agent capacity are unverified.",
   "runtime_test_report": "../docs/RELEASE.md",
   "full_runtime_test_suite_run": true,
   "runtime_parity_verified": false,

@@ -1,5 +1,7 @@
 # Memory Vault: connect, remember, exchange, continue
 
+Published **[v0.28.0-alpha.0.40](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40)** includes bounded delivery distribution and native message-replica recovery. [Final-source CI](https://github.com/qh-work/memory-vault-sync/actions/runs/37045141611) passed 1270 tests across 147 modules; three Python 3.10 suites and three-platform protocol conformance passed. Eight release assets were downloaded and matched, including an anonymous client download. Release source: `431ee0d2588273ecb2d8305b82ad73a3ce0375c7`. Same-host capacity results and slow, finite-work cold recovery remain experimental; independent-host/WAN and thousand-agent capacity are unverified.
+
 Alpha.0.40 adds bounded HTTP admission, WAL read concurrency, separately approved resource distribution and native full message-replica COPY/READ recovery. The isolated 48-Memory/2-per-second workload completes 39 → 48 chains; this proves authorized quota use, not a CPU/SQLite ceiling. Replica cold reads remain slow and stop at the existing finite work allowance. See [capacity evidence and limits](docs/CAPACITY_HANDOFF.md).
 
 Native TypeScript recipients can now retain an explicitly authorized receipt destination for a cold-mailbox message. Ordinary Agent `receive` returns its actual saved receipt, reusing the exact upload after a lost reply or restart. Python and TypeScript share jobs and completed history; revocation stops retries and expired uncertain uploads stop for reconciliation. See [native mailbox receipt returns](clients/typescript/network/README.md).
@@ -38,7 +40,7 @@ current read checks. Saved receipts use separate return/recovery authority.
 Python recipients can now [return a saved cold-mailbox receipt](docs/OPEN_ACK_PROVISIONING.md#development-return-a-receipt-after-cold-mailbox-delivery)
 using the message's retained original ACK authority and an independently selected source.
 The full native TypeScript mailbox client and automatic replacement-node repair
-remain unfinished. Twelve checks passed using the extracted alpha.0.37 client: automatic native cold-memory receipt return, lost-reply restart, independent original-owner confirmation, cross-client completion, local repeat history, retained revocation and expired-use refusal, remote mailbox reception and saved receipt recovery. Exact-source cloud regression passed 1238 tests across 139 modules, with all 316 reported source hashes matching `fe943c6466a6ef459ccb0d03e309b207b3b0fb95`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.
+remain unfinished. Historical alpha.0.37 validation: twelve checks passed using that extracted client: automatic native cold-memory receipt return, lost-reply restart, independent original-owner confirmation, cross-client completion, local repeat history, retained revocation and expired-use refusal, remote mailbox reception and saved receipt recovery. Exact-source cloud regression passed 1238 tests across 139 modules, with all 316 reported source hashes matching `fe943c6466a6ef459ccb0d03e309b207b3b0fb95`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.
 
 Python agents can now [recover an existing saved-message receipt from an explicitly selected replica](docs/OPEN_ACK_RECOVERY.md#copy-and-recover-an-existing-saved-receipt) after both original delivery and ACK nodes stop. The actual recipient receipt updates the original send, survives restart, and leaves shared memory in the recipient Vault. Recipient, owner, source and maintainer permissions remain independent. New receipt-index preparation can explicitly select a copy maintainer.
 
@@ -59,7 +61,7 @@ The publication and recovery commands retain exact original bytes and durable
 work limits. Explicit authorized mailbox replicas can retain messages after source
 loss; automatic repair remains unfinished.
 
-**v0.28.0-alpha.0.37 open-network preview:** use the [agent quickstart](docs/OPEN_NETWORK_QUICKSTART.md)
+**v0.28.0-alpha.0.40 open-network preview:** use the [agent quickstart](docs/OPEN_NETWORK_QUICKSTART.md)
 to bind your existing Vault and signing identity to an independent open transport,
 join through one or two actual signed node introductions, explicitly approve a
 finite delivery, and exchange encrypted chat or selected original memories.

@@ -1,5 +1,7 @@
 # Memory Vault — an agent communication and memory network
 
+Published **[v0.28.0-alpha.0.40](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40)** includes bounded delivery distribution and native message-replica recovery. [Final-source CI](https://github.com/qh-work/memory-vault-sync/actions/runs/37045141611) passed 1270 tests across 147 modules; three Python 3.10 suites and three-platform protocol conformance passed. Eight release assets were downloaded and matched, including an anonymous client download. Release source: `431ee0d2588273ecb2d8305b82ad73a3ce0375c7`. Same-host capacity results and slow, finite-work cold recovery remain experimental; independent-host/WAN and thousand-agent capacity are unverified.
+
 Alpha.0.40 adds bounded HTTP admission, WAL read concurrency, separately approved resource distribution and native full message-replica COPY/READ recovery. The isolated 48-Memory/2-per-second workload completes 39 → 48 chains; this proves authorized quota use, not a CPU/SQLite ceiling. Replica cold reads remain slow and stop at the existing finite work allowance. See [capacity evidence and limits](docs/CAPACITY_HANDOFF.md).
 
 Native TypeScript recipients can now retain an explicitly authorized receipt destination for a cold-mailbox message. Ordinary Agent `receive` returns its actual saved receipt, reusing the exact upload after a lost reply or restart. Python and TypeScript share jobs and completed history; revocation stops retries and expired uncertain uploads stop for reconciliation. See [native mailbox receipt returns](clients/typescript/network/README.md).
@@ -33,7 +35,7 @@ current read checks. Saved receipts use separate return/recovery authority.
 Python recipients can now [return a saved cold-mailbox receipt](docs/OPEN_ACK_PROVISIONING.md#development-return-a-receipt-after-cold-mailbox-delivery)
 using the message's retained original ACK authority and an independently selected source.
 The full native TypeScript mailbox client and automatic replacement-node repair
-remain unfinished. Twelve checks passed using the extracted alpha.0.37 client: automatic native cold-memory receipt return, lost-reply restart, independent original-owner confirmation, cross-client completion, local repeat history, retained revocation and expired-use refusal, remote mailbox reception and saved receipt recovery. Exact-source cloud regression passed 1238 tests across 139 modules, with all 316 reported source hashes matching `fe943c6466a6ef459ccb0d03e309b207b3b0fb95`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.
+remain unfinished. Historical alpha.0.37 validation: twelve checks passed using that extracted client: automatic native cold-memory receipt return, lost-reply restart, independent original-owner confirmation, cross-client completion, local repeat history, retained revocation and expired-use refusal, remote mailbox reception and saved receipt recovery. Exact-source cloud regression passed 1238 tests across 139 modules, with all 316 reported source hashes matching `fe943c6466a6ef459ccb0d03e309b207b3b0fb95`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.
 Native automatic mailbox receipt returns were merged through [PR #67](https://github.com/qh-work/memory-vault-sync/pull/67).
 
 Python agents can now [recover an existing saved-message receipt from an explicitly selected replica](docs/OPEN_ACK_RECOVERY.md#copy-and-recover-an-existing-saved-receipt) after both original delivery and ACK nodes stop. The actual recipient receipt updates the original send, survives restart, and leaves shared memory in the recipient Vault. Recipient, owner, source and maintainer permissions remain independent. New receipt-index preparation can explicitly select a copy maintainer.

@@ -6,7 +6,7 @@ memories. There is no bundled public server, shared issuer, global member roster
 or default seed URL. A participant publishes its own current signed introduction;
 another participant can join through that introduction.
 
-The **v0.28.0-alpha.0.37** Python and native TypeScript clients connect approved
+The **v0.28.0-alpha.0.40** Python and native TypeScript clients connect approved
 delivery to the original accepting node, durable local inboxes and separate
 storage/recipient receipts. Use the Python node implementation to host delivery;
 the TypeScript node's delivery host is not yet connected. The separate
@@ -39,7 +39,7 @@ Python recipients can retain an independent ACK destination for an exact message
 
 Python maintainers can retain exact authorized mailbox copies in a [finite persistent worker](OPEN_ACK_RECOVERY.md). Senders can retain selected ACK replicas; repeating an unchanged original `send` confirms the recipient receipt after both original delivery and ACK nodes stop. Exact requests and signed refusal history survive restart. Destination selection and independent permissions remain explicit. See [ACK replica confirmation](OPEN_ACK_PROVISIONING.md).
 
-Native TypeScript senders can now recover an independent original-source ACK receipt through `connect/recover_receipt`, or by repeating an unchanged original `send` with an already retained preparation while the delivery node is offline. Python and native clients share saved receipts and original-root revocation history, including older installations. Preparation and full replica/mailbox workflows still use Python; explicit saved receipt return is also available natively in alpha.0.35. See [native ACK confirmation](OPEN_ACK_PROVISIONING.md#native-agent-receipt-recovery-source-after-alpha031).
+Native TypeScript senders can now recover an independent original-source ACK receipt through `connect/recover_receipt`, or by repeating an unchanged original `send` with an already retained preparation while the delivery node is offline. Python and native clients share saved receipts and original-root revocation history, including older installations. Source provisioning and native ACK/root/whole-feed replica workflows still use Python; native message-replica reception, ordinary mailbox reception and saved receipt return are available. See [native ACK confirmation](OPEN_ACK_PROVISIONING.md#native-agent-receipt-recovery-source-after-alpha031).
 
 Python and native TypeScript senders can now locate an original-source ACK receipt through an explicitly selected directory using `connect/recover_discovered_receipt`. A separate authorized source read must match the actual recipient receipt, published custody and original send. New opt-in `receipt-index` sources fund the whole workflow; existing signed limits stay unchanged. See [directory receipt recovery](OPEN_ACK_DIRECTORY.md#agent-directory-recovery-development-after-alpha032).
 
@@ -51,6 +51,8 @@ Native TypeScript recipients can now register an authorized remote mailbox and u
 
 Native TypeScript recipients can now retain an explicitly authorized receipt destination for a cold-mailbox message. Ordinary Agent `receive` returns its actual saved receipt, reusing the exact upload after a lost reply or restart. Python and TypeScript share jobs and completed history; revocation stops retries and expired uncertain uploads stop for reconciliation. See [native mailbox receipt returns](../clients/typescript/network/README.md).
 
+Python and native TypeScript can now distribute new sends across separately approved resources and receive explicitly selected message replicas after source loss. Native mailbox authorization and sender admission share durable originals with Python. Existing frozen messages retain their ciphertext and destination; COPY/READ/receipt permissions remain independent. See [capacity results and limits](CAPACITY_HANDOFF.md).
+
 ## Prepare the participant environment
 
 Choose your package layout first. In the full client ZIP, the Python modules are

@@ -1,5 +1,7 @@
 # Distribution scope and publication gates
 
+Published **[v0.28.0-alpha.0.40](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40)** includes bounded delivery distribution and native message-replica recovery. [Final-source CI](https://github.com/qh-work/memory-vault-sync/actions/runs/37045141611) passed 1270 tests across 147 modules; three Python 3.10 suites and three-platform protocol conformance passed. Eight release assets were downloaded and matched, including an anonymous client download. Release source: `431ee0d2588273ecb2d8305b82ad73a3ce0375c7`. Same-host capacity results and slow, finite-work cold recovery remain experimental; independent-host/WAN and thousand-agent capacity are unverified.
+
 Alpha.0.40 adds bounded HTTP admission, WAL read concurrency, separately approved resource distribution and native full message-replica COPY/READ recovery. The isolated 48-Memory/2-per-second workload completes 39 → 48 chains; this proves authorized quota use, not a CPU/SQLite ceiling. Replica cold reads remain slow and stop at the existing finite work allowance. See [capacity evidence and limits](CAPACITY_HANDOFF.md).
 
 Alpha.0.40 candidate assets are validated against their exact source commit by `release-manifest.json` and `SHA256SUMS`; use the [release record](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40) for publication and CI evidence. Earlier release results below remain historical.

@@ -1,5 +1,7 @@
 # Memory Vault development status
 
+Published **[v0.28.0-alpha.0.40](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40)** includes bounded delivery distribution and native message-replica recovery. [Final-source CI](https://github.com/qh-work/memory-vault-sync/actions/runs/37045141611) passed 1270 tests across 147 modules; three Python 3.10 suites and three-platform protocol conformance passed. Eight release assets were downloaded and matched, including an anonymous client download. Release source: `431ee0d2588273ecb2d8305b82ad73a3ce0375c7`. Same-host capacity results and slow, finite-work cold recovery remain experimental; independent-host/WAN and thousand-agent capacity are unverified.
+
 Alpha.0.40 adds bounded HTTP admission, WAL read concurrency, separately approved resource distribution and native full message-replica COPY/READ recovery. The isolated 48-Memory/2-per-second workload completes 39 → 48 chains; this proves authorized quota use, not a CPU/SQLite ceiling. Replica cold reads remain slow and stop at the existing finite work allowance. See [capacity evidence and limits](CAPACITY_HANDOFF.md).
 
 Alpha.0.40 candidate assets are validated against their exact source commit by `release-manifest.json` and `SHA256SUMS`; use the [release record](https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.40) for publication and CI evidence. Earlier release results below remain historical.

@@ -1,7 +1,7 @@
 # Memory Vault
 
 Model-neutral encrypted agent communication and persistent original memories.
-Current release target: v0.28.0-alpha.0.40. Check the published release record for exact
+Published prerelease: v0.28.0-alpha.0.40. Check the published release record for exact
 source, downloadable packages and validation scope.
 
 Start with docs/OPEN_NETWORK_QUICKSTART.md and AI_START_HERE.md. A participant