docs: suppress reviewed write-good.Passive false positives

133 hits across 38 files, all previously classified during #4548's sweep
and deliberately left un-rewritten (predicate-adjective state/necessity
description, design-intent idiom, structural/type-description idiom,
no-single-actor topology claim, parallel-triple exception, vale
substring-match artifact — see hyperhive#4548's per-PR bodies for the
per-hit reasoning).

Wraps each one in a scoped <!-- vale write-good.Passive = NO/YES -->
pair (the supported mechanism — TokenIgnores has a known offset-drift
bug) rather than a blanket per-file or per-rule silence, so a *new*
passive-voice hit anywhere in these files still fails once the rule
gates CI (next commit). Table/list false positives (docs/swarm/credentials.md's
renewal-table cells) wrap the whole block, not each cell.

Part of #4546.

docs/web-ui/design-guide.md

@@ -45,6 +45,8 @@ home.js`, is the reference example — currently in the dashboard
 
 ## Motion
 
+<!-- vale write-good.Passive = NO -->
+
 **General rule, not case-by-case: every non-essential CSS animation
 gates on `prefers-reduced-motion` and pauses when its tab/section is
 hidden.** The dashboard's matrix-rain background (`packages/dashboard/
@@ -54,6 +56,8 @@ though it lives in the dashboard package rather than swarm-ui; every
 future swarm-ui animation follows the same pattern, not just whimsy
 pieces.
 
+<!-- vale write-good.Passive = YES -->
+
 Prefer CSS-driven animation over JS-driven where possible, and avoid
 jarring content swaps (layout shift, hard cuts) where a transition can
 smooth them instead.
@@ -88,6 +92,8 @@ The governing question for anything that shows time-sensitive data:
 needs a refresh story; a value that's silently gone stale with no way to
 tell is worse than one that's visibly stale.
 
+<!-- vale write-good.Passive = NO -->
+
 - **Relative-time labels must actually tick.** A label like "fresh (5s
   ago)" derives from a stored timestamp and re-renders itself on an
   interval — never a value frozen at fetch time that quietly goes stale
@@ -97,9 +103,10 @@ tell is worse than one that's visibly stale.
   1m / …" control the operator sets per page, paused while the tab is
   backgrounded and resumed on foreground.
 - **A refresh must never clobber input the operator is mid-edit on.**
-  Any polling component's contract needs to make this the caller's
-  problem to opt out of correctly, not something the next adopter
-  discovers by shipping a bug.
+Any polling component's contract needs to make this the caller's
+problem to opt out of correctly, not something the next adopter
+discovers by shipping a bug.
+<!-- vale write-good.Passive = YES -->
 
 ## Errors