rename(547): the server is grimoire — package, image, DB defaults, backups
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 1m4s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 44s
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 1m4s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 44s
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>
This commit is contained in:
@@ -33,8 +33,8 @@ from tests.helpers import tool_doc as _doc
|
||||
# explain what a RESULT means, which is a different job — they are deliberately
|
||||
# not held to this.
|
||||
_WRITE_SURFACES = [
|
||||
("scribe.mcp.tools.notes", "create_note"),
|
||||
("scribe.mcp.tools.notes", "update_note"),
|
||||
("grimoire.mcp.tools.notes", "create_note"),
|
||||
("grimoire.mcp.tools.notes", "update_note"),
|
||||
]
|
||||
|
||||
|
||||
@@ -79,7 +79,7 @@ def test_expires_when_is_described_as_a_state_not_a_date():
|
||||
"""The one field whose obvious reading is wrong. A date invents a staleness
|
||||
schedule nobody can justify; a constraint expires when the ground moves,
|
||||
which is a condition and not a time."""
|
||||
doc = _doc("scribe.mcp.tools.notes", "create_note")
|
||||
doc = _doc("grimoire.mcp.tools.notes", "create_note")
|
||||
assert "STATE" in doc, (
|
||||
"create_note no longer says expires_when is a STATE. Left to itself, "
|
||||
'"expires" reads as a date, and every check would get an arbitrary one.'
|
||||
|
||||
Reference in New Issue
Block a user