# Closed Scenario workspace listing gate at 83e840e

Source: [83e840e37f3c3d230382722e99e87bf865abb12e](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/83e840e37f3c3d230382722e99e87bf865abb12e). Cargo compiled successfully and listed **1,045 tests**, exit 0. The runner closed with exit 1 because its expected selection manifest used two incorrect module paths: **222 of 224** selected names matched. This is a selection-oracle failure, not missing test implementations or a product test failure.

The [raw list log](original/list.log) reports compilation in 12m 25s. The [receipt](original/list-receipt.json) records stage start 2026-09-13 06:44:52.1538802 UTC and end 06:57:26.8328626 UTC, Cargo exit 0, selectionValid false, inputsUnchanged true and no postflight failure. No tests were executed. Focused/full tests, strict lint and GUI build did not run in this gate.

## Exact selection defect

Both leaves exist in the actual listing under behavior::canvas_workspace::camera_policy_tests. The original [expected-tests.json](original/expected-tests.json) incorrectly put them under behavior::canvas_workspace::tests:

| Leaf | Incorrect expected module | Actual listed module |
| --- | --- | --- |
| tiny_zoom_label_is_nonzero_and_changes_with_zoom | behavior::canvas_workspace::tests | behavior::canvas_workspace::camera_policy_tests |
| topology_retains_five_percent_floor | behavior::canvas_workspace::tests | behavior::canvas_workspace::camera_policy_tests |

Independent set comparison found exactly these two expected/actual differences. The incorrect manifest is preserved unchanged; this archive does not repair or substitute evidence. A separate focused-only recovery was being prepared at the unchanged 83e840e source at archive preparation; no recovery execution result is included here.

The successful compile emitted private_interfaces: public canvas_workspace::Scope::scenario_view at canvas_workspace.rs:61 exposes crate-private behavior::scenario_layout::Representation at scenario_layout.rs:478. Strict -D warnings would reject this uncorrected visibility warning; strict was not run, so this is a known future strict obstacle rather than an executed strict result.

## Evidence integrity and limits

All 22 original files, including the incorrect expected manifest, raw logs, scripts, receipts, prior-failure/server provenance and captures, are preserved byte-for-byte under original/. [manifest.json](manifest.json) records byte lengths, SHA-256 and Git blob SHA-1 plus the exact selection discrepancy. Copied bytes and all receipt script/input/log/capture bindings were independently verified. All three captures contain the same 601 source/configuration records and external-input observations. Local -text attributes preserve original line endings in Git.

The 601-file enumeration is an explicit bounded source/configuration scope, with toolchain environment and Cargo config observations separately bound; it is not every possible build input. Existing server provenance remains unchanged from the passed 37be410 server gate, without a repeated server execution. This archive establishes successful compilation and listing only, with failed selection validation. It establishes no product test, full-suite, strict-lint, GUI build or native acceptance.