jochen
2e1a9abbf7
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 failed: its walk failed: a gate on a first machine (what it carried put back), a build, a machine
The node-engine's own since starts again at every restart, so an agent that restarted the engine in a loop kept agent-can-become-root quiet for ever (the review of 2026-10-09). The controller now keeps when it first saw the verdict waiting for the setuid search (migration 0085), forgets it at the next complete verdict, and raises once the engine's own bound has passed since; the bound and the pending reason are read from mesh-host's rootsearch.
10 lines
764 B
SQL
10 lines
764 B
SQL
-- The controller keeps when it first saw an agent account's root verdict waiting for the node-engine's search
|
|
-- for setuid programs (novox/hq ADR 0266), cleared by the next complete verdict.
|
|
--
|
|
-- The self-check does not raise `agent-can-become-root` while that search is within its bound, so a restart is
|
|
-- not an urgent condition each time. The node-engine's own "since" starts again at every restart: an agent
|
|
-- that restarted the engine in a loop kept the condition quiet for ever. This time is the controller's, kept
|
|
-- across the engine's restarts and its own, so the quiet ends once the bound has passed since the search first
|
|
-- read as pending, however often the engine started again.
|
|
alter table node add column agent_root_pending_since timestamptz;
|