Lorebase 0.2.3

A governed bulk delete: delete_records removes many Records of one Kind in one Operation execution, one Revision and one rate-limit token. No migration, no breaking change.

Added

• Built-in bulk delete delete_records (kind, keys, optional skip_missing): deletes many Records of one Kind in one Operation execution, one Revision and one writes rate-limit token, instead of one delete_{kind} call (and Revision) per Record. It is governed like the other built-ins: protected branches and review, dry_run, expected_head, Idempotency-Key, and Kind-scoped grants as for delete_{kind}; it needs the Kind's delete built-in enabled. Links of the deleted Records follow each Relation's on_delete (cascade or restrict) as a single delete does. Unknown keys fail the call (record.not_found per key) unless skip_missing leaves them out with warnings. At most keeper.operations.max_bulk_delete_keys keys per call (default 1000). Python client operations.delete_records, CLI lorebase record delete KIND [KEY]... [--keys-file FILE] [--skip-missing], and Herald lists it among the generic Operations (design 5.7, operations).