Complete M6.4 atomic environmental transfers

This commit is contained in:
dingo
2026-09-27 09:15:21 -04:00
parent 965a33ca48
commit 70cd288327
17 changed files with 744 additions and 4 deletions
+20
View File
@@ -1772,3 +1772,23 @@ ChunkStore does not yet bind a world identity, so coherent field/terrain pairing
cannot be independently authenticated by this view. Combined ownership, reservation,
atomic inventory transfer and retry outcomes remain M6.4. No deployment or World0
operation occurred.
## M6.4 atomic environmental transfers - 2026-09-27
Executed on Windows x64 with the installed Visual Studio toolchain:
- `tools/windows-check.ps1 -Preset release -Action check`: build and 52/52 CTests passed (NDEBUG).
- `tools/windows-check.ps1 -Preset analysis -Action check`: clang-tidy/warnings-as-errors build and 52/52 CTests passed.
- `tools/windows-check.ps1 -Preset asan -Action check`: AddressSanitizer build and 52/52 CTests passed.
- `tools/windows-check.ps1 -Preset release -Action format`: passed.
New environment-transfers-contracts exercises last-stock contention, fresh versus
stale/foreign views, exact retries, changed-payload refusal, expired command IDs,
command exhaustion, late-leg rollback, account and water capacities, admission
overflow, separate owner/field allocation budgets, and 100 batches checked against
independent expected balances across all ten compartments. No golden changed.
This evidence covers local in-memory atomicity. Coupled snapshots, allocation-failure
injection, process crash recovery and biological lifecycle integration are not claimed.
Linux/UBSan/TSan were not run locally; their existing Gitea jobs remain required CI
evidence. No cluster workload or World0 state was changed.