Fixed: builds that ran over each other

A build that takes four and a half minutes reads as a build that has failed. So an owner on the free plan pressed the button again, and again, and again. All four attempts checked the account, all four saw "no websites yet, full credit balance" — because the first build hadn't finished writing either of those things yet — and all four went ahead.

They finished the afternoon with four websites on a one-website plan and their entire allowance spent in three minutes. Nothing was circumvented. The gap was reachable by ordinary impatience, which is what made it worth fixing properly.

One build at a time

Builds are now serialised per account: a second one can't start until the first has finished writing what it did. Every limit downstream is then reading a settled account rather than one mid-flight.

• If you start a build while one is running, we wait for it and pick up where it lands. The website finalizing page used to tell paying customers to contact support in that situation.
• The free website is once per account. A downgraded account could previously claim another one.

Builds that stalled repairing themselves

When a generated page had a syntax error, the fix was to ask the AI to write the entire page again — which, on a long page, didn't fit in the space available. It was cut off, the repair was thrown away, and the next attempt made the identical call and was cut off in the identical place. Three rounds of that could burn half the build's time budget and still ship a page that didn't compile.

Now a broken bracket is repaired by changing the broken lines, not by rewriting nine thousand tokens of page — and most of the common breakages are fixed mechanically, with no AI call at all. A file that still can't be salvaged is abandoned on its own instead of taking the build down with it.

Also fixed

• The weekly growth email could fail outright for accounts that had deleted a website, rather than skipping the missing one.