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).
This commit is contained in:
parent
d5a27a5823
commit
e5e62ad2e6
1 changed files with 2 additions and 2 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue