epic: 1.0 readiness

[nextestudios]

Summary

Hardware validation, unknown-controller mapping, device selection, security hardening, staging cleanup, UI automation, signing, package size and key rotation.

Motivation

The spec forbids announcing 1.0 while essential journeys are unvalidated on real hardware.

Scope (in recommended order)

• test: validate the controller matrix on real hardware #78 — test: validate the controller matrix on real hardware (priority: high)
• feat: add a mapping wizard for controllers without a known profile #79 — feat: add a mapping wizard for controllers without a known profile (priority: high)
• feat: switch the active controller explicitly and diagnose duplicate devices #80 — feat: switch the active controller explicitly and diagnose duplicate devices (priority: medium)
• security: handle-based destination checks against junction races #81 — security: handle-based destination checks against junction races (priority: medium)
• feat: clean up leftover staging folders from interrupted operations #82 — feat: clean up leftover staging folders from interrupted operations (priority: medium)
• test: add WinUI automation tests for focus, dialogs and the virtual keyboard #83 — test: add WinUI automation tests for focus, dialogs and the virtual keyboard (priority: medium)
• chore: set up code signing for releases #84 — chore: set up code signing for releases (priority: medium)
• enhancement: reduce package size by trimming unused Windows App SDK components #85 — enhancement: reduce package size by trimming unused Windows App SDK components (priority: medium)
• security: support update-signing key rotation #86 — security: support update-signing key rotation (priority: low)

Dependencies

• feat: detect the active controller family (Xbox, PlayStation, Nintendo, generic) #32 (M2) → test: validate the controller matrix on real hardware #78, feat: add a mapping wizard for controllers without a known profile #79

Acceptance Criteria

• Every issue in the scope is closed or explicitly moved out of the milestone with a reason.
• PROGRESS.md, both changelogs and the relevant docs reflect what shipped.

---

Tracking issue for milestone 9 · 1.0 Readiness. Priority: high.