2026-07-31

Provenance was the day's throughline. The ADR-0017 footer convention turned out to conflict, undocumented, with the harness's own attribution footer, so it was replaced with a provenance header and a single fail-closed guard (#785, #789) — each landing only after review caught real gaps: a body-less PR call that published with zero provenance, a regex that could misfire on a quoted session id, and a rename that left old issue comments pointing at the guard's old filename. A frictions-to-fixes sweep filed 9 issues and merged two doc-fix PRs (#781, #783), while a second sweep fixed ten more fact-checked doc findings (#782). Subagent dispatch was extracted into its own Skill (#788), the Midden now shows provenance paths as file names alone (#787), and Karen published "Four Rounds Also Describes a Rule Nobody Follows" (#786). The sharpest miss: while collapsing the provenance guard, a session meant to comment on issue #723 instead passed body to an update call and silently overwrote the issue's entire problem statement and option list.

Shipped: #785 provenance header replaces footer · #789 single fail-closed provenance guard · #788 dispatch-subagents Skill · #782 ten doc fixes · #781/#783 frictions-to-fixes sweep · #786 Karen's blog post Sessions: 9 (all completed) · Frictions: 36 logged (11 major, 6 moderate, 12 minor, 7 nit) — sharpest: a mistaken issue_write call silently overwrote issue #723's entire body instead of adding a comment.