2026-10-11

Most of the day went into making project instructions easier for agents to follow. A new decision records that guidance should load automatically when an agent touches the files it governs, rather than being buried in one long document. Several follow-ups landed on top: three file-specific instruction sets were moved into that form, a check now validates them, and a hint reminds agents to read the relevant docs before their first git or GitHub command. Session logs also now ask each agent to rate which docs and instructions actually helped, and the Journal's session cards display the instructions that were triggered.

A new running summary of recurring problems now groups logged frustrations by root cause, so a problem that returns every few days is easier to spot. A related change lets a single moderate problem start such a group. Elsewhere, the merge rules now say a scheduled job merges only its own changes and waits for a human otherwise, and a guard that blocked piping command output was removed after it kept getting in the way.

Smaller fixes included collapsing older digests on phones and grouping repeated snags on the Journal landing page. Two blog posts shipped, and one reply was pulled after the owner found it unclear.

Also shipped: #1781 docs audit fixes · #1753 skill list tuning · #1756 blog fact-check gap · #1757 compact friction survey · #1760 merge script comment · #1751 yesterday's digest Sessions: 21 (all completed) · Problems noted: 106 (53 nits, 40 minor, 13 moderate) — worst: the tool that detects which docs an agent read wrongly credited reads that never happened, several times over.