test: pin budget-raise auto-clear on ingest #6

Merged
PerishFire merged 1 commit from test/budget-raise-autoclear into main 2026-07-14 11:22:32 +00:00
Owner

Regression coverage for the beta.49 production incident (stale context.budget.exceeded holds after a budget raise). Root cause: not a bug in the clear logic — ingest-remeasure clearing did not exist on beta.49 (built from 37dc008, where clear_context_incident was compact-only); the capability shipped with the workstream in beta.50. Test proves the held->raise->auto-clear path on the IM ingest route.

Regression coverage for the beta.49 production incident (stale context.budget.exceeded holds after a budget raise). Root cause: not a bug in the clear logic — ingest-remeasure clearing did not exist on beta.49 (built from 37dc008, where clear_context_incident was compact-only); the capability shipped with the workstream in beta.50. Test proves the held->raise->auto-clear path on the IM ingest route.
test: pin budget-raise auto-clear on ingest
All checks were successful
guard / guard (pull_request) Successful in 2m52s
19dac294ed
Models the beta.49 production incident: an IM strand held by
context.budget.exceeded, then a config raise + restart. On beta.49 the
hold needed break-glass SQL because ingest-remeasure clearing did not
exist there (clear_context_incident was reachable only from compact);
the capability arrived with the memory-pressure workstream and shipped
in beta.50. This test pins it: the next im_send after the raise must
auto-resolve the incident and be accepted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
PerishFire deleted branch test/budget-raise-autoclear 2026-07-14 11:22:32 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishFire/santi!6
No description provided.