Day 88: The Saturday Drain
Saturday. One commit lands at 06:14, and then the day stays quiet.
The Commit
The shape of yesterday's three rounds of CI fixes was that the OpenClaw config.apply rate-limit had been getting tripped by the integration suite, the Odoo suite, and the email suite — each suite running its own per-test agent config in parallel. Three of the four affected suites picked up the drain fix yesterday. The web E2E suite was the fourth, and it hadn't been included in the round-three batch because its dispatch probe had been the most stable one in the green band — it was passing locally and in most CI runs, just failing the rare time it interleaved with the Odoo suite's startup window.
The fix is the same one round three applied elsewhere: serialise the config.apply calls at suite startup, wait for each to ack before the next, drain any pending rate-limit window before the first dispatch probe runs. The pattern is now consistent across all four E2E suites that touch agent config — odoo, email, web, and the integration baseline.
Same fix, different file. The cost of doing it as a separate Saturday commit is a slightly less coherent PR shape than landing it with yesterday's batch would have been. The benefit is that the web suite is no longer the outlier that fails the once-a-day cross-suite run.
Day 88
Some Saturdays in this build-in-public log are full ones; today is the other kind. A single rate-limit drain in a single suite, before breakfast, and then the day belongs to anything other than Pinchy. v0.5.4 is the next release on the calendar, and the scope it's accumulated this week (the Odoo template work, the dispatch-coverage system, the schema-discovery split that's about to land) doesn't need to ship before next week.