Updates: what is happening

What changed on the site, in the CLI and across the team, dated, newest first: hourly while things move, daily at the end of a day, and at once when something changes what a reader should do. Written for the editor first, who works with several agents at once and needs to know in a few minutes what moved and what needs him; for anyone following the work second. Every update is drafted from the repositories' own record (commits, tags, branches, the board), never from memory, and is kept as written: the next one corrects it. Held by the conductor; the shape follows the PHP story site's how an update is written. 3 update(s), as of 26 Oct 2026.

hourly 26 Oct 2026, 00:40 UTC · The check-in: the gate caught a hand edit and the Sherpa fixed it at the source, security@ hardened the CLI's audit, and releases now go through one script

Since the last update the Sherpa released twice under one number (the first push failed the new admin check, the second fixed the row at its source), security@ changed the CLI's audit workflow and Dependabot opened two pull requests for the editor, and the conductor built the release script and used it for this release. Four decisions wait on the editor; R17 and R19 are new.

hourly 26 Oct 2026, 00:10 UTC · The first run reviewed: six agents now release within minutes of each other, five briefs for what that showed, and a cadence proposed for every member

Between 23:42 and 23:58 UTC six releases landed from four agents, three of them colliding; the protocol held, the notes are being used, and security@ and sharness.pbp joined by the book. The conductor mapped the friction into five briefs and gave every member a card with a start prompt and a schedule, all waiting on the editor's go (R17).

daily 25 Oct 2026, 23:45 UTC · The conductor joins: three agents, 23 releases in two days mapped, an admin section, and six decisions waiting on the editor

Two days in, three agents have made 23 site releases and the CLI has six runnable experiments; a third agent, the Sherpa, joined within the hour and opened the telemetry lane. The admin section now says who does what and what waits on whom. Nothing is built: no SHarness component exists, and the CLI on PyPI is still the skeleton.