Changes

Attribution compares a sha256 of the readable text extracted from the page behind the old value with the one behind the new — not a hash of the raw response. Vendor documentation pages carry per-request build ids and nonces, so their bytes differ on every fetch while the pricing content is identical; hashing the bytes would publish every price move on those sources as a repricing. Two limits, stated because they cut against us. An edit confined to the markup does not change the hash, so a value that moved on such a page is filed as reading even though the page did change. And a page with too little extractable prose to compare — a JSON API such as OpenRouter’s feed — falls back to hashing the raw body, where the noise problem returns in full and a cosmetically re-serialised feed reads as vendor. The fallback is deliberate: hashing the empty string would mark every such source permanently unchanged and turn its real repricings into reading. Attribution also does not distinguish a correction from a regression; both are reading, and telling them apart takes a human. See METHODOLOGY §9.