Anomalies — open queue, severity, cross-module auto-spawn

An anomaly is anything that didn't behave as expected — sensor reading off, alarm fired, crew reports something, telemetry gap.

To report one manually:
1. Anomalies tab → "+ Report anomaly"
2. **Vehicle** — which vehicle (auto-scopes to active mission)
3. **System** — power, propulsion, ECLSS, comms, GN&C, payload, structures, software, other
4. **Severity** — critical / major / minor / advisory
5. **Description** — what happened, what you observed
6. Save → goes into Open queue

Auto-spawned anomalies:
- **Life Support** critical alarms → anomaly auto-created with the alarm reference
- **Comms** critical outages → ditto
- **Propulsion** abort-feasibility failures → ditto

Workflow on an open anomaly:
- **Investigate** — post findings, attach telemetry, link to parts genealogy if a component is implicated
- **Root cause** — when known, record it; correlate with prior anomalies on the same system
- **Disposition** — open / under investigation / mitigated / accepted-risk / closed

Wally tool `mission_reportAnomaly` lets the crew dictate an anomaly from chat during ops.