Capture waits on nothing: a pending capture queue sends it to the cloud

Astra's second review showed the direct-to-server capture could forget
its strategy or make a second one, and it kept Capture waiting on the
network. Dara chose a client-only queue with no server change.

Each capture is now one versioned JSON record in its own Hive box, with
every id fixed when the moment is captured (strategy, pages, items, op
ids, client id). Capture returns once the record is written. The queue
sends captures of one strategy in order: createWithInitialPage, which
the server answers with the strategy it already has; then PageAddOp
under a fresh revision (a revision conflict resends under a new op id);
then the items. A lost answer resends the same ops; a refusal waits for
Retry, which gives what didn't land new op ids. A strategy deleted or
moved to another map fails its captures, and the next capture starts a
new one. The capture card, the library's cloud work card and the
sign-out check count captures still on their way or refused, and Open
waits until the page is in the cloud.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cfc9a2720fDara Adedeji committed on 10/13/2026, 9:20:10 PMparent9d0deab

Checks

6 successful · 8 skipped
All checks passed
14 files changedLine totals unavailable