LAB09: repair conflicting context

Allow 35–50 minutes. Use a new CP02 exercise folder. Read README.md, docs/project-brief.md, and docs/hardware.md. Create or update docs/requirements.md, docs/decisions.md, docs/evidence.md, and docs/handoff.md only with the populated content taught in this chapter. Label future threshold requirements planned; CP02 does not implement them. Preserve the supplied version before editing. Create an exercise note that records the starting checkpoint and the documents you inspect.

1. In a disposable copy of docs/hardware.md, seed the claim “The selected product 5477 has 8 MB flash.” Label the exercise note as an intentionally seeded fault so it cannot be mistaken for reference truth.
2. Open the manufacturer's product page for product 5477. Confirm that the page identifies the intended product, then locate its memory description.
3. Compare the seeded sentence with the selected target's source. Correct the active hardware reference to the documented 4 MB flash / 2 MB PSRAM identity, adding the source and relevant location.
4. Search the exercise documents for the stale 8 MB claim and the product identifier. Update references that actually describe this selected target. Do not globally replace unrelated numbers.
5. Add a brief decision or correction note explaining that a variant mismatch caused the contradiction. Keep the exercise's fault record separate from current guidance.
6. Read the resulting linked documents in order and review the diff. Confirm that the change corrected the fact without inventing a board-observed result.

Submit the corrected context and an evidence note with source, claim, correction, and remaining unknowns. The exercise tests source resolution, not possession of the physical board. A source that cannot be accessed is an open dependency; use the release's permitted source notes and record that limitation rather than fabricating a browsing result.

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.