docs: add the runners page and the Aug 18 changelog entry

[indykish]

Companion to the agentsfleet M136_001 Pull Request (PR). Both land together.

What changed

New page: Runners. The dashboard's runner policy dialogs had nowhere to
send an operator. Every field there is an assignment with a default and a range, and the
form can state the degraded verdict but not explain it. The page covers:

• enrolment through Admin → Runners → Add runner, and the token shown once;
• the environment variables a host reads — AGENTSFLEET_API_URL,
  AGENTSFLEET_RUNNER_TOKEN, and the optional RUNNER_STORAGE_HOME — and why no policy
  value is read from the host;
• every policy field with its effect, default and valid range: Isolation, Network policy,
  Allowlist (up to 32 hosts), Workers (1 to 64), Mounts (up to 16 paths);
• what marks a runner degraded and how it clears, plus Cordon, Drain and Revoke;
• the limits — allowlist egress unenforced, no-sandbox refused outside development,
  raising Workers past the started count needing a restart, and the capability report
  being self-declared.

Navigation. A Runners group in the Guides tab, after Workspaces.

Changelog. One <Update> for Aug 18, leading with the one-step install. It names the
server-derived naming and the UZ-AGT-006 that survives it, the upload source on the
platform fleet library, the mounts vocabulary and shown baseline, the model price labels,
and the development-runner lease failure.

Sourcing

Every number and name was read from the product repository on the branch that ships them,
not from prose:

• policy fields, labels and defaults — ui/packages/app/lib/api/runners.ts
• the 32-host allowlist cap — protocol_policy.MAX_REGISTRY_ENTRIES
• the 16-mount cap — policy-binds.ts
• enrolment flow and the environment pair — docs/architecture/runner_fleet.md
• degraded reconciliation — heartbeat_reconcile.zig

Verification

make lint passes: schema validation, mint broken-links (no broken links), and the
documentation-rules check. One DOC-03 violation was caught and fixed during authoring —
a four-sentence paragraph, split into a list.

Noted, not changed

AGENTS.md §Terminology contradicts itself: it names "agent" as the product noun and, in
the same sentence, calls "agent" legacy terminology to keep out of new prose. It reads
like a find/replace that hit both sides. Every live page and the whole navigation already
use "fleet", which is what the new page follows. Left alone deliberately — it is a
governance file and outside this milestone's scope.

Greptile Summary

Adds a Runners guide and an Aug 18 changelog entry, then exposes the new guide through the Guides navigation.

• Documents runner enrollment, host configuration, assigned policies, degraded states, lifecycle controls, and current limitations.
• Adds the Runners navigation group after Workspaces.
• Summarizes the Aug 18 product changes and fixes in the changelog.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
runners.mdx	Adds the runner operations guide and correctly distinguishes its two required environment variables from the optional storage variable.
docs.json	Adds the new Runners page to the Guides navigation.
changelog.mdx	Adds the Aug 18 release entry and links readers to the new Runners guide.

_{Reviews (2): Last reviewed commit: "Update runners.mdx" | Re-trigger Greptile}

Context used:

• Knowledge Base — Onboarding: landing page, quickstart, changelog, and memory
• Knowledge Base — Documentation validation tooling