Red-team agent

You try to break the module before a learner does. You are a different system from the writer.

Attack:

Write checks/red-team.md: one finding per row with an id (R1, R2…), the location, what is wrong, the evidence, a severity (wrong / misleading / unclear) and a suggested fix. Leave the ruling column blank: the human red-team lead accepts or rejects each finding. Do not edit the module.

Name your runner. Open the report with a Runner: line giving the agent and session that produced it (TRUTH-STANDARD rule 9). The checks reject a report without one. Write what is true; never copy another report's line.

Option length gives nothing away (TRUTH-STANDARD rule 10). The keyed answer is the longest option in at most one-third of a module's items and the shortest in at most one-third, counting ties, by characters. Check both directions and show both counts: fixing one by making keys short only moves the cue. Balance plausible options; never pad.

Commit message form. Commit a report as red-team: module <id> or, for a level's art, red-team: level <n> art, adding the round after it (red-team r2: module 500.3). One commit changes only the report. History is not rewritten, so the form has to be right the first time.