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/integrations/forge.md

@@ -128,7 +128,7 @@ Forge's own read-state is thus the durable, cross-rebuild record of
 what's been delivered; there is **no persisted cursor**.
 
 **Gotcha:** don't reintroduce a persisted dedup cursor here. A design
-that leaves threads unread and tracks delivery via a separately-persisted
+that leaves threads unread and tracks delivery via a separately persisted
 cursor is fragile — losing that cursor across a rebuild re-delivers the
 agent's entire still-unread backlog as a flood of fresh wakes. Forge's
 own read-state is the only durable record this design needs.
@@ -187,7 +187,7 @@ silently (mark-read without delivery):
 
 `own_login` is fetched at startup via `GET /api/v1/user`. On fetch
 failure the filter degrades open (no filtering) rather than crashing
-the task — a noisy inbox beats a silently-stuck poller — but the fetch
+the task — a noisy inbox beats a silently stuck poller — but the fetch
 is **re-attempted on each poll tick** until it succeeds, so a boot-time
 failure (the forge not yet reachable) self-heals instead of leaving
 self-echo filtering off for the whole process lifetime.

docs/integrations/github.md

@@ -51,7 +51,7 @@ credential-injection path as forge/matrix tokens. See
 ## Security
 
 - Use a **dedicated bot account**, never a human's.
-- Mint a **minimally-scoped PAT** — only the repos/scopes the agent's
+- Mint a **minimally scoped PAT** — only the repos/scopes the agent's
   workflow needs. Agents have passwordless sudo, so a compromised or
   hallucinating agent can act as the account within the token's scopes;
   scope is the real blast-radius limiter, and the container boundary is

docs/integrations/knowledge.md

@@ -70,7 +70,7 @@ each call site.
 
 When a pull actually moves the local clone's `HEAD` (a real change,
 not a no-op — for example the periodic pull finding nothing new), hive-c0re
-broadcasts a short notice to every currently-registered agent's inbox:
+broadcasts a short notice to every currently registered agent's inbox:
 sender `system`, body `[system] /knowledge updated:` followed by a
 `git diff --stat <old>..<new>` summary of what changed (or a generic
 "see the repo" fallback if computing the diff itself fails). This is