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>

tests/test_preference_write_path.py

@@ -6,7 +6,7 @@ WHY TWO DOORS AT ALL
 propose, offer three answers, and wait. That is right for a rule — the person
 a rule binds should have agreed to be bound.
 
-A preference inverts it: it is a rule Scribe can and should update during
+A preference inverts it: it is a rule Grimoire can and should update during
 use. A preference that asks every time never drifts, and drifting is the whole feature. Reaching one through
 `create_rule(kind=..., when_to_apply="when the moment this fixture stands in for arises")` would mean reading it through the gate's prose, and
 the caller would hesitate over exactly the act this kind exists to make