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:
@@ -14,7 +14,7 @@ from unittest.mock import AsyncMock, patch
|
||||
|
||||
import pytest
|
||||
|
||||
from scribe.services.embeddings import (
|
||||
from grimoire.services.embeddings import (
|
||||
_SUPERSESSION_PENALTY,
|
||||
_apply_supersession_penalty,
|
||||
)
|
||||
@@ -23,7 +23,7 @@ from tests.helpers import fake_note
|
||||
|
||||
def _stale(*ids):
|
||||
return patch(
|
||||
"scribe.services.supersession.superseded_ids",
|
||||
"grimoire.services.supersession.superseded_ids",
|
||||
AsyncMock(return_value=set(ids)),
|
||||
)
|
||||
|
||||
@@ -109,7 +109,7 @@ async def test_a_failed_lookup_returns_unpenalised_results_not_none():
|
||||
behaviour that shipped for months; returning nothing would turn a
|
||||
supersession hiccup into a broken search."""
|
||||
scored = [(0.70, fake_note(id=1)), (0.69, fake_note(id=2))]
|
||||
with patch("scribe.services.supersession.superseded_ids",
|
||||
with patch("grimoire.services.supersession.superseded_ids",
|
||||
AsyncMock(side_effect=RuntimeError("db gone"))):
|
||||
out = await _apply_supersession_penalty(scored, limit=5)
|
||||
assert [int(n.id) for _s, n in out] == [1, 2]
|
||||
@@ -121,7 +121,7 @@ async def test_an_empty_candidate_set_short_circuits():
|
||||
"""No candidates means no lookup — this runs on every ranked query, and a
|
||||
round trip to learn nothing is a round trip too many."""
|
||||
called = AsyncMock(return_value=set())
|
||||
with patch("scribe.services.supersession.superseded_ids", called):
|
||||
with patch("grimoire.services.supersession.superseded_ids", called):
|
||||
assert await _apply_supersession_penalty([], limit=5) == []
|
||||
called.assert_not_awaited()
|
||||
|
||||
|
||||
Reference in New Issue
Block a user