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>

docs/api-keys-and-mcp.md

@@ -35,7 +35,7 @@ Click **Revoke** next to the key in the keys table and confirm. Revoked keys are
 Grimoire exposes itself as a set of MCP tools that Claude (and other MCP clients)
 can use to read and write your notes, tasks, projects, rulebooks, and more. The
 server is **built into the app** — it is mounted as a streamable-HTTP endpoint
-at **`/mcp`** on the running Grimoire instance (`src/scribe/mcp/server.py`). There
+at **`/mcp`** on the running Grimoire instance (`src/grimoire/mcp/server.py`). There
 is nothing to install: no wheel, no separate package, no CLI. You connect a
 client straight to the URL with a Bearer token.
 
@@ -90,7 +90,7 @@ specific project at a dev instance or an admin key.
 ### Available Tools
 
 There are well over a hundred tools and they change with the app, so the
-registration in **`src/scribe/mcp/tools/`** is the reference. By family:
+registration in **`src/grimoire/mcp/tools/`** is the reference. By family:
 
 | Family | Examples | Purpose |
 |--------|----------|---------|
@@ -111,4 +111,4 @@ registration in **`src/scribe/mcp/tools/`** is the reference. By family:
 Server-level usage guidance — when to reach for each entity, the
 recall-before-acting reflex, and the rulebook conventions — is delivered to the
 client automatically via the MCP server's `instructions` block (defined in
-`src/scribe/mcp/server.py`).
+`src/grimoire/mcp/server.py`).

docs/api-reference.md

@@ -294,7 +294,7 @@ These serve the plugin's hooks.
 ## Grimoire MCP
 
 Claude clients connect to the built-in MCP server at `POST /mcp` (streamable HTTP,
-Bearer auth with an `fmcp_` key), served by `src/scribe/mcp/`. It is not a REST
+Bearer auth with an `fmcp_` key), served by `src/grimoire/mcp/`. It is not a REST
 surface — it exposes the same data as typed tools (`create_note`, `create_task`,
 `start_planning`, `search`, `enter_project`, …) with
 server-level usage guidance delivered in the MCP `instructions` block. See

docs/architecture.md

