Closed focused Scenario workspace recovery at 83e840e
Source: 83e840e37f3c3d230382722e99e87bf865abb12e. Direct execution of the already compiled desktop test binary closed with exit 101: 222 passed, 2 failed, 0 ignored, 821 filtered, test-reported duration 146.41 seconds. All 224 corrected selected names executed exactly once. The receipt records 2026-09-13 07:05:27.6737646 UTC through 07:07:55.2710548 UTC, unchanged inputs and no postflight failure. Full suite, strict lint and GUI build did not run.
Preserved failures
The raw log records both failures under behavior::scenario::workspace::tests:
- production_scenario_camera_external_controls_bounds_and_retained_deltas_cancel_old_drags, workspace/tests.rs:1355:9: vector equality failed; actual (37.999992, 80.411766), expected (30.0, 6.0).
- production_scenario_canvas_keeps_bounds_draft_identity_and_camera_through_editing, workspace/tests.rs:54:13: mounted-input assertion failed at scale 1; the log retains the actual ScenarioCanvas(BeginOccurrence) for Observation, including its full captured context, slot and lifeline identity.
These are actual failed tests. This archive does not assign their cause or claim a correction passed. The receipt's selectionValid false reflects the unsuccessful focused gate; independent comparison confirms all 224 intended names executed, so it is not another missing-name failure.
Binary and previous listing provenance
This recovery corrected the two expected module paths from the closed listing archive without changing source or recompiling. That original attempt retains Cargo exit 0/list 1,045 and selection-oracle failure; original-list-binding.json preserves its exact receipt/log/script/input hashes and incorrect/actual names.
The binary named by the original list log was bound after successful list compilation and before focused execution, not before listing: 149,769,728 bytes, SHA-256 f13052006fcbfb521b0cb1b94d97ae1c3b068342254e4512147bbe44a5fdfd9e. Its exact path and hash appear in both the original-list binding and focused receipt. The recovery invoked that executable with the exact 224 names, --exact and --test-threads=1; no Cargo, compiler, cleanup or GUI command ran in this recovery. The binary is not copied into this archive.
Integrity and limits
All 15 original files are preserved byte-for-byte under original/, including raw output, corrected expected selection, receipts, scripts, captures and prior-list provenance. manifest.json records original byte lengths, SHA-256 and Git blob SHA-1. Archive verification checked copied bytes, receipt/preparation/prior-list bindings, binary identity agreement and exact executed membership. All three source captures retain the same 601 records and external-input observations. Local -text attributes preserve original line endings.
This bounded source/configuration scope is not every possible build input. The existing private_interfaces warning remains a future strict obstacle at 83e840e; no strict result or GUI/native acceptance is claimed. The earlier failed-list evidence remains unchanged and linked rather than rewritten.