RD note from alpha field testing (2026-07-05):
In the app-level Timers page, allow marking one timer as the default. Every newly created event then starts with that timer already selected (instead of today's manual per-event selection), with the per-event choice staying editable as now.
Design notes:
- One default max; probably a star/radio affordance on the timer rows.
- The built-in Mock should stay selectable as default (useful for demo/dev rigs); a REAL rig would star its RotorHazard.
- Event creation (manual + wizard path) reads the default at creation time only — changing the default later doesn't retro-touch existing events.
- Registry-level persistence (
timers.json / registry meta) rather than per-event.
Not release-blocking; noted during v0.4.0-alpha.1 prep.
RD note from alpha field testing (2026-07-05):
In the app-level Timers page, allow marking one timer as the default. Every newly created event then starts with that timer already selected (instead of today's manual per-event selection), with the per-event choice staying editable as now.
Design notes:
timers.json/ registry meta) rather than per-event.Not release-blocking; noted during v0.4.0-alpha.1 prep.