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/tools/scheduling.md

@@ -17,11 +17,15 @@ cancel.
 
 ### `request_schedule_prompt(targets, body, first_fire_at_unix, interval_seconds?, description?)`
 
+<!-- vale write-good.Passive = NO -->
+
 Queue an operator-approval for a scheduled prompt. On approve,
 hive-c0re fans `body` out to each agent in `targets` at
 `first_fire_at_unix` (Unix timestamp). Recurring when `interval_seconds`
 is set, one-shot otherwise.
 
+<!-- vale write-good.Passive = YES -->
+
 Catch-up clamp: if hive-c0re is down across multiple intervals, only
 ONE delayed fire happens on resume (per recurring schedule). The
 skipped-cycle count surfaces in the per-target `last_result` for
@@ -41,10 +45,14 @@ rows (terminal state).
 
 ### `cancel_schedule(id, targets?)`
 
+<!-- vale write-good.Passive = NO -->
+
 Cancel a schedule. Omit `targets` / pass empty to cancel the whole
 schedule; pass a list to cancel just those recipients (the schedule
 autocancels once every target is gone).
 
+<!-- vale write-good.Passive = YES -->
+
 ### `fire_schedule_now(id)`
 
 Fire a scheduled prompt out of band immediately. Recurring schedules