d9b1137c93
Their newest class -- the instruction is dead AND the working one is undocumented -- inverts last iteration's sweep. I checked documented->parsed; the reverse is parsed->documented, and it enumerates, so it completes rather than samples. Eighteen flags parsed, fifteen documented, three live and undocumented: --film-interval and --skip-at (used by verify-dwell, in no usage example) and --no-hold, which plays a screen past its rest instead of clamping each element at its hold, documented in DECISIONS.md and absent from the header a reader consults. A capability that exists only in an 11000-line record does not exist to anyone reading the interface. Then I documented it wrong in the same command. I wrote the example as --screen=title --no-hold --time=6 and tested it: the renders are byte-identical because --time sets frozen and pose_at tests 'holding and not frozen', so an explicit instant makes --no-hold inert. Without --time the pair differs by max 253. I wrote a dead instruction inside the commit fixing dead instructions, and it only failed to ship because I ran the example rather than trusting that a parsed flag works -- the gap I had named one iteration earlier. Strongest evidence yet for their ranking: a wrong description costs a reader's belief, a wrong instruction hands them a null result that looks like a finding. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
61 KiB
61 KiB