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:
@@ -22,7 +22,7 @@ import pytest_asyncio
|
||||
|
||||
from tests.helpers import ensure_user
|
||||
|
||||
from scribe.services import snippets as s
|
||||
from grimoire.services import snippets as s
|
||||
|
||||
CODE = "def helper():\n return 1"
|
||||
NOTES = "Shaped this way because the caller owns the session.\n\nSuperseded #12."
|
||||
@@ -72,7 +72,7 @@ def test_notes_after_code_that_itself_contains_the_heading():
|
||||
def test_long_notes_are_chunked_apart_from_the_code():
|
||||
"""The heading is the chunker's split point, so a long explanation gets
|
||||
vectors of its own instead of averaging into the code's."""
|
||||
from scribe.services.embeddings import chunk_document
|
||||
from grimoire.services.embeddings import chunk_document
|
||||
|
||||
long_notes = "\n\n".join(["An explanatory paragraph about the history. " * 12] * 4)
|
||||
body = s.compose_body(code=CODE, language="python", when_to_use="a helper",
|
||||
@@ -107,7 +107,7 @@ def test_a_headed_or_multi_paragraph_trigger_is_advised_even_when_short():
|
||||
|
||||
@pytest_asyncio.fixture
|
||||
async def user_id(_dispose_engine):
|
||||
from scribe.models import async_session
|
||||
from grimoire.models import async_session
|
||||
|
||||
async with async_session() as session:
|
||||
uid = (await ensure_user(session, "snippet_notes_itest")).id
|
||||
|
||||
Reference in New Issue
Block a user