# M02-L02 — Configure the project workbench

**Outcome:** Open the intended root, run its applicable baseline, and verify file-based inspection.

**Start:** M02-L01; CP00 inspection resources and CP01 baseline bundle.

Open the extracted `sensor-monitor` folder in VS Code. The editor's active file and terminal working directory are separate state. In its integrated PowerShell terminal, run `Get-Location` and `Get-ChildItem`. Confirm the root against the checkpoint README before executing relative paths.

CP00 is an inspection packet. CP01 supplies the minimal executable host report and firmware build. From the CP01 root, use the documented Windows command wrappers:

```powershell
.\scripts\replay.cmd
.\scripts\build-firmware.cmd
```

Run each separately and save its actual result. The replay compiles and exercises software with synthetic input. The firmware command cross-compiles for the recorded target and options. No upload or physical observation is implied. The `.cmd` path requires no PowerShell execution-policy change; follow the matching project's dependency and setup documents.

**Recording note:** Idle waits between the recorded replay/build commands and their results are shortened. The commands, actual results and exit state remain visible. CP01 prints one fixed synthetic sample at 25.00 °C; it does not parse the CSV fixture. The later artifact listing inspects retained build files, and the labeled output transcription preserves the original results.

Record Git, compiler, Arduino CLI, and core versions. A native host compiler and the target cross-compiler have different jobs. A command that starts successfully does not prove every dependency is installed. The setup record should distinguish tool discovery, replay result, and cross-build result.

Ask the agent to read the README and introductory source, explain input/output, name the files used, and make no edits. Inspect the actual access controls and action record, then compare its claims with the open files. The official Windows sandbox documentation explains current runtime choices; do not substitute a prompt for actual controls. [Codex Windows sandbox](https://learn.chatgpt.com/docs/windows/windows-sandbox)

If PowerShell cannot find a tool, use `Get-Command` and the documented installation location. If a program exits before printing, record its exit code and inspect the supported runtime path; do not change policy code to fix a loader failure. If the agent is limited, complete the local checks and leave that interaction pending.

## Practice and completion

Complete the [exercise](exercise.md), then compare your artifact with the separately distributed instructor answer. A lesson acknowledgment records your own progress; it does not certify that a physical test occurred.

## Reading and figures

[Chapter 4](../../../../book/chapters/ch04/chapter.md). Resources: [Project checkpoint guide](../../../../examples/sensor-monitor/docs/checkpoints.md) and [toolchain setup](../../../../examples/sensor-monitor/docs/setup.md). Figure references: SS04-04–06.