[Bikebrainz]

The CLI treated a documented history ID as a row index, which could load a different request. Its asynchronous send loop also exited under set -e on the first i++, and refused or unfinished sends could produce an old response.

repeater load now uses the stable-ID endpoint and reports invalid/missing IDs as errors. repeater send polls until completion within its bounded wait and fails explicitly on refusal or exhaustion. repeater stop uses the existing stop-after-current-response API.

The website and developer changelogs are updated. The roadmap corrects stale claims about binary request loading, blocking sends, missing editor views, gzip/deflate display and leaf-key permissions. It explicitly records the reproduced binary-response Hex gap and the remaining immediate-cancellation limit.

Validation:

• The original CLI fails the new history-ID contract and exits with no output during the asynchronous-send regression.
• Local CLI contracts pass: stable IDs, missing rows, invalid input, multiple pending polls, refused sends, wait exhaustion and Stop.
• Real app test passes: ID 1 selects the first of two captured requests and sends its complete 70 KB binary body; ID 2 selects the second; a missing ID leaves the draft unchanged.
• Existing notes/Intruder CLI contracts and Bash syntax pass.
• New contract tests run in CLI CI; the real-app test runs against the installed Linux app.
• Website checks pass: 81 Markdown targets, 3 integrity hashes and 117 pages. Roadmap generation remains synchronized.

All eight cross-platform CI jobs passed on final head 4d1fd68eec4ea4278d40325aa7bd82b4e6a4c516 (run 36540909858).