Changelog

• witness/v1 — signed proof packets (sandbox transcripts, taint paths, version ranges), artifact-bound by sha256, in @reverify/core with a root-signed producer key registry at .well-known/reverify-keys.json.
• @reverify/checker — the open-source reference witness checker: five structural checks, CLI + library. Verify any witness independently, offline. The closed service proposes; the open checker disposes.
• New landing page — dark redesign with the full decay story, and a complete SEO/AISEO surface: JSON-LD entity graph, FAQ schema, dynamic OG images, llms.txt, and AI crawlers explicitly welcomed.
• Blog + changelog launch — this page.

• wpvulnerability checker — WordPress plugin CVE claims with a false-challenge guard (vulns fixed at-or-before the claimed version don't count).
• Adversarial checker for judgment claims — steelmanned counter-arguments, labeled verbalised, framed as contested, never "incorrect".
• Claim idempotency — identical resubmissions return the existing claim (deduplicated: true); the registry compounds instead of forking.
• One active challenge per claim — new episodes require a supported verdict in between. Alert noise solved structurally.
• tested_up_to verdict path — wordpress subjects now currency-checked against latest core; the first three real decay challenges (6.7/6.8/6.9 vs WP 7.0.2) shipped the same day.

First production release. Claim submission (POST /v1/claims), decay-class re-verification, signed challenges with C2 webhook delivery, and the pull fallback. Four checkers live: OSV, endoflife.date, wporg, Context7 (library semantics, Kimi reading pass with grounded-quote enforcement). Dashboard with claims, challenges, and transitions views. First tenant (WPHK) connected the same day.