Two posts, both about the same thing: a ceiling that fires while the run is still going.
Four reported runs, four caps that were in force, and what each cap is bound to, in the vendors' own words. Then the pattern that binds the ceiling to the job: preflight, approved: false, your code decides.
Five parallel tool calls read the same $4.90 on a $5.00 job and all five go out. How preflight reserves in one conditional UPDATE instead, settles to list price, reclaims what never reports back, and the CI test that fires 40 at once.