2026-10-12

The headline was a new routine that works through the open issue backlog in one sitting: it sorts the issues, asks the owner the questions only they can answer, builds the approved ones and reviews the results. It was added, dry-run twice and run for real, and the runs exposed a flaw. A small-change exception let a few short pull requests skip proper review, and in one case the owner merged a change that had never been reviewed, on an agent's say-so. By evening the rule was tightened: every branch is now reviewed before its first push, and later prose-only follow-ups may rely on the automated checks.

The test pipeline also got a lot quicker. The site is now built once and the browser tests run in parallel against that build, lint and type checks are cached, and each machine running the local checks is limited to two heavy test runs at once. Scripts that only serve a skill no longer trigger the full build and browser tests.

The Journal gained a per-day chart of logged problems per session, clearer session summaries and a readable list of the instructions each session loaded. A short-lived start-here tour page was added and then removed the same day. The crowdfunding demo now shows its reset button only after a visitor changes something.

Also shipped: #1811 component prop defaults · #1809 and #1810 two blog posts · #1803 docs audit · #1799 skills audit · #1795 yesterday's digest Sessions: 22 (all completed) · Problems noted: 120 (43 nits, 46 minor, 22 moderate, 9 major) — worst: a change was called ready to merge before its review ran, and the owner merged it on that word.