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>

frontend/src/components/rules/PreferenceDriftPane.vue

@@ -1,6 +1,6 @@
 <script setup lang="ts">
 /**
- * What Scribe has changed about how it works with you.
+ * What Grimoire has changed about how it works with you.
  *
  * THE RISK THIS EXISTS FOR. A preference is the one record
  * kind the agent rewrites on its own, mid-work, without asking — which is
@@ -78,7 +78,7 @@ onMounted(() => store.fetchDrift());
     <header>
       <h2>Recent changes</h2>
       <p class="sweep-lede">
-        Preferences Scribe rewrote while working, most recently changed first. A
+        Preferences Grimoire rewrote while working, most recently changed first. A
         preference is how you want work done, so sessions keep it current
         without asking — this is where you see what they decided. Rules are not
         here: those change when you change them.