You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Durable rental journal for provider release across daemon restart #4972
For a provider that supports reconciliation, persist its recoverable allocation key before a billable create. Record the exact provider instance and release intent before forgetting live ownership.
After registration on restart, restore the ending reservation before overlapping admission. Resume release by exact instance identity or resolve it when the provider proves absence.
If a provider cannot prove recovery, retain a fenced release unknown outcome for the operator.
Verification
Interrupt the daemon before identity arrives, after identity is recorded, and during release. Verify reconstruction of the reservation and release by exact identity. Verify that unknown release stays fenced.
Related work
Coordinate with ADR 0040 step 5 and the existing provider live and pending journals.
The issue specifies new required behavior for persisting and restoring provider rental identity across daemon restarts, with verification steps and related ADR links, rather than reporting an existing broken behavior.
Activity
apex-sentinel-staging commentedon Nov 22, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue specifies new required behavior for persisting and restoring provider rental identity across daemon restarts, with verification steps and related ADR links, rather than reporting an existing broken behavior.