🤖 Guidance pass B: fix stale and contradicting Spire text

2026-10-17 00:19:26 +02:00
parent 3f684ce459
commit 9fd01edd63
11 changed files with 20 additions and 24 deletions
@@ -84,5 +84,4 @@ Read these from `spire:project` (its `## Build` section; `project.local.md` wins
 ## Composition

 - **`workpad`** decides where documents go. **`research-tree`** comes first when how to build is itself an open question.
- **Superpowers** is not part of this cycle. When to use it anyway (e.g. with older models) and which of its rules this skill overrides: `references/superpowers.md`.
 - This skill does not govern code style, test frameworks, CI or plan formats.
@@ -59,7 +59,7 @@ The harness changes. When a claim fails, fix it here with a new date.
 |---|---|
 | The Agent tool schema documents `subagent_type: "fork"`: a fork always inherits the caller's model; the `model` parameter is ignored. | verified 2026-10-05 (schema text) |
 | `fork` is actually offered as an agent type in a given session. | unverified: the schema mentions it, but on 2026-10-05 it was not in the list of agent types offered to the reviewer |
-| A fork copies the **caller**, not an arbitrary agent. Only the agent holding a context (e.g. the Athanor as trunk) can fork it. | assumed (no parameter names a fork source; Igor's skill calls it "forking yourself") |
+| A fork copies the **caller**, not an arbitrary agent. Only the agent holding a context (e.g. the Athanor as trunk) can fork it. | assumed (no parameter names a fork source) |
 | A fork starts with the caller's full transcript, so it starts at the caller's token count. | assumed, not measured |
 | Can a fork fork again? Does a foreground fork return its result to the caller? Does it see the caller's preloaded skills? | unknown; check in a throwaway preflight before relying on trunk and forks |