Files
ARCADIA-Studio/harness/experiments/scenario-renderer-gates-37be410-20260913

Closed Scenario renderer Windows gate at 37be410

This archive records the completed attempt2 at source 37be41092beb1c940f345072df1e017ce45fe2fc. The gate is closed with a strict-lint failure. It is not a successful release or GUI acceptance gate.

Results

Stage Actual outcome Evidence
Desktop list Exit 0; exactly 1,010 unique tests listed receipt, raw log
Focused desktop Exit 0; 87 passed, 0 failed, 0 ignored; 923 filtered receipt, raw log
Full desktop Exit 0; 1,007 passed, 0 failed, 3 ignored, 0 filtered; test-reported duration 1220.70 seconds receipt, raw log
Full server, all targets Exit 0; 57 passed, 0 failed, 0 ignored across result groups 4/0/51/2 receipt, raw log
Strict Clippy, desktop and server all targets Exit 101; five collapsible_if errors in scenario_layout.rs receipt, raw log
GUI build Not run: the required prior strict stage failed No build receipt or executable acceptance is claimed

The 87 focused tests are the exact union of 12 existing dispatch/SVG/source-rename regressions, 53 typed activation/lifecycle/direct/atomic tests and 22 resolver tests. The full desktop executed multiset matches the list, including all 87 passing once. The three ignored tests are recorded by exact name in the full receipt; they are two source-rename timing probes and the 100-module source-symbol scale probe. Server execution includes exactly one passing scenario_layout::saved_scenario_positions_roundtrip_through_http_without_partial_or_noop_writes, exercising actual HTTP transactions/source/restart behavior.

Clippy reports collapsible_if at crates/oa-desktop/src/behavior/scenario_layout.rs lines 307, 316, 454, 676 and 709 in the tested pin, then fails oa-desktop compilation. This is an actual closed failure, not a waived warning or an unexecuted stage. Any correction requires its own pinned validation; these results do not establish strict success for a later commit.

Identity and archival verification

All 37 original gate files are retained byte-for-byte under original/, including the original preparation README, scripts, raw logs, receipts, package-clearance evidence and every capture. manifest.json gives each original byte count, SHA-256 and Git blob SHA-1. The archive uses local -text attributes to preserve original CRLF/LF bytes in Git. At archive creation every copied file matched its source bytes, every receipt's script/input/log/capture/prior-stage hash binding was independently checked, and all eleven captures contained exactly the same 591 version-controlled input records and external-input observations.

The 591-file scope is the explicit source/configuration selection documented in original/enumeration.json and original/expected-inputs.json; it is not a claim to hash every possible toolchain or registry input. External env.ps1 and Cargo config presence/absence remain separately bound. Every executed stage ran locked/offline in the frozen Scenario renderer worktree with the shared root target, following explicit oa-desktop package clearance while retaining dependencies. Exact commands, paths, tool versions, timestamps and statuses are in the unchanged original receipts.

Key SHA-256 bindings:

Evidence SHA-256
Initial 591-file capture ac2cfde68c6a8046fdfd5502aa35b4470dba9a9758621a115bac14c5845708e3
run.ps1 177f9366c09110feaa1d8c59401fb184776b39820018baa16d0b2561f0cc7748
Full desktop raw log 908e77a02f3cad6435ed3db550ca2d1a56b4ba8f5026633560b9d5fea0a15654
Server raw log 7c7d847ac942b23a33081fdc3eb9ec53a2c054cd422810e30528b5930c574d71
Strict raw log 160946a38372567a313d7e1739c4869b4c080f797d71f23fbcdda105ce53453d

post-execution-test-binary.json records the still-present 149,178,368-byte desktop test executable named by all.log, observed after full execution and the closed strict stage. Its SHA-256 is 395d60301964b1f5eba0e3c7e9df939a51d78b063a4d7f6ab84988a49702fb8a. This is explicitly a post-execution hash; no pre-execution hash existed, so it does not retroactively prove executable bytes at execution time. The executable itself is not copied into this source archive.

Scope and next evidence

The earlier 68a81c3 focused failure is separately preserved in its archive; 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, whose published 25 files were source-integrity verified only. The fresh 601-input UI gate has started at strict-corrected 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.