docs(6204): shipped instruction text describes the product, not this instance's records

MCP tool docstrings and comments, the server's orientation notes, the plugin
skills, every hook script and the plugin README/PACKAGING drop record ids,
milestone numbers, dates and incident stories, and state each non-obvious why
as a present-tense fact. History stays in the task logs.

Corrections found on the way:
- plugin README/PACKAGING said every hook is a GET; moment, rule-opened and
  reply-rules POST, so the plugin's key needs write scope. Both now say so,
  name Settings -> MCP Access, and list every wired hook and endpoint.
- the contract-change hint printed "(lesson #4207)", this instance's record,
  to every install. It no longer cites a record.
- tasks.py claimed there is no delete_task; there is.
- rulebooks.py cited delete_event and a design spec that no longer exist.
- scribe_after_write.sh carried an always-empty etag_q; removed.
- test_write_path_trigger pinned "| tac | scribe_defs | head -1", text that
  existed only in a comment about the old code; it now pins the real tail -1
  pipeline.
- docs/development.md: CI runs on Gitea Actions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugin/skills/shape-accounting/SKILL.md

@@ -100,8 +100,7 @@ from the derivation, not from asking permission.
 ## Derive groups are drift, not audit material
 
 The catalogue exists so the codebase is DRY **from inception**, not as DRY as
-the last sweep left it. Three surfaces say so without anyone running an audit
-(milestone 299):
+the last sweep left it. Three surfaces say so without anyone running an audit:
 
 - **At the write** — the prior-art hint (delivered beside a write where your
   client supports it; shell edits count as much as editor writes)
@@ -122,7 +121,7 @@ the last sweep left it. Three surfaces say so without anyone running an audit
   reason_code="convention-plumbing", reason=…)` (or `classify_shapes_by_rule`
   for a whole family) removes it from the queue. Dismissal is a judgment and
   it is recorded; silence is not.
-- **CSS is watched by name, never by body** (note 2917). Classes serving
+- **CSS is watched by name, never by body.** Classes serving
   different purposes share declarations because the style system makes them
   alike — `.text-muted` and `.pin-badge-auto` carrying the same `color:` are
   two meanings, not two copies — so a CSS family is the *same class defined
@@ -132,7 +131,7 @@ the last sweep left it. Three surfaces say so without anyone running an audit
   genuinely different things is dismissed with `reason_code="scoped-css"`.
   The datum that decides between the two is **what renders it**: every css
   row carries `used_by` (the files whose markup names the class — the CSS
-  consumer map, milestone 302), a derive group carries the family's
+  consumer map), a derive group carries the family's
   `consumers`, and the write-path line says "used by N template(s)". Many
   templates, one recipe → derive; one template each, different purposes →
   dismiss. `list_shapes(flag="unused-css")` is the map's negative space —
@@ -148,7 +147,7 @@ afterwards is drift of the moment, and the hint already said so at the write.
 
 ## The divergence readout — button B where button A is canon
 
-Three questions the ledger answers mechanically (#2793):
+Three questions the ledger answers mechanically:
 
 - **Divergence** — `list_shapes(project_id, flag="divergence")` (and the
   coverage line's "N DIVERGENT"): a shape new since the previous refresh, in
@@ -166,7 +165,7 @@ Three questions the ledger answers mechanically (#2793):
   re-confirm it (classify again with the same status) or re-judge.
 - **Weak stamps** — the coverage line's "N weak stamps … to judge —
   stamps_to_review": rows the write-path hook asserted, unattended, on a
-  resemblance below today's floor. They no longer elect a directory's canon
+  resemblance below the current floor. They do not elect a directory's canon
   or raise a divergence, but they still claim to be instances. Read each
   one and record the verdict with `classify_shapes` — `instance` if it is,
   otherwise what it actually is.

plugin/skills/writing-plans/SKILL.md

@@ -85,8 +85,8 @@ step in the list, `{{ref:milestone}}` is the milestone. They are replaced with
 the real id and title as the records are created.
 
 **Do not** write plans or specs to local `.md` files — the milestone is the
-record, not a file on disk. (The old `kind=plan` task is retired; `start_planning`
-no longer creates one.)
+record, not a file on disk. A plan is never a task: `kind="plan"` is refused,
+and `start_planning` makes a milestone.
 
 Before designing from scratch, **recall**: `search` Scribe for a related prior
 decision or note. Often the thinking (or half of it) already exists.