Safety Override Demo

TODO:

• [ ] Add page-specific notes for portfolio-evidence/demonstrations/safety-override-demo.md after inspecting the real project files.
• [ ] Cross-link Safety Override Demo to the most relevant code, data, testing, and safety pages.
• [ ] Identify the exact claim this page is supposed to support.
• [ ] List the public-facing evidence needed for this claim.
• [ ] Add links to videos, photos, logs, screenshots, or reports that prove the claim.
• [ ] State what a general reader should understand after seeing the evidence.
• [ ] State what a technical reviewer should be able to verify from the evidence.
• [ ] Separate proven results from still-in-progress work.
• [ ] Add dates, model versions, dataset names, and test conditions where relevant.
• [ ] Add limitations so the evidence is honest and not overstated.
• [ ] Add the demo file, date, model version, and what behavior is visible.
• [ ] Add what a viewer should not infer from this demo.
• [ ] 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.