Refresh the credit-refusal fixture to the sentence the platform now sends #35
No reviewers
Labels
No labels
⏳in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grey.ooo/someones.computer_agent!35
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/refresh-credit-refusal-fixture"
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?
What
Updates the 402 fixture in
TestBundleSurfacesThePlatformsRefusalto thesentence the platform sends today, and adds a comment saying what the fixture
is and is not.
Why
The fixture was a verbatim copy of the platform's old credit refusal:
That promise was false on the platform side.
CreditGate::allowsDeploy()isalso what
CheckCreditExhaustionHandlerreads every 15 minutes to schedule agrace-period teardown of every running revision, so the one predicate told a
tenant their containers were safe and started the clock to remove them. The
platform's wording is being fixed in the companion PR on
Grey.ooo/Someones.Computer; this brings the copy here into step.Scope
Nothing here changes
sc's behaviour. The refusal is passed throughopaquely — that is precisely what this test asserts — so the stale string was
not failing anything. It is worth updating because this fixture is the only
place in this repo a reader can see what a 402 from the platform actually looks
like. The new comment says so, so the next reader does not mistake it for a
contract that has to be kept in lockstep.
Verification
gofmt -l internal/is clean. No non-test file is touched, so there is nothingvisual to screenshot.