@@ -24,10 +24,10 @@ Grimoire is one app container and one PostgreSQL container. There is no language
 ```
 
 - **The web UI** is a Vue single-page app, built into the image and served by Quart. Every unknown path that isn't under `/api/` falls back to `index.html`; `/api/*` always answers JSON.
-- **The REST API** (`src/scribe/routes/`) backs the UI, one blueprint per resource.
-- **The MCP server** (`src/scribe/mcp/`) is how Claude reads and writes records. Each module in `mcp/tools/` registers its tools, and the server's instructions and each tool's docstring are the contract an agent reads. Requests authenticate with an API key as a Bearer token.
+- **The REST API** (`src/grimoire/routes/`) backs the UI, one blueprint per resource.
+- **The MCP server** (`src/grimoire/mcp/`) is how Claude reads and writes records. Each module in `mcp/tools/` registers its tools, and the server's instructions and each tool's docstring are the contract an agent reads. Requests authenticate with an API key as a Bearer token.
 - **The plugin** (`plugin/`) runs in the user's Claude Code. Its hooks call `/api/plugin/*` to put the right context in front of Claude at the right moment: the project at session start, matching rules and prior art before a prompt or a tool call, the rules mounted on a moment of work, and a check on the reply that ends a turn. Its skills describe the working practices. See [API Keys & MCP](api-keys-and-mcp.md) to install it.
-- **Services** (`src/scribe/services/`) hold the logic both doors share. Routes and MCP tools stay thin: parse the request, check access, call a service, return a plain dict.
+- **Services** (`src/grimoire/services/`) hold the logic both doors share. Routes and MCP tools stay thin: parse the request, check access, call a service, return a plain dict.
 
 ## Data model
 
@@ -80,14 +80,14 @@ Credentials Grimoire stores for outside services (forge tokens, the backup desti
 
 ```
 ├── alembic/versions/      database migrations
-├── src/scribe/
+├── src/grimoire/
 │   ├── app.py             app factory, blueprints, startup and shutdown
 │   ├── config.py          environment configuration
 │   ├── models/            SQLAlchemy models
 │   ├── routes/            REST blueprints
 │   ├── mcp/               MCP server and its tool modules
 │   ├── services/          shared logic
-│   └── restore.py         `python -m scribe.restore` for a fresh instance
+│   └── restore.py         `python -m grimoire.restore` for a fresh instance
 ├── frontend/src/          views, components, stores, composables, api client
 ├── plugin/                Claude Code hooks, skills and commands
 ├── scripts/               CI checks and the plugin version minter

docs/backups.md

@@ -11,9 +11,12 @@ Set it up under **Settings → Data → Scheduled backups** (admins only).
 One file per run, named for the moment it was taken in UTC:
 
 ```
-scribe-20261015T020000Z.tar
+grimoire-20261015T020000Z.tar
 ```
 
+Backups written while the app was called Scribe are named `scribe-…tar`.
+They are counted with the rest and restore the same way.
+
 It is a plain, **uncompressed** tar:
 
 - `manifest.json` comes first. It holds the backup format version, the Grimoire
@@ -65,12 +68,12 @@ A path **inside the Grimoire container**, normally a share mounted there:
 
 ```yaml
 services:
-  scribe:
+  grimoire:
     volumes:
-      - /nfs/backup/scribe:/backups
+      - /nfs/backup/grimoire:/backups
 ```
 
-Grimoire writes each file under a hidden name (`.scribe-….tar.part`) and renames
+Grimoire writes each file under a hidden name (`.grimoire-….tar.part`) and renames
 it once it is complete. A program watching the folder never sees half a
 backup.
 
@@ -115,7 +118,7 @@ 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 Grimoire, named `scribe`
+1. On Archives' **Backups** page, make a target for Grimoire, named `grimoire`
    for example.
 2. Choose how Grimoire's files arrive:
    - **S3**: turn on the S3 way in for the target and make an **append-only**
@@ -124,8 +127,8 @@ keeps service backups as "backup targets". Either destination works with it.
      - bucket: the target's name;
      - access key and secret key: the key you just made.
    - **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`.
+     `/backups/grimoire`, and point the target at that folder. In Grimoire, choose
+     **A folder** with `/backups/grimoire`.
 3. Set the target's **Retention** to **Archives**. Archives then keeps the
    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
@@ -141,7 +144,7 @@ Start Grimoire on an empty database, copy the backup file into the container,
 and run:
 
 ```sh
-docker exec -it scribe python -m scribe.restore /backups/scribe-20261015T020000Z.tar
+docker exec -it grimoire python -m grimoire.restore /backups/grimoire-20261015T020000Z.tar
 ```
 
 - The command refuses a database that already has an account. A restore

docs/configuration.md

@@ -2,7 +2,7 @@
 
 Grimoire reads its configuration from environment variables. Most settings people change day to day (registration, SMTP, retrieval thresholds, backups, forge connections) live in **Settings** in the web UI instead.
 
-Any variable marked *secret* can also be read from a file: set `<NAME>_FILE` to the path, for example a Docker secret at `/run/secrets/scribe_key`.
+Any variable marked *secret* can also be read from a file: set `<NAME>_FILE` to the path, for example a Docker secret at `/run/secrets/grimoire_key`.
 
 ## Environment variables
 
@@ -10,7 +10,7 @@ Any variable marked *secret* can also be read from a file: set `<NAME>_FILE` to
 
 | Variable | Default | Description |
 |----------|---------|-------------|
-| `DATABASE_URL` *(secret)* | `postgresql+asyncpg://scribe:scribe@localhost:5432/scribe` | PostgreSQL connection string, using the `asyncpg` driver |
+| `DATABASE_URL` *(secret)* | `postgresql+asyncpg://grimoire:grimoire@localhost:5432/grimoire` | PostgreSQL connection string, using the `asyncpg` driver |
 | `SECRET_KEY` *(secret)* | `dev-secret-change-me` | Signs sessions and seals stored credentials. Set it before first use and keep it (see below) |
 | `BASE_URL` | `http://localhost:5000` | Public URL, used in email links and OIDC redirects |
 | `SECURE_COOKIES` | `false` | `true` when Grimoire is served over HTTPS |
@@ -79,9 +79,11 @@ docker compose up --build
 [`docker-compose.prod.yml`](../docker-compose.prod.yml) is a stack file: the app and database on a private overlay network, with `SECURE_COOKIES` and `TRUST_PROXY_HEADERS` on. Provide `DB_PASSWORD` and `SECRET_KEY` in the environment:
 
 ```bash
-DB_PASSWORD=... SECRET_KEY=... docker stack deploy -c docker-compose.prod.yml scribe
+DB_PASSWORD=... SECRET_KEY=... docker stack deploy -c docker-compose.prod.yml grimoire
 ```
 
+The database user, database and volume default to `grimoire`. An install created under the name Scribe keeps its data by setting `POSTGRES_USER`, `POSTGRES_DB` and `PGDATA_VOLUME` to the names it was created with.
+
 The shipped files leave out healthchecks and restart policies on purpose. The app waits for its database on startup, and the orchestrator's defaults restart it if it ever exits.
 
 ### Volumes

docs/development.md

@@ -65,7 +65,7 @@ Work happens on `dev`. A release merges `dev` into `main` with a plain merge com
 
 ### Backend
 
-- Services open their own session: `async with async_session() as session:` (from `scribe.models`).
+- Services open their own session: `async with async_session() as session:` (from `grimoire.models`).
 - Routes and MCP tools stay thin; the logic lives in `services/`, shared by both.
 - Access checks go through `services/access.py`, never inline ownership checks.
 - Every wait on something outside the process has a deadline.

docs/features.md

@@ -86,7 +86,7 @@ Share a project, note or task with users or groups, as viewer, editor or admin.
 
 - **Personal export**: your notes and tasks as a Markdown ZIP (with YAML frontmatter) or JSON.
 - **Admin backup and restore**, with ids remapped so a backup restores onto another instance.
-- **Scheduled backups**: a daily, dated, uncompressed tar to a folder or an S3-compatible bucket, laid out so a deduplicating tool such as restic stores only what changed. `python -m scribe.restore` brings a fresh instance back from one. See [Backups](backups.md).
+- **Scheduled backups**: a daily, dated, uncompressed tar to a folder or an S3-compatible bucket, laid out so a deduplicating tool such as restic stores only what changed. `python -m grimoire.restore` brings a fresh instance back from one. See [Backups](backups.md).
 
 ## Sign-in