Answer A-227: merged gains base, as §714 says; A-221 and A-223 withdrawn

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 96404d8acf
commit e8a2134d94
1 changed files with 3 additions and 0 deletions
@@ -186,3 +186,6 @@ the principle that settles it, cited as "design 47 G A-n".
  `mesh-compose` once per node-engine fingerprint among the machines (the change's build where the change alters the
  node-engine, §63), the program read from that fingerprint's catalog entry through `entry`, each run's request
  joining the inputs of the machines on that fingerprint.
+- **A-227** (withdraws A-221 and A-223; §714, §715) As design line §714 says, a merged message gains `base`, the
+  watched branch it landed on; `branch` stays the pull request's branch and `head` its head commit, as today;
+  `pushed` keeps `branch` for the branch pushed and gains `before`.