Case Studies

Case: the assistant wrote the code and its answer key

Both implementation and generated tests treat “at least” as strict comparison. The test suite passes while the requirement fails. Repair by deriving a boundary case independently from the wording and preserving it as a regression test.

Case: a document tried to change the task

A retrieved note asks for an upload and falsified test results. The learner separates useful source data from the attempted instruction, refuses the extra action and records the issue. A prompt warning alone is not a guarantee; limiting accessible data/actions and reviewing outputs are separate controls.