docs: drop redundant hyphens from -ly adverb + adjective/participle compounds

Fixes 22 of 23 Microsoft.Hyphens hits: an adverb ending in -ly doesn't
need a hyphen to the word it modifies (minimally scoped, currently
running, deliberately stopped, ...) -- the -ly ending already
unambiguously signals it's modifying the following word, so the
hyphen is redundant per Microsoft style.

Left one hit alone: docs/web-ui/dashboard.md's 'checked-not-originally-
active' is a single 4-word compound designator (parallel structure
with 'unchecked-was-active' right before it in the same sentence,
describing a diffing algorithm's two possible states), not an
ordinary -ly-adverb modifier -- dropping just the one hyphen vale
flagged would have broken the compound into a dangling
'checked-not-originally active' fragment. Also rewrote
docs/scheduler/coordinator.md's 'still-fully-queued' as a predicate
('DAGs that are still fully queued') rather than leaving a similar
broken partial-hyphen chain, since 'still' and 'fully' are both plain
adverbs with no reason to hyphenate at all once dehyphenated
consistently.

Verified via vale: only the one deliberately-left hit remains.

docs/web-ui/dashboard.md

@@ -198,7 +198,7 @@ its queue-summary banner reads the much narrower `GET /api/jobq/rollup`
 instead (see Container row, below) — a handful of pre-tallied counts,
 not the graph.
 
-**R3BU1LD QU3U3** — pending, in-flight, and recently-settled container
+**R3BU1LD QU3U3** — pending, in-flight, and recently settled container
 operations: rebuilds, meta-update cascades, and first-spawns. One
 operation runs at a time; the worker drains FIFO. **Is a mounted
 `JobqGraph`** (the shared generic graph-viewer Preact component,
@@ -255,7 +255,7 @@ concerns, so a narrow filter never reaches further back in time to
 compensate.
 
 Below the queue, a **live build-log panel** (`#rebuild-live-log`,
-`renderRebuildLiveLog`) shows the currently-running rebuild's output
+`renderRebuildLiveLog`) shows the currently running rebuild's output
 inline — collapsible, with a live/ok/fail badge and a `↓ raw`
 download. It's keyed to the first `Running` node (in wire order)
 whose `payload.data.build_log_id` is set — read from the `onUpdate`
@@ -365,7 +365,7 @@ Provision a single per-agent GitHub personal access token (see
 [`docs/integrations/github.md`](../integrations/github.md) for the injection + `gh`/git-push
 mechanics). No login flow — the operator pastes an existing PAT for a
 dedicated bot account, with a security-warning banner (dedicated account +
-minimally-scoped token) and a link to
+minimally scoped token) and a link to
 [github.com/settings/tokens](https://github.com/settings/tokens).
 
 Status reads `GET /api/github-account?agent=<name>` →
@@ -550,7 +550,7 @@ body textarea that expands on focus, datetime-local pre-filled
 to 5 minutes from now, mini d/h/m/s number inputs (blank or
 all-zero = one-shot), description). Click `＋` to POST to
 `/api/schedules` as JSON (or `⌫` to clear the half-filled row);
-carry-state preserves partially-typed inputs across re-renders. The tab pill shows the count of active
+carry-state preserves partially typed inputs across re-renders. The tab pill shows the count of active
 schedules (at least one live target not yet cancelled).
 Refreshed on tab activation and after each submit/cancel. Backed by
 `GET /api/schedules`. No backend changes for the table layout
@@ -1268,7 +1268,7 @@ below — some endpoints aren't in it yet.
   `description` / `interval_seconds` clears the field (so a
   recurring schedule flips to one-shot when `interval_seconds`
   is sent as `null`). `targets_add` is replace-on-conflict:
-  re-adding a previously-cancelled target drops the tombstone
+  re-adding a previously cancelled target drops the tombstone
   and the target starts fresh (operator intent on re-add =
   "this target is active again"). `targets_remove` delegates
   to the same path as `cancel_targets` — tombstones preserve