sylpheed-port refined my ranking: rank silent instructions above loud ones. All
of theirs were loud -- wrong paths that error out and announce themselves --
while mine was silent: an inert env var returning a clean, wrong result. Only the
silent kind manufactures evidence.
The silent surface is enumerable, so this is a sweep rather than a sample: every
environment variable the docs name, checked against the code.
SYLPHEED_KF_TIME_SHIFT was still live in FIVE doc files after I fixed one last
iteration. Two of the five were genuine hits rather than historical quotes:
ui-resting-pose.md -- a RESULTS TABLE ROW labelled "with
SYLPHEED_KF_TIME_SHIFT=1". Re-running it sets an inert variable, produces the
DEFAULT row, and lets a reader conclude the two readings agree. A stale
instruction inside a results table is the purest form of the evidence-
manufacturing class.
HANDOFF.md -- "experiment reachable via SYLPHEED_KF_TIME_SHIFT=1", a live
instruction in the delivery contract.
And a live gate exists under a DIFFERENT NAME that the docs never pointed at:
SYLPHEED_KF_TIME_LEGACY, verified read at ui_layout.rs:595 -- the parser itself,
not only the tests, so it does reach screen info and screen render. Both hits now
redirect there.
Beware the proxy, which is the trap the port named about their own "parsed"
check: absent-from-code also flags SYLPHEED_DISC, XENIA_SRC and SYLPH_ISO, which
are container paths the brief sets and no code reads. Absent-from-code is
necessary, not sufficient, and I checked each rather than reporting the seven raw
hits.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
70ee001327