T-18 says there is no release, and PROGRESS.md names the wrong one #46

Two tracker records are older than the tree they describe.

docs/todo/infrastructure.md T-18 is titled "There is no release", status open, priority high. The release workflow exists (.github/workflows/release.yml), and gh release list shows v0.1.0 through v0.2.7 (v0.2.7 is the latest). The entry's premise ("The aarch64 half has never been built anywhere") is also stale: release.yml builds aarch64 and the other five targets, and docs/report/10-measured-versus-assumed.md records the cross builds.

docs/todo/PROGRESS.md:11 says v0.2.6 "is published" and its workflow table says release is green "on v0.2.6". v0.2.7 is published. The work order below it still opens with the glfwd_try_soname fix, which merged as PR #41 and is in v0.2.7, so it sends the next session at work that is already done.

PROGRESS.md is rewritten every session by design, so the stale work order is the more damaging half: it is the file docs/AGENTS.md tells a session to read first. T-18 should close in place with the acceptance command run (gh release list), or be rewritten to whatever is actually left undone (for example the PowerShell floor drift), and PROGRESS.md should carry the current release and the current work order.