Implement M6.7 bounded environmental interval scheduling

This commit is contained in:
dingo
2026-09-27 18:45:06 -04:00
parent 6dd0e49e45
commit ef40f38ed0
15 changed files with 360 additions and 3 deletions
+26
View File
@@ -1949,3 +1949,29 @@ separate verification step; local Docker Linux engine/toolchain is unavailable.
Final native validation: Release 54/54 (3.66s), clang-tidy analysis 54/54 (13.37s),
ASan 54/54 (46.72s), format check and git diff --check passed. M6.6 is natively
qualified; the next gate is M6.7 interval scheduling. No deployment was changed.
## M6.7 local environmental intervals - 2026-09-27
ADR-0057 and ENVIRONMENTAL_SCHEDULING.md define the stateless interval adapter.
Admission validates world/frame, fixed quantum, completed process/field revision,
ordered endpoints, at most 64 ticks and an exact input count. Each process tick is
atomic; execution failure explicitly returns the committed prefix and failing tick.
No new scheduler state, snapshot format, biology rule, dependency or deployment.
Tests compare 130-tick streams under rules 1 and 2 against direct execution using
batch widths 1/3/17/64, flattened report equality and final canonical snapshots.
Every batch pauses without mutation and restores before continuing. Admission
cases include foreign/stale boundaries, quantum mismatch, missing/extra input,
65-tick backlog, u64-max backlog and reversed intervals. Failure at first, middle
and final tick preserves precisely the committed prefix, then restores and resumes
to the uninterrupted result. The existing valid u64-max checkpoint now also tests
scheduler pause and wrap refusal. Partial success is intentionally not a whole-batch
transaction; callers must inspect failure and committed count.
Executed tools/windows-check.ps1 -Preset release/analysis/asan -Action check:
Release 54/54 (6.44s); clang-tidy analysis 54/54 (14.20s); ASan 54/54.
After making the optional failure access explicitly guarded, rebuilt Release and
reran both environmental CTests: 2/2 passed. Analysis/ASan include that final guard.
Release format-check and git diff --check passed. Tests retain NDEBUG checks.
Linux/UBSan/TSan CI confirmation remains pending; native validation does not claim
a Linux or target-server run. Next is M6.8 integrated ecological qualification.