sylpheed-port found a harness note asserting an unestablished fact under a
load-bearing number. Swept my printed output: 38 lines assert a screen or game fact
and the assertive ones are computed in the same run, so no instance there -- though
the sweep is keyword-based and the criterion is a judgement.
The class is real on the larger surface, and I have a known instance: ring_row.py
documented its calibration as 49.5 + 1.060*design_y, wrong because it was fitted
against menu_focus.py's approximate rows rather than the disc's. It sat in the file
underpinning every focus finding and was found by accident.
Tool docstrings carry calibrations, thresholds and claims about the game, nothing
verifies any of it, and unlike a why in an authored file there is no convention
demanding a citation.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
f1f23fc74c