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/reusing-code/SKILL.md

@@ -41,7 +41,7 @@ through recall/auto-inject; this skill is the active reflex around that.
   turn's shapes — reuse from memory leaves no such evidence.
 - If auto-inject already surfaced a snippet title that looks relevant, that's
   your cue to `get_snippet` it rather than start from scratch.
-- **Prior art offered beside a write is not noise — read it.** When Scribe notes
+- **Prior art offered beside a write is not noise — read it.** When Grimoire notes
   that a snippet is already recorded for the file you just wrote or edited, open
   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
@@ -59,7 +59,7 @@ through recall/auto-inject; this skill is the active reflex around that.
   YOUR edit's responsibility: if the edit changes the recorded shape,
   `update_snippet(id, code=…)` with the new form as part of the same task; if
   it doesn't, `verify_snippet(id, status="ok", commit_sha=…)` costs one call
-  and re-stamps the record as checked. Scribe never reads the repo — this
+  and re-stamps the record as checked. Grimoire never reads the repo — this
   moment, in the session that has the context, is the only place the record
   gets kept true.
 
@@ -115,7 +115,7 @@ shape is asked about once.
 
 ## A shared snippet is a suggestion, not a standard
 
-Scribe is multi-user, so a search can return snippets other people own. Those
+Grimoire is multi-user, so a search can return snippets other people own. Those
 come back marked `shared: true` with an `owner`.
 
 - Read one as **that person's suggestion**, not as the way things are done here.