8afe691301
build / mod (push) Failing after 32s
A battery's "why" now starts with one typed reason shared by the monitor, the HUD and the chat: only observation, waiting for a track, busy channels, no ammunition, or ready. It carries the age and the station of the mark it is about, and `/airdef why <n> source` moves the monitor to that station. The reason is computed from the same predicates the launch decision uses, and the detailed decision settles it, so a headline cannot promise or deny a shot the simulation does not take. The after-action review builds 4-5 measured steps per contact from the recording's scene journal and events: mark, handoff, lock, launch, outcome. The menu lists them per battery with a filter and opens a replay frame on a click (the outcome clip, else the map held at the launch or mark); `/airdef chains [battery]` prints the same list. Missing transitions stay missing and marked as no launch, never guessed, and the normal HUD still shows only the battery's own picture. Co-Authored-By: Kimi Code <noreply@moonshot.ai>