Archive closed Scenario renderer gate and strict failure

This commit is contained in:
2026-09-12 23:12:18 -07:00
parent 10c870b464
commit a5ffd10a0d
36 changed files with 44488 additions and 1 deletions
+1 -1
View File
@@ -42,7 +42,7 @@ No schema extension is required by this resolver proposal. No gesture/navigation
## Source implementation checkpoint
The subsequent [closed 68a81c3 Windows gate](experiments/scenario-renderer-gates-68a81c3-20260913/README.md) compiled and listed 1,010 tests, then failed focused execution (86 passed, one failed). All 591 inputs remained unchanged; full desktop/server/Clippy/GUI build stages were not run. The archive retains the actual failure and distinguishes the source-derived frame-padding correction 37be410 from execution evidence: that correction is unexecuted at this checkpoint. The paragraphs below describe the earlier source-only checkpoint.
The [closed 68a81c3 Windows gate](experiments/scenario-renderer-gates-68a81c3-20260913/README.md) preserves its focused failure (86 passed, one failed). The corrected [37be410 foundation gate](experiments/scenario-renderer-gates-37be410-20260913/README.md) then listed 1,010 tests, passed all 87 focused tests, completed full desktop at 1,007 passed/0 failed/3 ignored and server at 57 passed including the actual Scenario HTTP test, with all 591 captured inputs unchanged. Strict Clippy failed on five collapsible_if findings in scenario_layout.rs; this gate is closed failed and no GUI build ran. The later published workspace integration 46e106c has exact 25-file remote/local source verification only, with no UI compile or runtime acceptance at this checkpoint. A subsequent combined gate must validate the strict correction and UI integration; these foundation results do not transfer strict or GUI acceptance to that source. The paragraphs below retain the earlier source-only checkpoint.
Candidate [68a81c3](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/68a81c3f50d846e34cae96090979543878514c1e) contains the pure resolver and actual Scene adapter with 22 prepared tests. It retains the resolved Scene with explicit representation/owner identity, exact render-lane centers, origin-bearing bounds and latent message addresses. It does not wire saved views into workspace, camera, usage or gestures. The source is published and all 13 changed contribution files match remote blobs and sizes; no combined compile or execution is claimed at this checkpoint.