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>

docs/backups.md

@@ -1,7 +1,7 @@
 # Backups
 
-Scribe can back itself up every day to a **folder** or an **S3-compatible
-bucket**. Each run adds one file; Scribe never deletes an old one. Keeping and
+Grimoire can back itself up every day to a **folder** or an **S3-compatible
+bucket**. Each run adds one file; Grimoire never deletes an old one. Keeping and
 thinning the history is the destination's job.
 
 Set it up under **Settings → Data → Scheduled backups** (admins only).
@@ -16,14 +16,14 @@ scribe-20261015T020000Z.tar
 
 It is a plain, **uncompressed** tar:
 
-- `manifest.json` comes first. It holds the backup format version, the Scribe
+- `manifest.json` comes first. It holds the backup format version, the Grimoire
   version, when the backup was taken, and how many rows each table has.
 - Then there is one `<table>.jsonl` per table, one row per line.
 
 It holds everything the admin **Full Backup** download holds, laid out
 differently. It does **not** hold:
 
-- **Search indexes.** They are rebuilt from the records when Scribe starts.
+- **Search indexes.** They are rebuilt from the records when Grimoire starts.
 - **Sharing:** groups, project shares and note shares.
 - **Credentials:** API keys and forge connections. After a restore, issue new
   API keys and add forge connections again. (Forge tokens are also sealed under
@@ -61,7 +61,7 @@ file again.
 
 ### A folder
 
-A path **inside the Scribe container**, normally a share mounted there:
+A path **inside the Grimoire container**, normally a share mounted there:
 
 ```yaml
 services:
@@ -70,7 +70,7 @@ services:
       - /nfs/backup/scribe:/backups
 ```
 
-Scribe writes each file under a hidden name (`.scribe-….tar.part`) and renames
+Grimoire writes each file under a hidden name (`.scribe-….tar.part`) and renames
 it once it is complete. A program watching the folder never sees half a
 backup.
 
@@ -79,12 +79,12 @@ backup.
 You need four things:
 
 - **Address:** the service itself, like `https://backup.example.com`. Don't
-  include the bucket; Scribe addresses buckets by path.
+  include the bucket; Grimoire addresses buckets by path.
 - **Bucket.**
 - **Access key.**
 - **Secret key.**
 
-Scribe uploads and lists; it never deletes. A key that may **only add
+Grimoire uploads and lists; it never deletes. A key that may **only add
 objects** is therefore enough, and it is the safer key to hand out: a stolen
 one cannot wipe the history.
 
@@ -115,21 +115,21 @@ page asks for the secret again.
 [Fabled Archives](https://git.fabledsword.com/bvandeusen/fabledarchives)
 keeps service backups as "backup targets". Either destination works with it.
 
-1. On Archives' **Backups** page, make a target for Scribe, named `scribe`
+1. On Archives' **Backups** page, make a target for Grimoire, named `scribe`
    for example.
-2. Choose how Scribe's files arrive:
+2. Choose how Grimoire's files arrive:
    - **S3**: turn on the S3 way in for the target and make an **append-only**
-     S3 key. In Scribe, choose **An S3 bucket**:
+     S3 key. In Grimoire, choose **An S3 bucket**:
      - address: Archives' backup address (`http://<archives>:8081`);
      - bucket: the target's name;
      - access key and secret key: the key you just made.
-   - **A folder**: mount the share Archives watches into Scribe as
-     `/backups/scribe`, and point the target at that folder. In Scribe, choose
+   - **A folder**: mount the share Archives watches into Grimoire as
+     `/backups/scribe`, and point the target at that folder. In Grimoire, choose
      **A folder** with `/backups/scribe`.
 3. Set the target's **Retention** to **Archives**. Archives then keeps the
-   newest backups and thins the rest by day, week and month. Scribe only adds.
+   newest backups and thins the rest by day, week and month. Grimoire only adds.
 4. Give the target an expected cadence of **daily**, so a missed backup turns
-   it late in Archives as well as overdue in Scribe.
+   it late in Archives as well as overdue in Grimoire.
 5. Add an off-site **restic** replication job for the target. The uncompressed
    layout above is what lets that job send only what changed each day.
 
@@ -137,7 +137,7 @@ keeps service backups as "backup targets". Either destination works with it.
 
 ### Into a fresh instance
 
-Start Scribe on an empty database, copy the backup file into the container,
+Start Grimoire on an empty database, copy the backup file into the container,
 and run:
 
 ```sh
@@ -150,7 +150,7 @@ docker exec -it scribe python -m scribe.restore /backups/scribe-20261015T020000Z
 - Nothing limits the file's size.
 - It also reads the JSON from the admin **Full Backup** download.
 
-Afterwards, **restart Scribe** so the search indexes are rebuilt. Then issue
+Afterwards, **restart Grimoire** so the search indexes are rebuilt. Then issue
 new API keys, add forge connections again, and set up any sharing.
 
 ### From the web