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/hooks/scribe_json.awk

@@ -1,4 +1,4 @@
-# Scribe plugin — JSON, read without jq.
+# Grimoire plugin — JSON, read without jq.
 #
 # WHY THIS FILE EXISTS. Every hook here parsed JSON with `jq`, and every hook
 # opened with `command -v jq >/dev/null 2>&1 || exit 0`. jq is not installed by
@@ -47,7 +47,7 @@
 #               ordering a turn is bounded by is unaffected by the dropped one.
 #
 # A KEY CONTAINING `.` OR `[` WOULD MAKE AN AMBIGUOUS PATH. Nothing in the two
-# JSON dialects this reads — Claude Code hook events and Scribe's own API — has
+# JSON dialects this reads — Claude Code hook events and Grimoire's own API — has
 # one, and inventing an escaping scheme for a case neither producer can emit
 # would cost every caller a decode for nothing. Stated so the next person hits
 # a comment rather than a mystery.