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

FAIL

tests/scripts/linux-backends.sh:36 — Executable selection still assumes Cargo's native output layout. With CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu and a separate CARGO_TARGET_DIR, the locked build succeeds under /x86_64-unknown-linux-gnu/debug, then the script fails launching nonexistent /debug/ely-tree. An older native binary there would be tested instead. Launch the executable reported by Cargo's build-artifact JSON. Evidence: .work/l1.1-r2-explicit-target-build.log, .work/l1.1-r2-explicit-target.log.

tests/scripts/linux-backends.sh:55 — The text assertion counts contrasting control fills and icons, so it passes without any text. In an isolated rebuilt probe, returning immediately from Window::paint_glyph still makes the script exit 0 on both Wayland and X11. The inspected window has no text, yet its ink count is 10578 against the 500 threshold. Check known rendered text in a region excluding control fills and icons, and verify that disabling glyph painting fails the assertion. Evidence: .work/l1.1-r2-no-glyphs.log, .work/l1.1-r2-glyph-evidence.log, .work/l1.1-r2-mutation.log.