Documentation: ranking notes

Only one PR in this category carries leverage over other work (#36101, an error-handling policy that several stalled design discussions reference), so it is the sole P2; the NACKs on its specific recommendation do not lower its priority since the decision itself is what is blocking. The P3 block is homogeneous missing-documentation work and is ordered by how often the undocumented behavior is hit by users/integrators, then by developer-facing consolidation. Nothing here is P1: no document was found that would lead a user into fund loss, backup loss, or a security-relevant misconfiguration.

• #35518 (-*notify shell commands) and #35480 (ZMQ during reorgs/evictions) are the same author documenting undocumented notification semantics for external integrators; they are near-equivalent in consequence and belong in the same band — review #35518 first since it addresses an open documentation issue about a wrong user assumption, then #35480.
• #35858 (new doc/privacy.md) overlaps in content with existing doc/tor.md and doc/i2p.md and with #35395's consolidation pattern; if both land, the duplicated text in the per-network docs must be removed consistently, so #35858 should not be merged without checking that the source docs are trimmed.
• #30361 proposes relaxing the developer-notes LogError rule while reviewers prefer fixing the ~half of non-fatal call sites in code; the underlying doc/code mismatch is real but the resolution may belong in a code PR, so a decision on direction should precede review of this text.
• #35890 is the only P4 that actually fixes instructions that break when followed (append vs overwrite); it sits at the top of P4 and should be reviewed before the purely cosmetic #36155.

This pass by claude-opus-5 on 2026-09-17 saw every PR in the category at once and checked the bands given to each PR alone against each other, ordered the PRs, and noted chains and overlaps. Back to the category.