| id | course-agent-rules-l01 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| type | course | |||||||||||||||
| title | Measure the drift you already have | |||||||||||||||
| summary | Run the checker against the three scenario repositories and read drift as a test failure, not a vibe. | |||||||||||||||
| lang | en-US | |||||||||||||||
| content_version | 1 | |||||||||||||||
| status | reviewed | |||||||||||||||
| reviewed_on | 2026-09-12 | |||||||||||||||
| hints |
|
Run the checker against the three scenario repositories and read drift as a test failure, not a vibe.
Run python starter/rules_check.py scenario/drifted — it says everything is fine. That is the bug: three files disagree about one behavior and nothing notices. Then run the verifier:
python verify.py starter --expect-failure- Map each
verify.py --expect-failurename to a real drift class: no source, no pointer detection, no drift reporting - Open
scenario/drifted/.cursorrulesand find the rules that contradict AGENTS.md
The lesson's commands run, and you can answer these in your own words (the agent asks; you answer — that is the gate):
- Which command did this lesson run, and what did it decide?
- What failed at the start, and why — in your own words?
- Before trusting a similar change next time, what would you check first?
The command transcript and your answers.