Eleven tests were named "beyond the former ..." and pinned a value just above
a limit that no longer exists. Each now states and checks the current
contract:
- jsonShape: the caller's byte allowance is the only bound; a shape that fits
exactly is complete and one byte less is a capacity refusal.
- Hopper download: chunks arriving just inside the stall bound complete (the
trickle case already covers the total bound).
- Firmware: a selected analysis_timeout_ms above the default governs the owned
command, expressed from the default constant.
- Provider process output, CDP resources/timeline/WebMCP frames, Playwright
steps/artifacts/Electron waits, scenario diff and Bun ELF names: renamed to
the unbounded-count or exact-selection contract they check, with a note on
what bound (if any) still applies and where it is covered.
The six JavaScript analyzer tests with the same naming are left to their
workstream.
Refs #10515