rename(547): the plugin is grimoire — manifest, MCP key, hooks, env, skills

Step 3 of the Scribe -> Grimoire rename.

- Plugin `grimoire` in marketplace `grimoire-plugin`, MCP server key
  `grimoire`, so tools reach a session as mcp__plugin_grimoire_grimoire__*.
- hooks/scribe_* -> hooks/grimoire_*, their shell functions and the TMPDIR
  ledgers with them; SCRIBE_URL / SCRIBE_TOKEN / SCRIBE_HOOK_DIR /
  SCRIBE_LEDGER_DIRS -> GRIMOIRE_*; the project marker is `.grimoire`.
- skills/using-scribe -> using-grimoire, /grimoire:sync, stored processes
  arrive as grimoire-proc-<slug>; moment_actions names them the same way.
- Migration 0124 rewrites stored skill names (rule_moments,
  rule_moment_judgments, moment_mappings) from scribe:/scribe-proc- to
  grimoire:/grimoire-proc-, so a rule mounted on a skill keeps firing.
- Settings' install commands and MCP-only defaults, the docs and the
  tests follow.
- scripts/check_plugin.py drops the smoke event for a report-check hook
  that has no file in plugin/hooks.

Kept on purpose: the secret-sealing label, and the names that let backups
written as Scribe restore and be counted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugin/skills/using-grimoire/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: using-scribe
+name: using-grimoire
 description: Use at the START of every session, and before answering anything about the operator's work or starting any task — establishes the Grimoire-first reflex. You hold none of the operator's rules: they arrive by retrieval when your work matches one, and what_might_apply is how you ask before a consequential act — it returns the wide net of candidates with no bar. Call enter_project when a repo/project is in scope. Then recall before acting, update over duplicate, plan in Grimoire not in files.
 metadata:
   moments: session.start
@@ -9,7 +9,7 @@ metadata:
 
 Grimoire is the operator's self-hosted system of record (notes, tasks, issues,
 projects, milestones, systems) and rulebook, reachable
-through the bundled `scribe` MCP server. Its value is mostly in what it
+through the bundled `grimoire` MCP server. Its value is mostly in what it
 **already holds** — so make reading it a reflex, not something you wait to be
 asked for.
 

plugin/skills/using-grimoire/missed-retrieval.md

@@ -1,6 +1,6 @@
 # When a record doesn't reach the moment it should
 
-Part of the using-scribe skill. Read it when a rule should have governed a
+Part of the using-grimoire skill. Read it when a rule should have governed a
 moment and never arrived, when one arrives on every turn and never applies,
 or before touching a retrieval floor.
 

plugin/skills/using-grimoire/moments.md

@@ -1,6 +1,6 @@
 # Moments — rules that arrive when the work reaches a point
 
-Part of the using-scribe skill. Read it when a line says a rule arrived *at* a
+Part of the using-grimoire skill. Read it when a line says a rule arrived *at* a
 moment, when a reply is held for one read, when an action reached the wrong
 moment or none, when a mounted rule arrived and did not apply, and when a line
 proposes mounting or unmounting a rule.

plugin/skills/using-grimoire/projects.md

@@ -1,6 +1,6 @@
 # Projects: binding a directory, and starting one
 
-Part of the using-scribe skill. Read it when a working directory maps to no
+Part of the using-grimoire skill. Read it when a working directory maps to no
 project, or when a new project is about to be created.
 
 ## Binding a directory to a project
@@ -8,9 +8,9 @@ project, or when a new project is about to be created.
 **A directory does not have to be a git repo to have a project.** A repo is
 bound by its remote (`list_repo_bindings` shows the bindings). Anything else —
 a notes folder, a server's config directory, a scratch directory — is bound by
-a `.scribe` file naming the project:
+a `.grimoire` file naming the project:
 
-    {"instance": "https://scribe.example.com", "project_id": 2, "project": "Homelab"}
+    {"instance": "https://grimoire.example.com", "project_id": 2, "project": "Homelab"}
 
 `instance` is what makes the id trustworthy. An id means nothing on its own —
 it is a different project on every Grimoire — so a marker that has travelled to

plugin/skills/using-grimoire/writing-records.md

@@ -1,6 +1,6 @@
 # Writing a rule, a lesson, or a note that asserts a fact
 
-Part of the using-scribe skill. Read it before `create_rule`,
+Part of the using-grimoire skill. Read it before `create_rule`,
 `create_project_rule`, `create_preference`, `create_process` or
 `create_lesson`; when a lesson
 arrives that names the situation you are actually in; when the operator