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

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

@@ -0,0 +1,17 @@
+# Rebase (spire:gremlins)
+
+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.
+
+- Read the handoff notes and the diffs the brief lists (`git --no-optional-locks diff`, `git --no-optional-locks log -p`), and re-read the files they touch. Handoff notes live under `${notes_dir}`.
+- Do not change code and do not commit. If the brief names a trunk-notes path, update that file; it is the only file you write.
+- Finish with one line `READY`, then a short summary of what changed and anything the brief asked for that you could not do.
+
+## Delta since the base commit
+
+${delta}
+
+## Brief
+
+${brief}

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

@@ -0,0 +1,19 @@
+# Block ${block} (spire:gremlins)
+
+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.
+
+## Delta since training
+
+${delta}
+
+## Rules for this gremlin
+
+- ${commit_rule}
+- Write your handoff note to `${note_path}`.
+- Write gate and test output to `.txt` files under `${logs_dir}`.
+
+## Brief
+
+${brief}

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}