soak

Overview ¶

Command soak drives the storage path at the capacity targets in docs/retention-policy.md and checks that the bounds it promises actually hold: rows stay under the per-endpoint ceiling, retention keeps up with the writers, the disk budget engages and can be left again, refused mutations are recorded, and the list screens stay fast while all of that runs.

It exercises the store rather than the agent socket. The question the M4 gate asks is about database and storage bounds, and a websocket per endpoint would measure the transport instead. What it cannot yet cover is named in the report rather than assumed.