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/writing-plans/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: writing-plans
-description: Use when a piece of work has an arc — several steps toward one goal, worth tracking as a unit — and you want the approach reviewable before you start. Triggers when the user asks you to plan, design an approach, or scope an effort, or when work is about to sprawl across several steps. Not for single-step work. The plan lives in a Scribe milestone (via start_planning), not a local file.
+description: Use when a piece of work has an arc — several steps toward one goal, worth tracking as a unit — and you want the approach reviewable before you start. Triggers when the user asks you to plan, design an approach, or scope an effort, or when work is about to sprawl across several steps. Not for single-step work. The plan lives in a Grimoire milestone (via start_planning), not a local file.
 metadata:
   moments: work.plan
 ---
@@ -56,7 +56,7 @@ the project has the same title or reads as the same plan, they return it as
 `existing_milestone` and create nothing. Add to that plan, or pass `force=true`
 only when you have read it and this really is separate work.
 
-## When it does: start the plan in Scribe, not a file
+## When it does: start the plan in Grimoire, not a file
 
 Call **`start_planning(project_id, title)`** before designing or implementing —
 so the milestone exists to write into, rather than being backfilled from work
@@ -78,7 +78,7 @@ rules. The plan lives in that milestone:
 **Never write an id you have not been given.** A plan body that says "see
 #4012" before #4012 exists is a guess, and other sessions and users are
 creating records from the same sequence at the same time — the number goes to
-whoever creates next, and the plan then points at their record. Scribe refuses
+whoever creates next, and the plan then points at their record. Grimoire refuses
 a body citing an id that has not been assigned. Where the plan and its steps
 need to cite each other, write a placeholder instead: `{{ref:N}}` is the Nth
 step in the list, `{{ref:milestone}}` is the milestone. They are replaced with
@@ -88,7 +88,7 @@ the real id and title as the records are created.
 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
+Before designing from scratch, **recall**: `search` Grimoire for a related prior
 decision or note. Often the thinking (or half of it) already exists.
 
 ## What a good plan contains