#3601 · #3587 · #3512 · #3178

Four skill docs that had drifted past the code

Each of these told a reader something that stopped being true. None is a behaviour bug, which is exactly why none of them surfaced: docs have no runtime, so nothing fails when they go stale.

issuefilewhat had drifted
#3601chain-patterns told sessions to PUSH state; CC 2.1.236 added a subscribe primitive
#3587review-pr two copies claimed backgrounding "since 2.1.218"; that was forks only
#3512dream hard rm on files not in git, and an unrotated index write
#3178doctor cited two issues as open work; both closed 2026-07-20

Before and after

was:


      

now:


      

The one that bit back

Documenting notify_when_idle failed CI. test-tool-call-signatures.sh carries a registry of allowed params per tool, stamped 2026-06-03, and it rejected the parameter as unknown. The registry was stale, not the doc: the live schema has carried notify_when_idle since CC 2.1.236. Fixing #3601 therefore meant fixing the gate that encoded the same outdated belief.

test-tool-call-signatures.sh
  registry stamped 2026-06-03
  SendMessage allowed: {to, message, summary}       stale
  SendMessage allowed: {to, message, summary,
                        notify_when_idle}           CC 2.1.236