Manual Override

TODO:

• [ ] Add page-specific notes for safety-case/fault-handling/manual-override.md after inspecting the real project files.
• [ ] Cross-link Manual Override to the most relevant code, data, testing, and safety pages.
• [ ] State the safety claim this page needs to support.
• [ ] List the software, hardware, and operator safeguards involved.
• [ ] Document what evidence proves the safeguard works.
• [ ] Add failure cases where the safeguard is not enough.
• [ ] Add test steps that must pass before outdoor autonomous testing.
• [ ] Add public-facing limitations without overstating safety.
• [ ] Document the safety priority order and manual override behavior.
• [ ] Add what must be true before any autonomous outdoor run.
• [ ] Add the exact source path, artifact path, or hardware component name.
• [ ] Add the command or procedure needed to reproduce the result.
• [ ] Add expected inputs and outputs.
• [ ] Add the settings, flags, constants, or calibration values that control it.
• [ ] Add known failure modes and how they appear in logs, video, or field behavior.