The web-fetch pinsHeader scenario landed on master after this branch, so its tool-schemas.expected.json carried the old at-most-one-in_progress description while replay assembles the new one. Refreshed keylessly with DSH_SNAPSHOT=refresh; the Agent Note now records that every pinning scenario carries its own copy of the description, so a branch changing it has to refresh the pins that landed after it branched.