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 store

The pipeline stores URL, retrieval time, HTTP status, content hash, authority class, normalized claims, and conflicts. Raw snapshots are operational evidence; pages show the useful conclusion and source card.

03

Correction path

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