01

Authority order

Maintainer project/release pages come first for identity and compatibility. Official platform documentation supports installation behavior. Community reports create investigation tasks but do not become confirmed fixes by repetition.

02

What we record

For each source we keep its URL, check time, HTTP status, content hash, source type, useful facts, and any conflicts. The public page shows the conclusion and the link readers can check for themselves.

03

Correction path

When a maintainer changes a file or warning, the weekly diff identifies affected pages. A material correction updates the content and changelog; a fetch failure does not change the factual record.