feat: enforce configured whole-work budget envelopes (#56) #108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-56-work-budget-enforcement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Refs #56: COMPLETE active AC1-6, not a new specification-only slice. Owner-authorized normal /loop follows architecture/backlog acceptance #103. Prior PR94 remains specification-only with its consumed reviewordinal1 preserved.
Canonical PR metadata is exact current HEAD; base/merge-base
e2348656238a2ff9a3244868e2beb543d86f15a5, branchissue-56-work-budget-enforcement. Normal implementation/remediation commits only, no amend/force/rewrite. Each independent result is frozen to its own HEAD/base; prior findings/results and finite counters remain in issue receipts/excluded ledger, never reset.Functional Boundaries
e2348656and schema3 reader23a28e31 refuse4 before claim/effect/record mutation. Exact historical fixtures have CI history and no persisted credentials.Installed/reopen/crash/race/exhaustion/rollback, compound integrity, downgrade/backup, receipt, byte and review-budget regressions exercise actual paths. Ordinary dispatcher106, claims/fencing59 and drivers105 remain separate; ordinary-dispatch refusal retained. One configured SQLite owner is project authority, not cross-database quota or a second workflow engine.
Latest Validation
Closed/offline locked makecheck:1600passed,85existingnative-prerequisite skips,106subtests; all static/type/import/secret/diff gatesPASS. PackagecheckPASS including two real installed older readers and backup/artifact/revocation preservation. Focused42PASS; makeauditPASS no known vulnerabilities. Parent inspected full latest delta/newfiles and committed/pushed clean exact source normally.
85skips require pinned bubblewrap/OCI setups, not positive native/realCodex/live/isolation/billing evidence. No external repository mutation, paid/live inference, owner credentials/production state/realprofiles, deployment/release/main or security weakening.
Fresh complete whole-PR review and exact currentness remain required. No review result, merge permission or issue closure is inferred from implementation/check claims; finite review history persists across reentry.
STOP_REVISE — Do Not Merge
Final fresh native whole-PR review
ses_e82fa5df9ffergwywKo4CjS5Nj, conserved issue56ordinal10/10 (including prior PR94ordinal1), reviewed COMPLETE HEADd1d55d406923674c847b98a30756a05e87b52d2cagainst base/merge-basee2348656238a2ff9a3244868e2beb543d86f15a5: REQUEST_CHANGES.Remaining NEWP2:
ports/intake.py:703–707checks immutable work-envelope compatibility after durable approval/decision consumption and Program creation/amendment665–702. A changed expiry or incompatible project/task budget can refuse after changing the Program, stale its old binding and invalidate prior approval without returning ApprovedMeaning. Future remediation must prevalidate immutable original compatibility, keep original expiry and ensure atomic final approval/binding state; refusal regressions preserve old meaning/binding.Both final independent required makecheck/packagecheck gates passed; latest implementation1670tests/85explicitnativeprereqskips/106subtests and packagePASS. These passes are not approval. Prior specific findings were not repeated, but atomic validation/commit boundaries remain a recurring broader pattern. Full disposition/new-versus-recurring evidence is published in linked issue #56 and the preserved excluded ledger.
No exact APPROVE; finite10/10 exhausted. Entire /loop invocation is STOP_REVISE, not QUEUE_EMPTY. PR and issue stay OPEN, branch clean/pushed, all nine normal commits/history preserved. No more product patches or review dispatches, no counter reset, self-review substitution, force/auto/direct integration or silently skipping to another issue under this invocation. New explicit STOP_REVISE restart authority is required for further delivery; already accepted architecture/backlog does not need reconfirmation.
Canonical develop stays
e2348656; this PR's functional changes are NOT integrated or accepted. #103 architecture publication/delegated alignment acceptance and docPR107 integration remain complete. No external repository/production/main/release/deployment effects.Superseded Unmerged By Explicit Owner Recovery Mandate
Owner's direct 2026-10-27T15:34:28Z decision authorizes a distinct, materially revised persistence-boundary recovery for #56, identity
kernel56-atomic-approval-recovery-20261027T153428Z; issue receipt: #56 (comment).This PR's delivery remains STOP_REVISE, permanently 10/10 consumed, including original PR94 specification ordinal1 and functional PR108 ordinals2-10. Preserve all original native review results, nine normal commits and branch
issue-56-work-budget-enforcementatd1d55d406923674c847b98a30756a05e87b52d2c. It will be closed UNMERGED AS SUPERSEDED, never merged or given review11. This does not mark #56 complete.Replacement branch
issue-56-atomic-approval-recoveryretains this full ancestry and will add a genuine atomic approval/budget-persistence correction with comprehensive rollback/recovery tests. Replacement PR will receive its separately authorized maximum four fresh complete independent reviews, not a reset or extension of this counter. Replacement link will be appended after actual creation. No original history or branch will be deleted or rewritten.kilo referenced this pull request2026-10-27 16:22:17 +00:00
Replacement PR created: #109 #109, branch
issue-56-atomic-approval-recovery, HEAD76083c7a95abd8b3e801506a1e4f55b164328bab, basee2348656238a2ff9a3244868e2beb543d86f15a5. It retains originald1d55d4ancestry and all nine commits, and adds the substantive shared SQLite atomic acceptance boundary plus24regressions. Full primary makecheck1694PASS/85existingopt-in skips/106subtests and packagecheckPASS. New recovery0/4 before first fresh independent dispatch; this PR stays CLOSED/UNMERGED/STOP_REVISE, original10/10 unchanged.Pull request closed