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:
@@ -42,7 +42,7 @@ def test_a_request_for_approval_has_its_own_named_section():
|
||||
"""A go-ahead request inside a completion list, as "Blocked by the
|
||||
permission check", reads as a fault rather than a question waiting on the
|
||||
operator. The heading is what they scan for, so it is pinned by name."""
|
||||
from scribe.services import reply_shapes
|
||||
from grimoire.services import reply_shapes
|
||||
|
||||
assert "Approval requested" in _text()
|
||||
# The kinds live in the delivered shapes: the asks shape
|
||||
@@ -78,7 +78,7 @@ def test_the_skill_points_at_the_delivered_shapes_instead_of_restating_them():
|
||||
def test_the_worked_completion_report_agrees_with_the_delivered_completion_shape():
|
||||
"""The two copies that could drift: the worked example here, and the
|
||||
completion shape the server sends when a task closes. Same sections."""
|
||||
from scribe.services import reply_shapes
|
||||
from grimoire.services import reply_shapes
|
||||
|
||||
shape = reply_shapes.SHAPES["completion"].text
|
||||
for section in ("Where this sits", "What now works", "How / why", "Needs you", "Next"):
|
||||
@@ -89,6 +89,6 @@ def test_the_worked_completion_report_agrees_with_the_delivered_completion_shape
|
||||
def test_the_core_names_the_header_the_skill_quotes():
|
||||
"""The skill tells the reader what the delivered core looks like; if the
|
||||
header changes, the pointer would describe something that never arrives."""
|
||||
from scribe.services import reply_shapes
|
||||
from grimoire.services import reply_shapes
|
||||
|
||||
assert reply_shapes.render(reply_shapes.core(), full=True).startswith("Reply shape · Every reply")
|
||||
|
||||
Reference in New Issue
Block a user