A-464: name mesh-host in a code span, as the words test asks

This commit is contained in:
2026-11-17 01:42:59 +01:00
parent a4d7d44cd0
commit 709ad9de59
@@ -1470,6 +1470,6 @@ the principle that settles it, cited as "design 47 G A-n".
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
names. (Live, 2026-11-17 01:45: the source still named mesh-contracts at 20b06dbc, the node-engine's `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.)