P2 after comparing with the other PRs here (assessed alone as P3): Raised to P2: documents a privacy feature's prerequisites and scope limits, where absent/fragmented guidance can lead operators to over-trust private broadcast.
P3 because it consolidates fragmented and duplicated privacy advice across multiple network docs
Helps node operators understand the prerequisites and scope limitations of private transaction broadcast
P2 after comparing with the other PRs here (assessed alone as P3): Raised to P2: corrects privacy-relevant documentation (persistent I2P identity exposure, wallet txs not covered) that could otherwise lead operators to a wrong conclusion; same consequence class as #35858.
P3 because it corrects misleading documentation about persistent I2P address exposure
The change is marginal and only affects operators checking I2P privacy behavior
P3 after comparing with the other PRs here (assessed alone as P4): Raised to P4->P3: the current text is factually wrong against the codebase (58/129 LogError calls fatal, per #30348) and keeps re-triggering review debates, which is more than cleanup.
P4 because it only loosens internal developer guidance for logging conventions
It does not correct misleading user-facing documentation or affect node behavior
Wait for the author to respond to multiple standing objections on whether to close this pull request
Documentation as the primary change: developer notes, design documents, build and usage docs, release notes, RPC help text when the change is to the text rather than the interface, and code comments when a PR consists mainly of them. The Docs label is a strong prior.
Not docs: a code change that also updates its docs (that area).
What matters here
Wrong documentation first: text that would lead a user or developer to do the wrong thing, especially around security, backups, and configuration. Then missing documentation for something users hit often or that a design decision depends on (a design doc that unblocks a project counts as leverage). Then release notes completeness. Then clarity improvements to frequently read pages. Then typo and style fixes, which are P4 unless they fix a meaning.
Every band, state, and summary on this page is model output against a written category definition, shown with its rationale. It is an unofficial tool and does not speak for the project. Click a row to expand it. The category definition lives in ryanofsky/prio-bitcoin/categories/docs.md; pull requests that improve it are welcome.