rename(547): the server is grimoire — package, image, DB defaults, backups

Step 2 of the Scribe -> Grimoire rename.

- src/scribe -> src/grimoire, and every import, patch target, module path,
  hypercorn entry point and `python -m grimoire.restore` with it; pyproject,
  uv.lock and the frontend package are named grimoire.
- Image git.fabledsword.com/bvandeusen/fabledgrimoire; CI's Postgres service
  runs as grimoire / grimoire_test.
- Compose files default the DB user, database and (prod) volume to grimoire,
  each overridable from .env, so an install created as Scribe keeps its data
  by setting POSTGRES_USER, POSTGRES_DB and PGDATA_VOLUME.
- Backups are written as grimoire-<ts>.tar with format grimoire-backup-tar.
  Archives named scribe-* with the scribe-backup-tar manifest still restore
  and are still counted at the destination (folder and S3), with tests.
- Exports, the MCP auth realm, the ASGI scope key and the persistent logger
  carry the new name.

Kept on purpose: the secret-sealing key label stays "scribe.secrets.v1",
because every stored secret was derived under it.

Plugin identity (plugin name, hooks, env vars, .scribe marker, skills) is
step 3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

frontend/src/api/version.ts

@@ -2,7 +2,7 @@ import { apiGet } from "./client";
 
 /**
  * What `/api/version` answers — the client's half of `build_version_payload`
- * (`src/scribe/routes/api.py`), which is where the reasoning for the shape is
+ * (`src/grimoire/routes/api.py`), which is where the reasoning for the shape is
  * written down.
  *
  * EVERY FIELD BUT `version` IS OPTIONAL, and an absent one means "this build

frontend/src/components/BackupScheduleSettings.vue

@@ -187,7 +187,7 @@ async function backUpNow() {
       </ul>
 
       <p class="intro">
-        Each run adds one dated file, <code>scribe-&lt;date&gt;.tar</code>, holding every table
+        Each run adds one dated file, <code>grimoire-&lt;date&gt;.tar</code>, holding every table
         as plain lines. It is not compressed, so a deduplicating tool such as restic stores only what
         changed since the day before. Grimoire never deletes old backups — the destination keeps and
         thins the history. Sharing, API keys and forge connections are not included.
@@ -237,7 +237,7 @@ async function backUpNow() {
         </label>
         <label class="field">
           <span>Bucket</span>
-          <input v-model.trim="form.s3_bucket" class="fs-input" placeholder="scribe" />
+          <input v-model.trim="form.s3_bucket" class="fs-input" placeholder="grimoire" />
         </label>
         <label class="field">
           <span>Access key</span>

frontend/src/views/SettingsView.vue

@@ -1068,7 +1068,7 @@ async function exportData(scope: "user" | "full") {
     const blob = new Blob([JSON.stringify(data, null, 2)], { type: "application/json" });
     const a = document.createElement("a");
     a.href = URL.createObjectURL(blob);
-    a.download = `scribe-backup-${scope}-${new Date().toISOString().slice(0, 10)}.json`;
+    a.download = `grimoire-backup-${scope}-${new Date().toISOString().slice(0, 10)}.json`;
     a.click();
     URL.revokeObjectURL(a.href);
     toastStore.show("Backup downloaded");
@@ -1091,7 +1091,7 @@ async function exportNotes(format: "markdown" | "json") {
     const stamp = new Date().toISOString().slice(0, 10);
     const a = document.createElement("a");
     a.href = URL.createObjectURL(blob);
-    a.download = `scribe-${stamp}.${ext}`;
+    a.download = `grimoire-${stamp}.${ext}`;
     a.click();
     URL.revokeObjectURL(a.href);
     toastStore.show("Export downloaded");
@@ -1319,7 +1319,7 @@ async function handleRestoreFile(event: Event) {
     if (res.status === 413) {
       throw new Error(
         "the file is bigger than the web upload allows. Restore it with " +
-        "`python -m scribe.restore <file>` inside the Grimoire container instead.",
+        "`python -m grimoire.restore <file>` inside the Grimoire container instead.",
       );
     }
     if (!res.ok) {