Say S17 clears once the new bus is sent, as it does
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered

The comment and the signals table's bound said it cleared once the bus's machine runs the new build; it
clears once that machine has been sent it, when no send is refused for the bus any more.
This commit is contained in:
jochen
2026-10-09 03:23:47 +02:00
parent 9a7ae131cb
commit 822e52123c
2 changed files with 4 additions and 3 deletions
+1 -1
View File
@@ -213,7 +213,7 @@ var signalsTable = []signalRow{
{Row: "S17", Signal: "a send held for the bus's planned step is told to a person", Emitter: "controller's plan",
Trigger: "each send refused because it would replace the bus outside its step (novox/hq issue 336)",
Bound: "none: raised at the first refusal, for the operator, naming what waits, the bus build from and to, " +
"since when and `bus upgrade`; cleared once the bus's machine runs the build the mesh holds",
"since when and the mesh-controller.bus call; cleared once the bus's machine has been sent the build the mesh holds",
Kind: kindBusStepWaiting, Severity: conditions.Warning, Phase: 3,
needs: func(f *signalFacts) error {
if f.plansErr != nil {