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

@@ -12,7 +12,7 @@ real options and a reasoned choice — not a single path defended after the fact
 
 ## Recall first
 
-`search` Scribe before generating from scratch — a prior decision, note, or
+`search` Grimoire before generating from scratch — a prior decision, note, or
 brainstorm on this often already exists. Build on it instead of repeating it.
 
 ## Open up
@@ -30,7 +30,7 @@ brainstorm on this often already exists. Build on it instead of repeating it.
 
 ## Capture the decision
 
-When a direction is chosen, record it in Scribe (`create_note`, e.g. tag
+When a direction is chosen, record it in Grimoire (`create_note`, e.g. tag
 `decision`): the choice, the alternatives weighed, and the reason. That's what
 keeps the same question from being re-litigated later — and what a future
 session reads to understand *why*, not just *what*.