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/README.md

@@ -1,44 +1,44 @@
-# Scribe plugin for Claude Code
+# Grimoire plugin for Claude Code
 
-Turns a self-hosted [Scribe](https://git.fabledsword.com/bvandeusen/FabledScribe)
+Turns a self-hosted [Grimoire](https://git.fabledsword.com/bvandeusen/FabledScribe)
 instance into a first-class Claude Code extension:
 
 - **MCP tools** over your notes, tasks, projects, milestones, systems, and
   rulebook (the `scribe` server).
 - **Session-start push channel** — a `SessionStart` hook injects the
   active project's live state (from the server) and this adapter's short
-  Claude Code guidance, so Scribe surfaces *without being asked*. Rules are
+  Claude Code guidance, so Grimoire surfaces *without being asked*. Rules are
   never preloaded; they arrive by retrieval when your work matches one.
 - **Prior-art recall on writes** — a `PreToolUse` hook on Write/Edit checks the
   file about to be written against your recorded snippets (what's kept at that
   path, and what resembles the code) and offers them before the helper is
   rewritten. Titles only, never blocks the edit.
-- **The shared Scribe skills** — client-neutral Agent Skills, the same files
+- **The shared Grimoire skills** — client-neutral Agent Skills, the same files
   any client's package would ship: using-scribe, writing-plans, reporting-back
   (reply to the operator in a shape that says where the work stands),
   systematic-debugging, verification, brainstorming, reusing-code (record and
   recall reusable code as snippets), shape-accounting and family-canon.
   Replaces superpowers.
-- **Your Scribe Processes as skills** — saved Processes are synced into local
+- **Your Grimoire Processes as skills** — saved Processes are synced into local
   `~/.claude/skills/scribe-proc-*` stubs that auto-surface by relevance; the
   stub fetches the live procedure via `get_process`. Refreshed each session and
   on demand with `/scribe:sync`.
 
-It is designed so you can uninstall `superpowers` and depend on Scribe instead
-of auto-memory — leave auto-memory at its default; Scribe replaces its job by
+It is designed so you can uninstall `superpowers` and depend on Grimoire instead
+of auto-memory — leave auto-memory at its default; Grimoire replaces its job by
 holding the one copy, not by switching it off.
 
-**How the pieces divide the work**: the Scribe server orients
+**How the pieces divide the work**: the Grimoire server orients
 every MCP client and serves live state; the skills in `skills/` state every
 reflex in full and name no client; this plugin is the Claude Code adapter —
 hooks that deliver at the right moment, `/scribe:sync`, and the few things only
-Claude Code needs said (`hooks/scribe_static_context.md`). Packaging Scribe for
+Claude Code needs said (`hooks/scribe_static_context.md`). Packaging Grimoire for
 another client: see [PACKAGING.md](PACKAGING.md).
 
 ## Install
 
-The plugin ships inside the Scribe app repo, so the marketplace *is* that repo —
-you always get the plugin version that matches your Scribe instance.
+The plugin ships inside the Grimoire app repo, so the marketplace *is* that repo —
+you always get the plugin version that matches your Grimoire instance.
 
 ```
 /plugin marketplace add https://git.fabledsword.com/bvandeusen/FabledScribe.git
@@ -49,15 +49,15 @@ On install you'll be asked for:
 
 | Setting | What |
 |---|---|
-| **Scribe base URL** | e.g. `https://scribe.example.com` (no trailing slash) |
-| **Scribe API key** | a write-scoped `fmcp_` key from **Settings → MCP Access** (stored in your OS keychain) |
+| **Grimoire base URL** | e.g. `https://scribe.example.com` (no trailing slash) |
+| **Grimoire API key** | a write-scoped `fmcp_` key from **Settings → MCP Access** (stored in your OS keychain) |
 | **Active project id** | optional — numeric project id to scope the session-start context |
 
 ## What gets wired
 
 - `plugin.json` `mcpServers` → the `scribe` MCP server at `<base URL>/mcp` (Bearer auth).
 - `hooks/hooks.json` → SessionStart hook (`hooks/scribe_session_context.sh`),
-  **fail-open**: if Scribe is unreachable it injects nothing and never blocks
+  **fail-open**: if Grimoire is unreachable it injects nothing and never blocks
   the session.
 - `hooks/hooks.json` → PreToolUse hook on `Write|Edit`
   (`hooks/scribe_prior_art.sh`) → `GET /api/plugin/prior-art`. Returns
@@ -69,7 +69,7 @@ On install you'll be asked for:
   line names a duplicate family (no canon) or a canon recorded elsewhere for
   the names being written (its own dedup channel, `exclude_derive`).
   Fail-open but not fail-silent: a configured instance that does not answer
-  in time is said, once per outage ("Scribe did not answer … this write went
+  in time is said, once per outage ("Grimoire did not answer … this write went
   UNCHECKED"), so a session can tell "checked, nothing there" from "never
   checked"; an answer clears the marker. The local by-name arm needs no
   server and always runs. Toggle in **Settings → General → Knowledge
@@ -82,9 +82,9 @@ On install you'll be asked for:
 - `hooks/hooks.json` → PreToolUse hook on every tool (`hooks/scribe_moment.sh`)
   → `POST /api/plugin/moment`: the rules mounted on the moments the call
   reaches. It skips tools that `GET /api/plugin/moment-tools` says reach
-  nothing mounted, and Scribe's own tools, whose responses carry
+  nothing mounted, and Grimoire's own tools, whose responses carry
   `moment_rules`.
-- `hooks/hooks.json` → PostToolUse hooks on Scribe's `get_rule`,
+- `hooks/hooks.json` → PostToolUse hooks on Grimoire's `get_rule`,
   `rule_outcome`, `update_task` and `add_task_log`: they keep the session's
   ledgers of rules opened and acted on (`get_rule` also reports to
   `POST /api/plugin/rule-opened`), and claim the task being worked
@@ -102,7 +102,7 @@ On install you'll be asked for:
 - `hooks/hooks.json` → Stop hook (`hooks/scribe_reply_check.sh`): sends the
   reply that ends the turn to `POST /api/plugin/reply-rules`, which holds it
   once for an unopened rule mounted on the reply moments or matching the reply.
-  When the turn closed a Scribe task (`update_task`/`create_task` with status
+  When the turn closed a Grimoire task (`update_task`/`create_task` with status
   done), the same request has the server check the reply for the completion
   sections — where the work sits, what needs you, what comes next. If they are
   missing it blocks once with the reason the server returns, and records how
@@ -120,9 +120,9 @@ On install you'll be asked for:
   land under category `plugin`, action `shape_check`.
 - `skills/` → the universal process-skills, surfaced by description match.
 - `hooks/scribe_sync_processes.sh` (a 2nd SessionStart hook) + the `/scribe:sync`
-  command → generate `~/.claude/skills/scribe-proc-*` stubs from your Scribe
+  command → generate `~/.claude/skills/scribe-proc-*` stubs from your Grimoire
   Processes (via `GET /api/plugin/processes`); also **fail-open**, and pruned to
-  match what exists in Scribe.
+  match what exists in Grimoire.
 - `hooks/hooks.json` → PreCompact hook (`hooks/scribe_precompact_preserve.sh`):
   tells the summarizer which parts of the conversation to keep literally. Local
   only, and it never blocks, because a blocked compaction is skipped outright.