The line was printed on the way INTO a re-read, so an install with
`retry_degraded` off -- or on "auto" behind `fallback_engines: off`, which is
the same thing -- produced no record anywhere of a degraded page. The engine
answers 200, nothing raises, and the only other copy of the finding is in the
reply, which belongs to the client: a batch could come out almost entirely
truncated and leave the server log looking like a clean run. That is how ~97%
of one run went unnoticed.

Finding a ruined page is now separate from being able to fix it, and when the
chain is empty the log says so and names the setting that emptied it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S8LAP3ueNzQJtwzhgVbq66