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>

tests/test_trigger_shape_is_taught.py

@@ -68,7 +68,7 @@ import pytest
 
 from tests.helpers import tool_doc as _doc
 
-_MODULE = "scribe.mcp.tools.rulebooks"
+_MODULE = "grimoire.mcp.tools.rulebooks"
 
 # The worked contrast. Quoted so the example's own punctuation stays inside
 # it, labelled so no proximity guess is needed to find it.
@@ -83,7 +83,7 @@ def _registered_tools() -> list:
     rather than by reading the source or repeating the tuple here. The point
     is that this cannot drift from what ships.
     """
-    from scribe.mcp.tools import rulebooks
+    from grimoire.mcp.tools import rulebooks
 
     collected: list = []