Add deterministic transactional lifecycle command scheduler
This commit is contained in:
@@ -130,3 +130,20 @@ results/ecs-gcc142.jsonl; all 56 fingerprints match corresponding Windows sample
|
||||
No production rule or snapshot-format change occurred. This supersedes the
|
||||
pending Linux experiment note above. The final follow-up edits only record
|
||||
results and decision scope; production ECS adoption remains deferred.
|
||||
|
||||
## M1.6 sequential scheduler (2026-09-19)
|
||||
|
||||
Native commands: `tools/windows-check.ps1 -Preset release -Action configure`,
|
||||
clang-format on changed C++ files, `cmake --build --preset release`,
|
||||
`ctest --preset release`; then `tools/windows-check.ps1 -Preset analysis -Action check`,
|
||||
`tools/windows-check.ps1 -Preset asan -Action check` and Release `-Action format`.
|
||||
All three configurations passed 5/5 CTests; clang-tidy and format-check passed.
|
||||
Tests execute under NDEBUG and cover six batch permutations across 32 seeds,
|
||||
an independent direct-lifecycle reference, ordered receipts, restore continuation,
|
||||
rejected conflicts and malformed admission, the 1,024-command boundary, full entity
|
||||
capacity and tick/ID exhaustion. Golden `d61ad5bf0c928c76` remains unchanged.
|
||||
|
||||
The copy-and-commit implementation allocates before publishing world state and
|
||||
statically checks noexcept publication/receipt moves. Allocation-failure injection
|
||||
was not run. No scheduler throughput claim, concurrency validation, durable input
|
||||
journal or Kubernetes execution is implied. Linux CI is pending this source push.
|
||||
|
||||
Reference in New Issue
Block a user