refactor(exec,api): share mutation transactions and recovery - #1151
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Cypher statements and analyst property write-back now use one mutation transaction for the private catalog, rewrite staging, receipts, counters, commit, and recovery. The facade retains generation publication, while both entry points share authority-aware rollback and adjacency invalidation. Explicit multi-statement transactions use the same abort adapter after unpublished writes.
Recovery follows the actual selected generation after publication errors. Failed restoration retains its backup after owner drop and denies further use of the affected owner; retained streams check a recovery epoch before and after each pull. Absent targets preserve their empty snapshot contract, and substituted rollback-root links are rejected before touching outside files. Existing caller-specific catalog observation and counter semantics are preserved. ADR 0028 records the boundary; no durable or public result format changes.
Validation:
make pre-push-fastpassed. Exact-head CI remains required.Closes #1010
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.