Answer A-334: in a group take-in the changed runner is wanted on its own pass, first

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-13 02:12:58 +01:00
parent e4145affa2
commit 5df4fb0ff6
1 changed files with 4 additions and 0 deletions
@@ -638,3 +638,7 @@ the principle that settles it, cited as "design 47 G A-n".
  made and cannot close a cycle. How it is checked: the indexer's cycle rule accepts today's trunk catalogue and G's own
  (the dry run's entries, kept as test data), and refuses a cycle with a build edge among delivered artifacts, naming
  them.
+- **A-334** (sharpens A-328; §29, §65, §268; principle 5) In a group take-in that changes the runner, the runner is the
+  acting part the other members wait on, so it goes first as the node-engine does (§268): its member is wanted on its own
+  pipeline-ended once that passed, ahead of the group. The other members keep §29: their pipelines run on the new runner
+  once it runs, and they are wanted together on group-ended. The bound stays a failure bound only.