rename(547): what people read says Grimoire
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 52s
CI & Build / integration (push) Successful in 1m1s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 36s
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 52s
CI & Build / integration (push) Successful in 1m1s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 36s
Step 1 of the Scribe -> Grimoire rename: every capitalised "Scribe" in prose
becomes "Grimoire" ("Fabled Scribe" -> "Fabled Grimoire") across the UI,
the PWA manifest and page title, the MCP instructions and tool docstrings,
hook and skill text, docs and README, with the tests that assert on that
prose moving with it. Old migrations keep their wording.
Identifiers are untouched here: the package, plugin name, MCP server key,
hook file names, env vars, the .scribe marker and FabledScribe repo/image
names move in steps 2 and 3, along with prose that quotes them.
The sweep matched "Scribe" only as a whole word, so describe/subscribe and
friends are untouched. The longer name took the MCP instructions one
character over their 1,600 budget; two phrases are shortened to fit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -11,7 +11,7 @@ than a reimplementation of it. What they pin:
|
||||
* the marker is found from a subdirectory, the way git finds its root;
|
||||
* a bare integer works, because that is what a person writes by hand;
|
||||
* the marker BEATS a git remote, since someone put the file there on purpose;
|
||||
* an `instance` naming a different Scribe is refused — the case the field
|
||||
* an `instance` naming a different Grimoire is refused — the case the field
|
||||
exists for. A project id means nothing on its own: id 2 is a different
|
||||
project on every instance, so a marker that travels would otherwise scope
|
||||
the session to the wrong project, confidently and without a word.
|
||||
@@ -73,7 +73,7 @@ def test_the_marker_is_found_from_a_subdirectory(tmp_path):
|
||||
|
||||
def test_a_matching_instance_is_honoured(tmp_path):
|
||||
"""Host-only comparison, so http/https and a trailing slash are not a
|
||||
mismatch — only a genuinely different Scribe is."""
|
||||
mismatch — only a genuinely different Grimoire is."""
|
||||
_marker(tmp_path, instance="http://scribe.example.com/", project_id=2)
|
||||
assert _sh(f'scribe_scope_query "{tmp_path}"', tmp_path) == "project_id=2"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user