v0.12.14: @newsroom.wire: the wire's release notes and corrections, and two more wires, each from its own vault

Two releases built on the session branch this morning as v0.12.10 and v0.12.11, while @newsroom.ux released v0.12.10 to v0.12.13 on dev; merged onto v0.12.13 as one release, with the wire's new colours moved to the themes' tokens.

The wire's vault publishes its release notes, and corrections propagate to the story (026, 039). The Industry Wire's desk published its second edition on 13 October (release 2026-10-13.1): nineteen new stories since the first edition, thirteen stories of 11 October corrected after their primary sources were fetched, and, as the brief of v0.12.6 asked, a release file (data/releases.json, wire-releases/v1) with one entry per publish, the commit message starting with the release id, and the step written into the vault's own runbook. The page had shown the release notes since v0.12.6; card 026 closes and the wire test pins them. What the page did not show was the corrections themselves: now each corrected story carries its changes, dated, as the vault records them, the edition's header carries the desk's corrections note, and a story from an earlier edition says so. The snapshot carries the same, and the desk's latest release note.

More than one wire (040). The research agent built two more vaults on the Industry Wire's pipeline, and the owner relayed its brief: read them at /wire/owasp/ and /wire/aws/, under the same contract, with the named reader as before. One code and one builder now serve every wire, each from its own config. The pages draw what a vault adds beyond the edition: a map as entities with the stories that name them, a stack as the deadlines in the header and each service with the items that touched it. Each wire keeps its own inbox, visit and lens in the browser, and a story id shared by two vaults is kept apart. The design is admin/notes/2026-10-13__more-than-one-wire.md.

Found on the way: the desk's release note and the personal brief both say the reader's lane was not read, so the five decisions the reader sent are not reflected (card 030 carries the note: the lane's read key has not reached the wire's agent).