# LAB04 — Chapter 4 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.

Your deliverable is `setup-record.md` and a short inspection review. Record the actual folder, tool versions, checkpoint, one baseline command, and its result. Then request a file-based explanation and identify at least two claims you can check in the files. State where a proposed command would run and whether it actually ran.

For success, the record must let you distinguish four outcomes: the tool is unavailable; the tool starts but the project check fails; the project check passes; or an account limit prevents the agent interaction. A learner who documents and correctly diagnoses an unavailable tool has made useful progress, but should leave the baseline check incomplete until it executes successfully. Do not turn an incomplete setup into a pass by borrowing another machine's output.

Stop the agent with the interface's stop control if it is doing the wrong task. After stopping, inspect files and terminal state before resuming. An interrupted turn may have completed some actions. Save the current state and start again with a brief that names what remains. “Stop” is a control action, not a guarantee that nothing happened before it.

## 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.