@aiquants/auth-directory-drizzle 0.7.1 → 0.8.1

package/README.md

@@ -55,6 +55,13 @@ authorization admin UI uses. Removals are issued one at a time because `AdminRem
 descriptor; adding a batch form to the authorization core would breach the package boundary, and the
 count is already bounded by the reconciler's circuit breaker.
 
+**Every transaction goes through one seam.** All nine of them are opened by `transactionRunner` in
+`db.ts`, which runs the work again when — and only when — the server rolled it back
+(see [`@aiquants/mssql`](../mssql/README.md) — **only the deadlock victim `1205` is run again**, and the closure is wrapped in `capture` so the ORM cannot destroy that evidence). Calling `db.transaction` directly
+at each site means touching nine places to change the policy, and one of them eventually gets left
+behind without saying so. Configure with `transactionRetry` on any factory's options; the closure
+must keep its side effects inside the database, because a retry runs it from the start.
+
 **A refusal does not abort the run.** Stopping at the first refused removal leaves the additions
 committed, the earlier removals committed and the ledger untouched — and every later run recomputes
 the same plan and dies at the same index, so one legitimately-guarded row blocks the whole group's