docs(self-surfacing): derive groups are drift not audit material — shape-accounting + reusing-code skills, static floor, plugin README (after-write hook), api-reference rows (#2902, milestone 299 step 4)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-22 13:38:06 -04:00
parent b88225eeb3
commit 10687120a5
5 changed files with 52 additions and 2 deletions
@@ -44,6 +44,13 @@ through recall/auto-inject; this skill is the active reflex around that.
  it before you go any further. Either it's the helper you were about to
  duplicate — reuse it and drop yours — or it isn't, and the record needs the new
  location adding. Both are cheaper now than after the duplicate settles in.
+- **A `Shape ledger at …` line is the ledger speaking, not the record.** It
+  names a duplicate family ("identical body in N other files, no canon") or a
+  canon elsewhere for a name you just wrote — for edits made through Bash
+  (sed, heredocs, scripts) as much as through Write/Edit. Derive the family or
+  reuse the canon *now*; a family that is convention rather than copies is
+  dismissed with `classify_shapes(..., status="exempt",
+  reason_code="convention-plumbing")`, never ignored.
 - **A `[records this file]` hint is a duty, not a menu.** When the hint says a
  snippet records the very file you're editing, the record's freshness is now
  YOUR edit's responsibility: if the edit changes the recorded shape,