A continuous-integration bill is not a speed problem. It is a counting problem — and almost every instinct you have about making builds cheaper is aimed at the wrong variable.
A spare laptop makes a fine always-on machine. The reason it keeps dying isn't the hardware. It's three power defaults written for a device someone carries, not one that lives on a shelf.
A database that accepts a hundred connections is not a database that does useful work on a hundred things at once. On a four-core box, throughput stopped scaling at four, and the fix was to stop counting connections and start counting cores.
Good images make a page look finished, but the wrong image can cost you a takedown notice or a license bill. This is the practical order: find free ones, confirm you're actually allowed to use them, make your own when nothing fits, and know when paying is the cheaper option.
A subsite whose mapped domain is parked looks deleted from every angle. The front end shows a parking page, the REST API returns nothing, and no URL you guess resolves. It isn't gone. Here's why it hides, and the thirty-second fix.
You change a few lines in a snippet, press Save, and get "Could not update snippet. Request failed with status code 403". Press Save on the unchanged snippet and it works. Your login is fine. Something between you and WordPress is reading the code itself.
Run the test by itself and it passes, every time. Run the whole suite in parallel and it fails, but only some days, and its failure looks exactly like a real bug. In our case the code was fine. The test was waiting on a clock.
You put a "create an account" link on one site of a WordPress multisite. Visitors who click it land on the main site, which either says "Registration has been disabled" or signs them up there instead.
Every feature arrives with its tests. Nobody times the hook. Then one day git push takes 25 minutes for a one-line change, and the suite is still running one test at a time on a 16-core machine.