Record implementation package and standalone route validation

This commit is contained in:
UnixNight committed 2026-10-25 19:59:41 -04:00
1 parent 09cf1172bf
commit b915a2c2e4
3 files changed
+17

No files matched your search

+5
View File
@@ -76,3 +76,8 @@ allowed where it resolves a core-system question, without waiting for every leve
errors, SDL dummy lifecycle and539 unchanged hashes. RETURN also verifies
retained input order and tutorial availability normalization. Packages rebuilt
after the implementation milestone; platform runtime claims remain separate.
- Packages: clean09cf117 Linux/Windows self-contained outputs; Linux launch from
/tmp passes practice/RETURN and outside scene load. Release validation layers
unavailable; source full integration validated above. Package evidence recorded
separately without changing runtime. Continue the remaining source-state and
shared-camera/control/collision gates rather than resuming feature expansion.
+6
View File
@@ -12,6 +12,12 @@ SDL dummy lifecycle and539 unchanged original hashes. GPU validation is enabled
and every run reports zero errors. Native Windows runtime and original-game
comparison are not added by these tests. Known limits remain explicit in the
current checkpoint coverage/implementation reports.
Both self-contained packages now identify clean09cf117. Linux release smoke from
`/tmp` passes practice/RETURN (including input order and gadget availability) and
outside load; see linux-package-return.log and linux-package-outside.log under
artifacts/implementation/. Those release invocations have validation unavailable;
the enabled-validation evidence is the full integration run above. Windows is
cross-published, with no additional native Windows runtime claim.
Architecture checkpoint: see `checkpoint/review.md` for coverage and remaining
gates. C1 objective/task order and C2 per-actor Carl callback corrections pass the
+6
View File
@@ -32,6 +32,12 @@ retained input ordering and enabled gadget state1 after tutorial state4. The
preserved baseline's240-step walk and new phase implementation have essentially
identical completed travel/final position, with the intended within-frame delay
verified separately. No native Windows/original runtime comparison is claimed.
Self-contained Linux/Windows packages rebuilt from clean09cf117
(`artifacts/implementation/package.log`, both BUILD-INFO source_dirty=no).
Linux release runs from `/tmp` pass lab→VR04→lab RETURN assertions and a direct
outside scene load; source static query construction succeeds in all three route
profiles. Release invocations lack validation layers; the full source integration
above runs with validation enabled. Later changes only record this package evidence.
## Architecture reverse-engineering checkpoint