From 62f3cc4b1926034d5eb83e22b6d2032d814866d7 Mon Sep 17 00:00:00 2001 From: iris Date: Sat, 15 Aug 2026 12:24:53 +0200 Subject: [PATCH] docs(coordinator): fix stale DAG-history cap, wire request name, infra container list --- docs/coordinator.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/coordinator.md b/docs/coordinator.md index 893cb908..9e231eb4 100644 --- a/docs/coordinator.md +++ b/docs/coordinator.md @@ -174,7 +174,7 @@ without a row are seeded from observed state on first touch (running ⇒ `Up`); destroy removes the row. The admin-socket responses carry the submitted DAG ids; `hivectl` polls -`HostRequest::QueueDag` (~1s) and prints a progress line per DAG — roll-up +`HostRequest::QueueNodes` (~1s) and prints a progress line per DAG — roll-up glyph, template, agent, node chain — so CLI verbs block until their jobs finish (`--no-wait` opts out; failures exit non-zero). Nodes appended in-DAG (a `MetaLock` growing per-agent rebuild @@ -259,8 +259,9 @@ whether any dedup needs reintroducing is tracked as a follow-up. Cancel only applies to still-fully-queued DAGs (an in-flight nix build isn't interruptible) — each op is one DAG now, so there are no child DAGs to cascade to. Roll-up state: `Failed` if any node failed, else `Running` / `Queued` / -`Cancelled` / `Done`. The snapshot retains the 5 most recent terminal DAGs -per template. +`Cancelled` / `Done`. The snapshot retains the 50 most recent terminal +DAGs — a flat cap over the whole sorted list, not per template, since +the dashboard renders one recent-builds list and one number bounds it. ### Approvals @@ -500,8 +501,8 @@ Two things to know about the weights: same value and the weight does *not* rank agents against each other. What `80` buys is that agents yield to everything **not** on this drop-in path: host services (nginx and dnsmasq among them) and the - infra containers (`hive-ci`, `hive-forge`, `hive-matrix`), which stay - at the kernel default of `100`. + infra containers (`hive-ci`, `hive-forge`, `hive-gateway`, + `hive-matrix`), which stay at the kernel default of `100`. - `IOWeight=` is only honoured when the backing device runs the BFQ scheduler or has blk-iocost QoS enabled. On a host using `none`/`mq-deadline`/`kyber` without iocost, systemd writes the value