delete_all contract defines completion by acceptance-time emptiness, which remote passes cannot satisfy

api/openapi/v1.yaml defines delete_all completion as "finished once nothing from before the request remains" (line 3311) against "its own acceptance time" (line 3322), and lines 1061, 1199, and 1345 say delete_all "empties the collection". The spec refuses acceptance-time predicates for remote collections, and a remote cache re-fills continuously — so a caller building a poll-until-empty loop against a live remote cache never terminates.

The text is wrong the same way for all three formats, so a single-format edit would leave the document inconsistent in a new way. One follow-up fixes Maven, npm, and container together: define remote delete_all completion as one bounded pass over the rows the pass observes (ceil(N/page) batches), with re-cached rows surviving by design.

The exact lines are recorded in feat(managementapi): maven remote bulk pass (S1... (!1756 - merged) • Hayley Swimelar • 19.4's What section. The npm and container bulk passes (steps 32 and 33) inherit the same text.

Related to #314