# FND010-LAB1 — local release-aware change control

1. Run `python run_lab.py` to create the primary local fixture. If you intentionally need to discard and recreate an owned lab workspace, use `python run_lab.py --reset`.
2. Read `workspace/fixture_metadata.json`, inspect the graph with `python inspect_state.py`, and read `task_brief.json`.
3. Evaluate the requested change on the target line. You may compare merge/rebase/cherry-pick/reconstruction/reversal options as appropriate; the lab does not prescribe one history aesthetic.
4. After any candidate change, run `python run_checks.py`. Record the Git result and behavior result separately.
5. Resolve `v1.4.1-candidate` to its actual commit. Do not treat the tag as deployment proof.
6. `simulate_external_effect.py` creates a synthetic state outside the repository. Use it to reason about what a later Git revert would and would not reverse.
7. Complete `release_aware_change_control_record.csv` and `submission_notes.md`.

For transfer assessment, the assessor provisions `transfer_workspace` before learner delivery. Use that provided fixture; learner-side generation is not required. No network or credentials are required.