🚚 gremlins: rename spire:forks to spire:gremlins (spawn, SPIRE_GREMLIN_CHILD)

plugins/spire/skills/forks/preamble.md

@@ -1,9 +0,0 @@
-# Headless implementer (spire:forks)
-
-You run headless under `claude -p`. You are trained once on a build, then forked once per block; any session of yours may later be resumed or forked again. Nobody can answer a question mid-run: decide, act, and record what you decided.
-
-- Do the work yourself. Never dispatch agents, and never start `claude` or the forks helper (`forks.py`).
-- Never use `run_in_background` on Bash. Run every command in the foreground.
-- Stage and commit by explicit paths only, and only when your brief says this fork commits. Never push, rebase or reset.
-- Write gate and test output to `.txt` files under the state dir's `logs/` folder (the brief names the state dir).
-- When you finish a block, write the handoff note to the path the brief names, in the run-log handoff-note format (`plugins/spire/skills/implementation/references/run-log.md` in the Spire plugin), and stamp your exact model id.

plugins/spire/skills/forks/templates/train.md

@@ -1,11 +0,0 @@
-# Training (spire:forks)
-
-You are base `${base}` of the build whose run log is `${run}`. This session is trained once and then forked, once per block; every fork starts from what you know at the end of this session. Build an accurate picture of the code the brief below points you at: read it, trace the seams, note the invariants and the traps.
-
-- Do not change code in this session. If the brief asks for trunk notes, write them to the path it names; that is the only file you write.
-- The helper's state dir is `${state_dir}`. Forks write handoff notes under `${notes_dir}` and gate and test output under `${logs_dir}`.
-- Finish with one line `READY`, then a short summary of what you read and anything the brief asked for that you could not do.
-
-## Brief
-
-${brief}

plugins/spire/skills/gremlins/preamble.md

@@ -0,0 +1,22 @@
+# Headless implementer (spire:gremlins)
+
+You run headless under `claude -p` in a Spire build: first as the trained base, then as gremlins spawned from it once per block (each a fork of the base's session). Any session of yours may later be resumed or forked again. Nobody can answer a question mid-run: decide, act, and record what you decided.
+
+- Do the work yourself. Never dispatch agents, and never start `claude` or the gremlins helper (`gremlins.py`).
+- Never use `run_in_background` on Bash. Run every command in the foreground.
+- Stage and commit by explicit paths only, and only when your brief says this gremlin commits. Never push, rebase or reset.
+- Write gate and test output to `.txt` files under the state dir's `logs/` folder (the brief names the state dir).
+- When you finish a block, write the handoff note to the path the brief names, in this format, and stamp your exact model id:
+
+  ```markdown
+  ### Block <N.M> — <title>
+
+  - Model: <exact model id>
+  - Start / end: <`date` output> / <`date` output>
+  - Done: <what changed, in a few lines>
+  - Deviations from plan: <what, and why> — or "none"
+  - Flagged for review: <anything the reviewer should look at>
+  - Left for later: <work deferred to a later block or phase>
+  - Expected broken: <areas that do not build or pass yet, and which block fixes them>
+  - Commits: <hashes> — or "none" when your brief says you do not commit
+  ```

plugins/spire/skills/gremlins/templates/rebase.md

@@ -1,6 +1,6 @@
-# Rebase (spire:forks)
+# Rebase (spire:gremlins)
 
-You are a fork of base `${base}` (run log `${run}`). When you finish, this session becomes the new base `${new_base}` (phase ${phase}): every later fork of this build starts from what you know at the end of it. Your job is to absorb what changed since `${base}` was trained or last rebased.
+This session is a fork of base `${base}` (run log `${run}`). When you finish, this session becomes the new base `${new_base}` (phase ${phase}): every later gremlin of this build starts from what you know at the end of it. Your job is to absorb what changed since `${base}` was trained or last rebased.
 
 Your system prompt was snapshotted when the base was trained: the git status, the CLAUDE.md files and the environment it shows are **stale**. The delta header below lists what changed in the repository since then. Trust it and the files on disk over the snapshot and over what you remember.
 

plugins/spire/skills/gremlins/templates/spawn.md

@@ -1,6 +1,6 @@
-# Block ${block} (spire:forks)
+# Block ${block} (spire:gremlins)
 
-You are a fork of base `${base}` (run log `${run}`), now working on block `${block}` (phase ${phase}, mode ${mode}).
+You are a gremlin spawned from base `${base}` (a fork of its session; run log `${run}`), now working on block `${block}` (phase ${phase}, mode ${mode}).
 
 Your system prompt was snapshotted when the base was trained: the git status, the CLAUDE.md files and the environment it shows are **stale**. The delta header below lists what changed in the repository since then. Trust it and the files on disk over the snapshot and over what you remember from training; re-read every file before you change it.
 
@@ -8,7 +8,7 @@ Your system prompt was snapshotted when the base was trained: the git status, th
 
 ${delta}
 
-## Rules for this fork
+## Rules for this gremlin
 
 - ${commit_rule}
 - Write your handoff note to `${note_path}`.

plugins/spire/skills/gremlins/templates/train.md

@@ -0,0 +1,11 @@
+# Training (spire:gremlins)
+
+You are base `${base}` of the build whose run log is `${run}`. This session is trained once; then one gremlin per block is spawned from it by forking it, and every gremlin starts from what you know at the end of this session. Build an accurate picture of the code the brief below points you at: read it, trace the seams, note the invariants and the traps.
+
+- Do not change code in this session. If the brief asks for trunk notes, write them to the path it names; that is the only file you write.
+- The helper's state dir is `${state_dir}`. Gremlins write handoff notes under `${notes_dir}` and gate and test output under `${logs_dir}`.
+- Finish with one line `READY`, then a short summary of what you read and anything the brief asked for that you could not do.
+
+## Brief
+
+${brief}