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/scheduler/jobq.md

@@ -37,6 +37,8 @@ Each **row** you see in a queue view (the **BU1LDS** page's R3BU1LD QU3U3
 nested under it are that job's steps, in order (occasionally a couple run
 side by side). A step shows one of:
 
+<!-- vale write-good.Passive = NO -->
+
 | Glyph | Meaning                                                 |
 | ----- | ------------------------------------------------------- |
 | `⏸`   | queued, waiting its turn                                |
@@ -47,6 +49,8 @@ side by side). A step shows one of:
 | `⊘`   | cancelled                                               |
 | `·`   | skipped (not needed for this run)                       |
 
+<!-- vale write-good.Passive = YES -->
+
 A step that isn't needed for a given run stays in the graph as `·` rather
 than being absent from it, so the same kind of operation keeps a
 recognizable shape run to run, whichever steps it actually needed.