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_defs.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 # shellcheck shell=bash
-# Scribe plugin — the pieces the hooks share.
+# Grimoire plugin — the pieces the hooks share.
 #
 # scribe_prior_art.sh fires BEFORE a Write/Edit tool call; scribe_after_write.sh
 # fires AFTER a Bash tool call and diffs the working tree, so code written by
@@ -13,7 +13,7 @@
 #   scribe_defs                stdin code → "kind<TAB>name" per definition
 #   scribe_local_dups ROOT REL "kind<TAB>name" lines on stdin → the by-name
 #                              local-duplicate lines (ARM 1)
-#   scribe_unreached STATE SID SECS REL  the "Scribe didn't answer" line, once
+#   scribe_unreached STATE SID SECS REL  the "Grimoire didn't answer" line, once
 #                              per outage — or nothing, if said lately
 #   scribe_reached STATE SID   the server answered: the next outage speaks again
 #   scribe_config              sets `url` + `token` from the env, returns 0
@@ -500,12 +500,12 @@ scribe_defs() {
 # ---------------------------------------------------------------------------
 # ARM 1 — BY NAME, LOCALLY. Does a definition of this already exist?
 #
-# The recorded arms ask Scribe what was RECORDED; the ledger arm asks what a
+# The recorded arms ask Grimoire what was RECORDED; the ledger arm asks what a
 # BOUND repo's ledger knows. A helper nobody recorded, in a repo nobody bound,
 # is invisible to both, so it gets defined again in the next file. This arm asks the one question only the
 # developer's machine can answer, inside the repo, holding the code about to
 # be written: no index, no storage, no server — it runs even on an install
-# that has never configured Scribe.
+# that has never configured Grimoire.
 #
 # Definition-shaped patterns only. Grepping for bare occurrences would match
 # every CALL site and drown the real finding — and a hint that is mostly noise
@@ -852,7 +852,7 @@ scribe_local_dups() {
 # pass through a subshell's output, where it could land in a log or an `xtrace`
 # line. Returns 0 only when both are usable, so a caller can either bail
 # (`scribe_config || exit 0`) or carry on degraded — the session-context hook
-# still owes its static floor when Scribe is unconfigured.
+# still owes its static floor when Grimoire is unconfigured.
 # Declared here, not just assigned inside the function: `scribe_defs.sh` owns
 # these two names, and a sourcing hook should have them defined the moment it
 # sources — before any code path that might reference them. It also lets
@@ -890,7 +890,7 @@ scribe_unreached() {
     [ $((now - last)) -lt "$_SCRIBE_UNREACHED_QUIET" ] && return 0
   fi
   printf '%s' "$now" > "$marker" 2>/dev/null || true
-  printf '> Scribe did not answer the prior-art check for `%s` within %ss — this write went UNCHECKED against the record and the shape ledger (the local by-name arm, if it spoke above, needed no server). If the name matters, check it yourself: `search` for the concept, `list_shapes(project_id, path=…)` for the ledger. Said once per outage; if it keeps happening the instance is slow or down.' "$4" "$3"
+  printf '> Grimoire did not answer the prior-art check for `%s` within %ss — this write went UNCHECKED against the record and the shape ledger (the local by-name arm, if it spoke above, needed no server). If the name matters, check it yourself: `search` for the concept, `list_shapes(project_id, path=…)` for the ledger. Said once per outage; if it keeps happening the instance is slow or down.' "$4" "$3"
 }
 
 scribe_reached() {
@@ -1305,12 +1305,12 @@ scribe_turn_fact() {
 # The second key is a `.scribe` file in the directory (or above it, the way
 # git finds its root), naming the project the work belongs to. It is a
 # POINTER, not a copy: an id and enough to check the id means what it says.
-# Nothing Scribe should be holding goes in it.
+# Nothing Grimoire should be holding goes in it.
 #
 #   {"instance": "https://scribe.example.com", "project_id": 2,
 #    "project": "FabledScribe"}
 #
-#   instance    WHICH Scribe the id belongs to, and the reason this file is
+#   instance    WHICH Grimoire the id belongs to, and the reason this file is
 #               not just a number. A project id means nothing on its own: id 2
 #               is a different project on every instance, so a marker that
 #               travels — a copied directory, a shared machine, a repo someone