The native pause-resume scenario failed with both old and new builds
because the harness could not reliably see an upload in flight. Pause
itself behaved correctly.
Client progress counts bytes handed to the socket, and the daemon writes
it to SQLite once per second. Loopback buffers absorb about 1-3 MiB of a
body (sometimes over 5 MiB on Linux), so a 4 MiB PUT read as 0 or as
complete in nearly every sample. The trigger fired on the 3rd or 4th PUT
at best, later or never under load, and never on Linux. With
FILE_CONCURRENCY=2 and PUT_CONCURRENCY=1, the file queued behind the
in-flight PUT is already dispatched and finishes too, so a late pause
left nothing paused.
The fixture now holds the first direct body after 64 KiB until the
harness has paused. pause-resume uses the 12 MiB default size, so a held
body still reads as partial. The scenario asserts that the held object
arrives intact and that every received object was reserved before the
pause. The daemon already follows the documented contract: pause stops
new dispatch and lets in-flight objects finish.
pause-resume: macOS arm64 10/10, Linux arm64 10/10 (old harness 0/5 on
Linux). Full native matrix on macOS: 26/26.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>