ElyOffice/tasks/reviews/L1.1-r1.md

FAIL

Cargo.toml:25 — The new backend features require dependencies absent from the tracked Cargo.lock. In a clean copy, cargo build --locked -p ely-tree and locked metadata both exit 101 because the lockfile needs updating; the smoke script hides this by adding 26 packages during cargo tree. Commit the matching lockfile and verify a clean locked build. Evidence: .work/l1.1-r1-locked.log, .work/l1.1-r1-backends.log.

tests/scripts/linux-backends.sh:30 — The executable path ignores Cargo's target directory. With a separate CARGO_TARGET_DIR, the probe successfully built ElyTree there, then failed because $root/target/debug/ely-tree did not exist. If that path contains an older binary, the script tests that binary instead of the build it just produced. Resolve and launch the actual Cargo build artifact. Evidence: .work/l1.1-r1-custom-target.log.

tests/scripts/linux-backends.sh:32 — ready ElyTree does not establish that a frame was presented: its next-frame callback runs before presentation. In an isolated, rebuilt probe, replacing platform_window.draw(...) with a no-op still made this script exit 0 and claim both backends drew. Wayland tracing confirmed zero surface-buffer attachments, versus one with the original binary. Require successful presentation and compositor-visible rendered content before reporting success; a disabled presentation path must fail this test. Evidence: .work/l1.1-r1-no-presentation.log, .work/l1.1-r1-presentation-evidence.log.