v0.30.1

Writes land in your own database. Connect a database with ablo connect and the models you already read become writable. ablo.<model>.create, .update, and .delete route through Ablo’s commit chokepoint and into your database — no connection string in the client. A claim you hold is checked at the chokepoint before the write applies, so agents and people take turns on a row whether they reach it by reading from Ablo or by writing back to your own database.

A write returns as soon as it is durably accepted; the receipt calls that queued. For the authoritative outcome, pass wait: 'confirmed'. Ablo watches the change actually land in your database — the write-ahead-log echo for a replicated source, the event feed for a signed endpoint — and promotes the receipt to confirmed before the call returns. The code is the same either way; only the feed Ablo waits on differs.
A clearer error when a table isn’t ready yet. ablo push records your models, but a plane’s physical tables are created separately, out of band — so a model can exist in the schema before its table does. Read or write one in that window and you now get a typed model_not_provisioned error (HTTP 409) that says what’s missing and how to fix it, instead of an opaque failure.