Field Failure To Dataset

TODO:

• [ ] Add page-specific notes for engineering-process/iteration-records/field-failure-to-dataset.md after inspecting the real project files.
• [ ] Cross-link Field Failure To Dataset to the most relevant code, data, testing, and safety pages.
• [ ] State the engineering decision, requirement, or policy being documented.
• [ ] List the options considered and why the current choice was made.
• [ ] Connect the decision to field failures, metrics, or hardware limits.
• [ ] Add files, flags, datasets, and tests affected by the decision.
• [ ] Add what would make this decision need to change later.
• [ ] Add how a reader can verify the decision from evidence in the repo.
• [ ] Add test date, time, weather, route, model version, and manual takeover count.
• [ ] Add what failed, what worked, and what data should be collected next.
• [ ] List dataset tag, image count, label count, source, and purpose.
• [ ] Add how to verify filenames, annotations, and correction labels match.
• [ ] 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.