Refresh the credit-refusal fixture to the sentence the platform now sends #35

Merged
geusebio merged 1 commit from chore/refresh-credit-refusal-fixture into main 2026-08-22 14:46:16 +00:00
Owner

What

Updates the 402 fixture in TestBundleSurfacesThePlatformsRefusal to the
sentence 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:

Deploying is paused: Acme has a credit balance of $0.00. Anything already
running stays up. Top up at … to deploy again.

That promise was false on the platform side. CreditGate::allowsDeploy() is
also what CheckCreditExhaustionHandler reads every 15 minutes to schedule a
grace-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 through
opaquely — 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

GOWORK=off go test ./internal/upload/
ok  git.grey.ooo/Grey.ooo/someones.computer_agent/internal/upload  0.282s

gofmt -l internal/ is clean. No non-test file is touched, so there is nothing
visual to screenshot.

## What Updates the 402 fixture in `TestBundleSurfacesThePlatformsRefusal` to the sentence 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: ```text Deploying is paused: Acme has a credit balance of $0.00. Anything already running stays up. Top up at … to deploy again. ``` That promise was false on the platform side. `CreditGate::allowsDeploy()` is also what `CheckCreditExhaustionHandler` reads every 15 minutes to schedule a grace-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 through opaquely — 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 ```text GOWORK=off go test ./internal/upload/ ok git.grey.ooo/Grey.ooo/someones.computer_agent/internal/upload 0.282s ``` `gofmt -l internal/` is clean. No non-test file is touched, so there is nothing visual to screenshot.
Refresh the credit-refusal fixture to the sentence the platform now sends
All checks were successful
CI / build (pull_request) Successful in 2m9s
c71e258845
The 402 body in TestBundleSurfacesThePlatformsRefusal was a verbatim copy of
the platform's old refusal, which promised "Anything already running stays up".
That promise was untrue on the platform side — the same predicate that produced
it also scheduled a grace-period teardown of every running revision — and has
been rewritten there to say what actually happens.

sc asserts nothing about the wording; the sentence is passed through opaquely,
which is what the test exists to prove, so the stale copy was not failing. It is
updated because this fixture is the only place in this repo a reader can see
what a 402 from the platform looks like, and a fixture that lies about that is
worse than no example. A comment now says so, to stop the next reader treating
it as a contract they have to keep in step.
geusebio deleted branch chore/refresh-credit-refusal-fixture 2026-08-22 14:46:18 +00:00
Sign in to join this conversation.
No reviewers
No labels
in-progress
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
Grey.ooo/someones.computer_agent!35
No description provided.