rename(547): what people read says Grimoire

Step 1 of the Scribe -> Grimoire rename: every capitalised "Scribe" in prose
becomes "Grimoire" ("Fabled Scribe" -> "Fabled Grimoire") across the UI,
the PWA manifest and page title, the MCP instructions and tool docstrings,
hook and skill text, docs and README, with the tests that assert on that
prose moving with it. Old migrations keep their wording.

Identifiers are untouched here: the package, plugin name, MCP server key,
hook file names, env vars, the .scribe marker and FabledScribe repo/image
names move in steps 2 and 3, along with prose that quotes them.

The sweep matched "Scribe" only as a whole word, so describe/subscribe and
friends are untouched. The longer name took the MCP instructions one
character over their 1,600 budget; two phrases are shortened to fit.

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

plugin/skills/reporting-back/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reporting-back
-description: Use when you are about to write the reply the operator will read and the delivered reply shape is not enough — work finished, stopping on a blocker, asking them to decide or to do something, answering "where are we", or proposing an approach. The long-form reference behind the reply shapes Scribe delivers: why sections are chosen rather than filled, who decides what, taking placement from the record, and a completion report worked in full. Triggers on reporting completion, handing off, asking a question, or summarising progress.
+description: Use when you are about to write the reply the operator will read and the delivered reply shape is not enough — work finished, stopping on a blocker, asking them to decide or to do something, answering "where are we", or proposing an approach. The long-form reference behind the reply shapes Grimoire delivers: why sections are chosen rather than filled, who decides what, taking placement from the record, and a completion report worked in full. Triggers on reporting completion, handing off, asking a question, or summarising progress.
 metadata:
   moments: reply.report
 ---
@@ -14,7 +14,7 @@ still unreadable to them. Shape it around **where the work stands**.
 
 ## The shapes arrive on their own
 
-Scribe delivers the default shape for each kind of reply as product, at the
+Grimoire delivers the default shape for each kind of reply as product, at the
 moment it is due: the core ("Reply shape · Every reply") with each turn, the
 completion report when a task closes, the asks when you put a question to the
 operator, the plan when you plan. A shape this session has already seen comes
@@ -61,7 +61,7 @@ and it costs the operator the decision twice.
 ## Take the placement from the record
 
 A remembered milestone title or "next step" reads exactly like a real one when
-it is wrong. So take placement from Scribe:
+it is wrong. So take placement from Grimoire:
 
 - `update_task` and `create_task` return a **`placement`** block — the project,
   the milestone, `position` (step N of M), `progress`, and `next` (the next open