rename(547): what people read says Grimoire

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>

frontend/src/components/BackupScheduleSettings.vue

@@ -189,7 +189,7 @@ async function backUpNow() {
       <p class="intro">
         Each run adds one dated file, <code>scribe-&lt;date&gt;.tar</code>, holding every table
         as plain lines. It is not compressed, so a deduplicating tool such as restic stores only what
-        changed since the day before. Scribe never deletes old backups — the destination keeps and
+        changed since the day before. Grimoire never deletes old backups — the destination keeps and
         thins the history. Sharing, API keys and forge connections are not included.
       </p>
 
@@ -223,7 +223,7 @@ async function backUpNow() {
           <span>Folder</span>
           <input v-model.trim="form.folder_path" class="fs-input" placeholder="/backups" />
           <span class="field-hint">
-            A path inside the Scribe container — usually a share mounted there that a backup
+            A path inside the Grimoire container — usually a share mounted there that a backup
             service watches.
           </span>
         </label>