wireguard-admin/docs/evidence/milestone-10.md

Milestone 10 acceptance evidence

Run: 2026-10-26T21:07:24Z, local development workspace. This report covers the styled TUI keyboard footer only. Milestone 9 remains retired and unaccepted.

Source and environment

• HEAD: e141c03c2c401b09ad0fa78557cb9403640ea80a; working tree was dirty with PLANS.md, README.md, src/delivery/qr.rs, and src/tui/render.rs. The following SHA-256 values identify the relevant integrated inputs at the gates: render.rs 40e2abc891cc562a628eb661dcdcd3e052818c4332c25f3ae555e184d9adb65d; forms.rs 8ecbd614c1ecc7f1ab4cbae9223f9820c5d8315c62a54cffbc6d5c2e640f6c31; qr.rs b8d30e6b24370fd1e3d666586481af74b12f279043cb1e0a7a1e61923588c4b8; README.md fa4ef797565895dbd78f920e92263df718720bdb84dba48da88e611020638741; Cargo.lock b8549df27f971dc550218cfc28e788f6630a1e13e7df538aded38e969ab713b6.
• rustc 1.97.1 (8bab26f4f 2026-07-14) and cargo 1.97.1 (c980f4866 2026-06-30). The release build used the locked local target; no container, VM, production service or VPN was accessed.

Checks and scope

Exact command	Result
cargo test --locked tui::	Exit 0; 38 TUI unit tests passed.
cargo test --locked --test tui_workflow	Exit 0; 6 integration tests passed, including isolated PTY smoke.
cargo fmt --all -- --check	Exit 0.
cargo clippy --locked --all-targets -- -D warnings	Exit 0 after M10.3-R1 repair.
cargo test --locked	Exit 0; 271 library units passed, 2 opt-in container drivers ignored; all integration suites and 2 compile-fail doctests passed. The Testcontainers target reported 25 passed and 1 ignored; no opt-in Alpine run occurred.
cargo build --locked --release	Exit 0.
git diff --check	Exit 0.

The TestBackend checks cover 120×30, 80×24, 40×8, 34×8 and below-minimum rendering. They assert visible footer interior, styled key labels, applicable 80×24 list actions, compact navigation/Help and overflow, context-specific forms/progress, and QR Esc guidance without fixture payload disclosure. These are synthetic buffer checks; no physical terminal QR scan or systemd behavior is claimed.

Review and decision

Independent M10.1 review found R1/R2 context/form hint issues; repair and re-review closed both on the integrated implementation. A separate fresh integrated M10.3 review found R1 (Clippy failure) and R2 (README context overstatement). The repairer fixed both; the same independent reviewer re-reviewed the repaired state and reported no remaining actionable finding. The reviewer supported M10-A1–A5 within synthetic/PTY scope; the coordinator's full gates above satisfy M10-A6. Compact QR may show a too-large condition at 34×8 while retaining Esc clearing guidance. M10 acceptance is scoped to TUI presentation and does not upgrade M9 systemd/IPv6 evidence.