Clarify retained server provenance in next UI gate

This commit is contained in:
2026-09-12 23:24:13 -07:00
parent 59ccfe0e3a
commit c26ee6d263
@@ -37,4 +37,4 @@ Key SHA-256 bindings:
## Scope and next evidence
The earlier 68a81c3 focused failure is separately preserved in [its archive](../scenario-renderer-gates-68a81c3-20260913/README.md); the corrected real-frame-padding evaluator now passes as part of all 87 focused checks here. This foundation gate does not execute the later saved-view workspace/display integration at [46e106c04e82e3d5b0acac43c99c7ee3e5a9c1b5](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/46e106c04e82e3d5b0acac43c99c7ee3e5a9c1b5), whose published 25 files were source-integrity verified only. The subsequent combined UI gate must cover its new controller/camera/usage tests, the strict correction, full desktop/server checks, strict lint and a GUI build. Native interaction and minimum-window acceptance remain separate requirements; no native acceptance or free graphical spacing gesture is claimed here.
The earlier 68a81c3 focused failure is separately preserved in [its archive](../scenario-renderer-gates-68a81c3-20260913/README.md); the corrected real-frame-padding evaluator now passes as part of all 87 focused checks here. This foundation gate does not execute the later saved-view workspace/display integration at [46e106c04e82e3d5b0acac43c99c7ee3e5a9c1b5](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/46e106c04e82e3d5b0acac43c99c7ee3e5a9c1b5), whose published 25 files were source-integrity verified only. The fresh 601-input UI gate has started at strict-corrected [2c9cd2b3e661ef85f11590c7128dcb2f502d0c26](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/2c9cd2b3e661ef85f11590c7128dcb2f502d0c26), with no pass claimed yet. It covers the new controller/camera/usage tests, full desktop, strict desktop lint and a GUI build. Its verified unchanged core/server/root-manifest scope retains the exact 37be410 server receipt and raw-log provenance (57 passed); it does not repeat server execution. Native interaction and minimum-window acceptance remain separate requirements; no native acceptance or free graphical spacing gesture is claimed here.