The two page schemes are two questions, not two readings of one

Eli, on the ambiguity refusal I had built: "no. let model decide which one to
use. these are separate things to call."

He is right, and the refusal was me inventing a problem. resolvePage now
resolves in ONE scheme chosen by the caller. Unqualified, digits are the PDF
page -- the scheme every PDF has -- and anything else ("iv", "A-3") can only
be a printed label; `pdf:` and `printed:` say so explicitly. The `ambiguous`
status is gone, and a miss now names which scheme it searched.

Also corrected, Eli again: "there can be printed page numbers even without a
table of contents. a ToC is just one way to navigate using printed page
numbers." The model-facing description had been written as though the printed
label existed to serve a contents page. It is the number ON THE SHEET, and it
is how the record gets cited -- a pinpoint in a brief, an index, an exhibit
stamp, a transcript. A contents page is one consumer among several, and
teaching the model otherwise would have narrowed when it reaches for it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H9ToHYJVDxfeJcJwdzrP2H