build-log-overhaul
`/build-log` today is split across two routes (`/build-log` for the job index and `/build-log/status` for the live pipeline state) and presented as flat tables, bullet lists, and lightly-styled `<dl>` blocks. Every piece of data the TDD pipeline produces — current section, current agent, current stage, live worktrees with PIDs, completed sections with test counts and commit hashes, cross-section knowledge patterns, deferred follow-ups — surfaces somewhere, but the page has no narrative. A YouTube viewer landing cold has no idea what they're looking at; a technical reader has to ping-pong between routes to assemble a mental model. The page reads like a CI dashboard intended for the author, not a "show the work" content surface for a brand whose entire pitch is "AI agents are building this site in public."