docs: three anchors that were already broken point at their headings
The swarm UI reference links the try-out section by its heading, and drops a pointer to a hivectl section that never existed along with the sentence that claimed hivectl sets the hive's limits. The turn-loop index links the persistence reference's /harness/paused heading by its real slug.
This commit is contained in:
parent
26152161ca
commit
aff8cf629d
2 changed files with 3 additions and 4 deletions
|
|
@ -27,7 +27,7 @@ agents) runs:
|
|||
queued and unacked, so a resume drains the backlog instead of
|
||||
losing it; reminders and todo wakes buffer in their channels. Set
|
||||
it with `hivectl agent <name> pause` or the dashboard toggle; see
|
||||
[persistence](../../4-implementation/agent-state/persistence.md#-harnesspaused-per-agent).
|
||||
[persistence](../../4-implementation/agent-state/persistence.md#harnesspaused-per-agent).
|
||||
1. Long-poll `Recv` on its socket. The host-side broker
|
||||
(`broker.rs::recv_blocking_batch`) returns immediately if there's
|
||||
a pending message, otherwise waits up to 30 s for a broker `Sent`
|
||||
|
|
|
|||
|
|
@ -226,7 +226,7 @@ run, newest first, one card per run. A card shows the repo and PR, the head
|
|||
commit, whether the run was a try-out or a requested review, how long ago it
|
||||
started, how long it took, how many classifications ran, and the outcome as a
|
||||
badge. Select a card to open it: it shows the same result table as the
|
||||
[try-out](#review-try-out), the overall verdict, the reason when the outcome
|
||||
[try-out](#try-a-classification), the overall verdict, the reason when the outcome
|
||||
has one, and a link to the posted review when there is one. While the first
|
||||
answer loads, the section shows three grey placeholder cards.
|
||||
|
||||
|
|
@ -742,8 +742,7 @@ A saved change isn't instant. The hive reads the caps about every 30 seconds,
|
|||
and a running agent takes a changed cap at its next spawn or rebuild, so the
|
||||
row shows the new value before the agent runs under it. The card reads
|
||||
`GET /api/agents/{agent}/limits`; when that read fails, the card shows the
|
||||
reason and a **retry** button. [hivectl](../../2-handbook/hives/hivectl.md#per-agent-resource-limits)
|
||||
sets the hive's own limits.
|
||||
reason and a **retry** button.
|
||||
|
||||
### Permissions
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue