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

@@ -1,6 +1,6 @@
 ---
 name: systematic-debugging
-description: Use when diagnosing a bug, failure, or unexpected behavior — investigate methodically instead of guessing. Triggers on "why is this failing/breaking", a stack trace, a flaky test, or any "it should work but doesn't". On resolution, capture the issue in Scribe so it isn't re-debugged from scratch.
+description: Use when diagnosing a bug, failure, or unexpected behavior — investigate methodically instead of guessing. Triggers on "why is this failing/breaking", a stack trace, a flaky test, or any "it should work but doesn't". On resolution, capture the issue in Grimoire so it isn't re-debugged from scratch.
 metadata:
   moments: work.debug
 ---
@@ -12,7 +12,7 @@ guessed fix that "seems to work" often just moves the bug somewhere else.
 
 ## Recall first
 
-Before digging in, `search` Scribe for the symptom — a prior issue
+Before digging in, `search` Grimoire for the symptom — a prior issue
 (`list_tasks(kind="issue")` or `search`) may already hold the cause and the fix.
 Don't re-debug what's already solved.
 
@@ -32,7 +32,7 @@ Don't re-debug what's already solved.
 
 ## Capture the issue (so it's findable)
 
-When resolved, record it in Scribe as its own issue (`create_task(kind="issue")`):
+When resolved, record it in Grimoire as its own issue (`create_task(kind="issue")`):
 **symptom → root cause → fix → how it was verified** in the body, optionally
 linked to the task it arose from (`arose_from_id`) and the subsystem it touches
 (`system_ids`). Even a problem fixed in passing is worth two lines — that's how