Unify recurring allocation admission, custody and explanations - #374
Merged
adrianwebb merged 3 commits intoSep 17, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Unify recurring and manual workdays on canonical allocation admission, explicit custody and auditable explanations.
Work authority
Contributor mode (select one):
Plan
Repair the observed acceptance failure through the existing runtime path. Local verification complete; merge after required Actions, then verify managed local recovery. No tags or releases.
Changes and commits
7e629cb: Migration 0034 retains schedules as canonical intents and drops retired tier/budget columns. Scheduled starts delegate to the existing preflight/start with stable occurrence IDs and existing receipts. Persist SDK supply/selection explanations in existing allocation metadata; retain replayable agent selectors.
Verification
Build and file policies passed. 39 focused tests passed, including native PostgreSQL schedule migration. Exact protected SDK staging artifact: 5bf0a7bc3e9090f0885abb915101d33fe5d28df8, Verify 35188738580 success. Local development migration/rebuild in progress; no full golden lifecycle accepted.
Risk and rollback
Database migration 0034 requires drained workdays and coordinated application/database rollback. No credential migration. Restore compatible application/database state together; never run the retired writer against migrated schedules. No purge or bootstrap reinstall.
Completion summary
Bounded repair verified locally. Integrated golden lifecycles remain unproven and are not claimed as complete by this PR.
AGPL committer authorization
Base-owned workflow retains provider-authenticated author authorization.
Submission checklist