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
This commit is contained in:
1 parent
3197acfc6a
commit
b219adde91
4 files changed
+6
-5
No files matched your search
@@ -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
|
||||
|
||||
|
||||
Reference in new issue
Block a user