gates.md/session-setup.md: Regel für eine neue Session-Id nur noch in gates.md - session-setup verweist statt die plan.md-Grenze zu wiederholen, gates.md zählt die beiden Agenten-Fälle (#219); 10.1.0-beta.14

Files changed:
- CHANGES.md
- VERSION
- instructions/gates.md
- instructions/session-setup.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

instructions/gates.md

@@ -241,7 +241,7 @@ points). The agent never proposes this itself, and it is no way past a refusal.
 caller's budget nor is refused by it at exactly the moment something has gone wrong. That is
 permitted because the script sets the id for those two commands only, never in the caller's
 shell, and the set is a constant in the script. It is not a precedent for an agent: an agent that
-exports a `bugreport-*` id, or any other, outside the two cases above is opening the gate.
+exports a `bugreport-*` id, or any other, outside the two agent cases above is opening the gate.
 
 Background: the [[Iteration and Cost Limits]] concept page in `kb/`.
 

instructions/session-setup.md

@@ -104,8 +104,8 @@ The run key, the workshop directory name and the session id are then the same st
 checklist in `work/<runkey>/README.md` and the budget state cannot disagree about where the
 run stands.
 
-A new id may only be taken at a unit boundary recorded in `plan.md` - never after a gate
-refusal. See [gates.md](gates.md).
+When a new id may be taken at all - and that it never may after a gate refusal - is
+[gates.md](gates.md) § Taking a new session id.
 
 ## Scope