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:
@@ -19,11 +19,11 @@ import pytest
|
||||
import pytest_asyncio
|
||||
from sqlalchemy import delete, func, select
|
||||
|
||||
from scribe.models import async_session
|
||||
from scribe.models.note import Note
|
||||
from scribe.models.user import User
|
||||
from scribe.services.knowledge import location_matches, location_parts
|
||||
from scribe.services.snippets import (
|
||||
from grimoire.models import async_session
|
||||
from grimoire.models.note import Note
|
||||
from grimoire.models.user import User
|
||||
from grimoire.services.knowledge import location_matches, location_parts
|
||||
from grimoire.services.snippets import (
|
||||
SNIPPET_NOTE_TYPE,
|
||||
backfill_snippet_data,
|
||||
compose_body,
|
||||
@@ -152,7 +152,7 @@ async def test_keyword_arm_applies_the_location_filter(seeded):
|
||||
keyword (ILIKE) arm, which is the second place the SQL clause has to appear."""
|
||||
user_id, ids = seeded
|
||||
with patch(
|
||||
"scribe.services.embeddings.semantic_search_notes",
|
||||
"grimoire.services.embeddings.semantic_search_notes",
|
||||
AsyncMock(return_value=[]),
|
||||
):
|
||||
assert await _ids_for(user_id, q="nested", repo="Grimoire") == {ids["nested"]}
|
||||
@@ -180,7 +180,7 @@ async def test_semantic_arm_applies_the_location_filter(seeded):
|
||||
candidates = [(0.9, n) for n in rows]
|
||||
|
||||
with patch(
|
||||
"scribe.services.embeddings.semantic_search_notes",
|
||||
"grimoire.services.embeddings.semantic_search_notes",
|
||||
AsyncMock(return_value=candidates),
|
||||
):
|
||||
# No keyword can match this, so every hit below came from the stub.
|
||||
|
||||
Reference in New Issue
Block a user