LAB13 — Expose freshness without changing policy

Start CP05 in a fresh folder. Suggested time: 45–60 minutes. Run .\scripts\replay.cmd fixtures/normal.csv and record its output/exit. Attempt .\scripts\build-firmware.cmd and preserve the actual result separately.

Add JSON Boolean current to each sample record using the existing Snapshot.current flag. Change only the status formatter and its reporting description. Preserve bounded formatting, existing fields, policy, acquisition, timing, dependencies, and exact target.

Run normal and stale-recovery fixtures. Parse each output line as JSON and verify Boolean type. The stale-recovery current flags must be true, true, true, false, true, false, true, true. The state/error sequence must remain unchanged. Explain why a recovering FAULT can have current data.

Cross-build the changed source and save its actual receipt or exact open dependency. Inspect the final diff. Submit the patch, updated output contract, original/modified replay records, build evidence, and limitations. A strict consumer may require an intentional schema update for the new field.

If the output is wrong, inspect the format placeholder/argument pairing and the mapping to the existing flag. Do not alter policy to make the report look convenient. Recover from the preserved CP05 copy if necessary. Chapter 13 contains the worked answer and the PowerShell JSON inspection sequence.