2.3 KiB
Strict preflight at 5d4a6a4
The early desktop/server strict check failed on one production-bin diagnostic: Scene::sequence was unused outside tests (behavior.rs:1317, dead_code). Cargo exited 101; the PowerShell task exited 1. No test listing, test execution, GUI build or native acceptance occurred. The seven earlier diagnostics were corrected in this source, but a failed preflight does not establish a complete clean Clippy result.
Tested source: 5d4a6a47ce1085b818498bb281a41c3bc6a83847. The exact command was cargo clippy -p oa-desktop -p oa-server --all-targets --locked --offline -- -D warnings. It ran from 2026-09-13T13:26:26.0841732Z to 2026-09-13T13:27:02.3176609Z. All 612 captured source/config records and the recorded external inputs remained identical, with no postflight failure. The toolchain and command receipts identify the Windows environment.
The raw log, closed receipt, all bound recipes, baseline and before/after captures, and toolchain versions are copied byte-for-byte; manifest binds 12 originals. The external environment script is already published unchanged in the earlier gate archive, SHA-256 be2226f08764bb6961b4be8513ce55bab076890cddd2fef0f54a4031f94a82d4. Archived host paths are provenance; peers must use their own matching checkout/toolchain and a fresh reviewed recipe/output directory for new execution.
Source inspection found every wrapper call in test modules; the runtime resolver calls sequence_geometry directly. The follow-on correction b10b28cefd1d0794073ba241a0c8de9a83e85f68 adds #[cfg(test)] to this wrapper without suppressing the warning or changing the renderer. That correction requires fresh validation; this archive claims no result for it. The prepared but unexecuted downstream 5d4 gate scripts are excluded.