The bake-off table said what to measure and against which pass bars, but not how to get there: what has to exist before labelling starts, how the three labelled sets are built, and which engine behaviours the scoring has to account for. Two of those behaviours came out of the first measured run and change the numbers if ignored. Typed extraction fabricated nested fields, so invented values count as errors rather than only missed ones. Answers carry over between unrelated calls on a reused engine instance, so a harness that does not reset between items reports better results than a cold one. The labelled data stays outside the repo: it is a week of personal browsing, and the repo is treated as public.