# LAB08: add a recoverable troubleshooting path

Allow about 25–40 minutes. Extract CP02 into a new `lab08` exercise folder or use your existing preserved copy. Do not overwrite earlier work. Open the Sensor Monitor root and note the starting Git status if it is a repository.

1. Read the README from the perspective of a person returning after a month. Mark one unclear prerequisite or working-directory assumption.
2. Add a **Troubleshooting** section with a “Script not found” entry. Explain how to confirm the project root and locate `scripts/replay.cmd` before retrying.
3. Include a relative link to `docs/hardware.md`, plus a sentence explaining when it is needed. Keep host replay and firmware compilation as separate actions.
4. Open the Markdown preview. Follow the relative link, return to the README, and copy the replay command from the preview into the intended terminal.
5. Run the documented check when the required tools are available. Save the actual outcome, checkpoint, command, and any remaining setup problem in your exercise notes.
6. Review the diff. Confirm that your change improves navigation or reproduction and does not introduce machine-specific paths or unrelated source edits.

Submit the edited README and the short check record. If tool setup is incomplete, your formatting and link checks can still be complete, but the build-path check remains open. Record the exact missing dependency; do not award yourself a passing execution result merely because the command is present.


## Evidence record

Record checkpoint, changed files, exact actions, actual results, and limitations. Preserve the starting exercise copy. Expected behavior is a criterion, not an observed run.