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/process/pr-review-gate.md

@@ -38,6 +38,8 @@ independently.
 
 ## What arming automerge actually means
 
+<!-- vale write-good.Passive = NO -->
+
 Automerge isn't "no human ever looked at this." Whoever arms it has
 already judged the PR sound at a coarse level — the signal it sends is
 roughly _"apart from maybe minor tweaks a reviewer can still catch,
@@ -46,6 +48,8 @@ already happened. No large changes are expected to surface after
 that point — a reviewer's job past that point is to flag it if one
 does, not to assume none ever will.
 
+<!-- vale write-good.Passive = YES -->
+
 The practical consequence for a reviewer: on a repo where someone with
 write access may already have armed automerge before your review
 lands, a plain `APPROVED` can