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/shape.md

@@ -110,6 +110,8 @@ shapes the renderers call:
 - `api.fromHistory` — `true` while backfill replay is running; renderers
   use it to suppress live-only side effects.
 
+<!-- vale write-good.Passive = NO -->
+
 **`create(opts)` options:** `logEl` (log container element), `streamUrl`
 (SSE endpoint), `historyUrl?` (optional replay endpoint — skipped if absent
 or if the fetch fails), `renderers` (kind→fn map; unknown kinds fall through
@@ -126,6 +128,8 @@ than captured once — lets a page default otherwise-collapsed panels open
 per a live browser-local preference; renderers that force a row open
 regardless, for example message-bearing tool_use, are unaffected either way).
 
+<!-- vale write-good.Passive = YES -->
+
 **Sticky-bottom + snap animation.** `stickToBottom` is the
 operator's intent: true means "keep snapping to bottom on every
 mutation," false means "I scrolled up, leave me alone." The flag
@@ -238,6 +242,8 @@ checkboxes use a lighter snapshot-then-restore pattern (snapshot
 before `replaceChildren`, restore after) since they're single
 values rather than per-row caches.
 
+<!-- vale write-good.Passive = NO -->
+
 **`<details>` open-state preservation:** any collapsible element
 tagged with `data-restore-key="<stable-key>"` survives the
 refresh. `snapshotOpenDetails()` walks managed sections before
@@ -250,6 +256,8 @@ dashboard's own answered-questions history list was the only
 nothing to restore, kept in place for the next collapsible section
 that needs it rather than ripped out along with their one caller.
 
+<!-- vale write-good.Passive = YES -->
+
 **Side panel (dashboard):** long content opens in a drawer that
 swipes in from the right — a singleton `#side-panel` with a
 titled header, a close button, and a scrollable body. Closes on