From e5e62ad2e673924f401a7cdfa4b9b821fb32de78 Mon Sep 17 00:00:00 2001 From: iris Date: Thu, 2 Jul 2026 14:49:06 +0200 Subject: [PATCH] docs(web-ui/dashboard): fix missing /api/ prefix on meta-update endpoint POST /meta-update was documented without the /api/ prefix in two places (BU1LDS section prose + endpoint list). The actual route is /api/meta-update (hive-c0re/src/dashboard.rs). --- docs/web-ui/dashboard.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md index a2efbc92..61fe767a 100644 --- a/docs/web-ui/dashboard.md +++ b/docs/web-ui/dashboard.md @@ -145,7 +145,7 @@ nodes are skipped. A `select all / select none` control sits above the tree. Checking inputs + submitting bumps the lock in `/meta/` and rebuilds the selected agents in sequence; each outcome reaches the root agent as a `rebuilt` -system event. `POST /meta-update`. While a lock-bump ripple runs, +system event. `POST /api/meta-update`. While a lock-bump ripple runs, the panel shows a pulsing "⏳ meta-update running" banner and the update button is disabled (snapshot field `meta_update_running`, live event `meta_update_running`). @@ -1197,7 +1197,7 @@ that's a browser-level decision, not ours. Per-target `last_result` is annotated as a manual fire so the audit trail distinguishes scheduled fires from operator- triggered ones. -- `POST /meta-update` — `nix flake update` the selected +- `POST /api/meta-update` — `nix flake update` the selected `meta/flake.lock` inputs, then rebuild the affected agents. - `GET /dashboard/stream` — unified live event channel: broker `sent` / `delivered`, plus the mutation events listed