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>
2026-10-22 10:46:37 -04:00
parent 06be537a18
commit e99f1169f7
142 changed files with 460 additions and 460 deletions
@@ -45,7 +45,7 @@ docker compose exec app alembic revision -m "short_description"

 `plugin/` ships straight from git: installs fetch it through `.claude-plugin/marketplace.json`, and there is no build step. After changing anything under `plugin/` or `.claude-plugin/`, run `make mint-plugin` before committing. Claude Code only refreshes an installed plugin when its version changes, and CI fails a plugin change that didn't bump it.

-The hooks must run on a bare machine: POSIX shell, awk, sed and the usual coreutils, plus `git` and `curl`. They fail open, so a slow or unreachable Scribe never blocks Claude Code.
+The hooks must run on a bare machine: POSIX shell, awk, sed and the usual coreutils, plus `git` and `curl`. They fail open, so a slow or unreachable Grimoire never blocks Claude Code.

 ## CI and releases