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,14 +33,14 @@ from unittest.mock import AsyncMock, patch
|
||||
|
||||
import pytest
|
||||
|
||||
from scribe.services import retrieval_surfaces as rs
|
||||
from grimoire.services import retrieval_surfaces as rs
|
||||
|
||||
SERVICES = ("plugin_context",)
|
||||
|
||||
|
||||
def _service_source(name: str) -> str:
|
||||
from pathlib import Path
|
||||
root = Path(__file__).resolve().parents[1] / "src" / "scribe" / "services"
|
||||
root = Path(__file__).resolve().parents[1] / "src" / "grimoire" / "services"
|
||||
return (root / f"{name}.py").read_text()
|
||||
|
||||
|
||||
@@ -57,7 +57,7 @@ def test_every_surface_name_is_a_real_telemetry_source():
|
||||
# The rule arms record through the one pipeline, where
|
||||
# `source` is the spec's own field — so for them the spec IS the string
|
||||
# `record_retrieval` receives, and the join key is checked against it.
|
||||
from scribe.services.retrieval_pipeline import NOTE_ARMS, RULE_ARMS
|
||||
from grimoire.services.retrieval_pipeline import NOTE_ARMS, RULE_ARMS
|
||||
|
||||
via_pipeline = {arm.source for arm in (*RULE_ARMS, *NOTE_ARMS)}
|
||||
missing = [
|
||||
@@ -168,7 +168,7 @@ async def test_the_write_path_config_carries_every_arm_it_drives():
|
||||
and found nothing". That is the failure this asserts against, and it is the
|
||||
reason tests build the dict from the registry rather than by hand.
|
||||
"""
|
||||
from scribe.services import plugin_context as pc
|
||||
from grimoire.services import plugin_context as pc
|
||||
|
||||
# Both modules read settings: `pc` for the enabled switch, `rs` for the
|
||||
# pairs. Patching one and not the other reaches a real database.
|
||||
|
||||
Reference in New Issue
Block a user