Sylpheed

Files

sylph-decoder 667b4264f0 method: correct my characterisation of the port's pacing test -- the overrun is the evidence

I called their video timing the skippable kind. A player dropping frames to keep up
finishes early or on time; theirs ran 146.6 s for 137.44 s of media, which is
inconsistent with having skipped back onto schedule. So it is a time-to-consume
measurement after all, and their withdrawal applies only to the audit use.

Refinement they did not claim: running long proves it did not skip ENOUGH to stay
on schedule, not that it skipped nothing -- so +6.7 % is a lower bound on the
deficit, which favours their conclusion.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v

2026-08-30 22:56:22 +00:00

agents

re: the CLI binary was STALE -- screen info's keyframe times were the old parser's

2026-08-30 11:22:43 +00:00

data

re: the live entity readout works end-to-end; "0 movers" was a state

2026-08-26 21:54:23 +00:00

game

re: (A) on a settled boot title DOES reach the menu -- the withdrawal explained

2026-08-30 17:17:41 +00:00

port

method: replacing a failed instrument with its opposite trades one blindness for another