Answer A-464: the gate's source follows every merge into a watched branch

This commit is contained in:
2026-11-17 01:42:43 +01:00
parent 47332934b8
commit a4d7d44cd0
@@ -1463,3 +1463,13 @@ the principle that settles it, cited as "design 47 G A-n".
mesh-contracts #14, merged 2026-11-16 14:14Z, was never taken in; `packages` kept every mesh-contracts package at
20b06dbc, and every build of the node-engine since 15:24Z and of the assigner since 22:51Z failed on symbols only #14
holds.)
- **A-464** (amends A-463; principles 2, 3, 1 and 4) The gate's source of a watched branch follows every merge into
that branch, whoever made it: on the forge bridge's `merged` of a repository the source names, at the branch the
source watches, the gate moves that repository's head to the merge and says `source-moved`, as for a group it
merged itself; a merge it did not make is said so in its log and its record. At its start the gate compares each
head with the forge's branch head (through the seat `git`) and moves every one behind it the same way, so a merge
whose message was lost is followed too. The gate's tool `gate_source_follow` (branch, repository, why; a hand act)
does the same for one repository now. A-463's comparison in the indexer stays: it then takes in what the source
names. (Live, 2026-11-17 01:45: the source still named mesh-contracts at 20b06dbc, mesh-host at 13fcfae0 and
mesh-delivery at 8c4489fb, though #14, #232, #233 and #237 were merged into their mains; every merge made outside
the gate, as in recovery, was never taken in, built or delivered.)