# LAB05 — Chapter 5 practical exercise

Read the [chapter](chapter.md) and complete its worked example first. Use a fresh copy of the named resource/checkpoint so the starting state is recoverable.

Starting from your baseline commit, perform the supplied reporting-label edit independently. Write a one-sentence acceptance statement before editing. Use the editor to make and save the change, inspect the ordinary diff, and run the relevant check. Stage the exact file and inspect the cached diff. Then commit with a message explaining the reporting purpose.

```powershell
# Context: PowerShell in the practice repository; inspect before committing.
git status
git diff --cached
git commit -m 'Clarify synthetic input in the report label'
git log --oneline -2
git status
```

Your deliverable is two explanatory commits plus a short note identifying the baseline and label change. The expected observation is a history whose second entry contains only the intended change and any deliberately associated documentation. Your IDs and timestamps will differ from the book. Figure SS05-05 shows the teaching history and message order.

As an additional staging check, edit a harmless sentence in the README, stage it, then edit that sentence again. Inspect both diff views without committing. Explain which version would enter a commit now. Restore your chosen final sentence in the editor and restage only if you intend to keep it. This shows that “staged file” does not mean every future edit to that file is automatically selected.

## Submission check

Submit the named artifact with actual/synthetic/illustrative evidence labels. Include a starting state, action, result, and remaining limitation. Compare with the separately distributed instructor key after your own attempt. The chapter's completion checklist and transfer task remain part of the learning activity.