v0.5.0

A correctness release. Nothing new to learn, several things that were quietly wrong and are now right.

• The watch stopped crying wolf. A source counted as deprecation news if a line held a
  deprecation word or a date. Provider pages stamp themselves daily, so every watched page looked
  like a shutdown announcement every morning: one issue a day, each claiming twenty-odd sources had
  changed, when the lines it had matched were Last updated 2026-10-01 UTC. and bare dates. A date
  on its own is no longer a signal — it is what a page prints when it reprints itself. A date
  carried alongside anything else still is, because a table row of model and date is how most
  providers actually publish a shutdown. The watch now keeps one rolling issue it rewrites, instead
  of opening one a day, and a second run on the same day updates the existing one.

• Records expire when their date arrives. Five records crossed their effective dates between
  September 28 and 30 while still marked active, which the validator correctly refuses — a shutdown
  that has already happened is not pending. CI had been red for three days with no commit to blame,
  and the warning was real but buried inside the daily noise above. Both halves are fixed: the
  records are expired, and the signal that would have surfaced them is legible again.

• Six new records, and the fixtures that prove them. Four Gemini 3.8 preview deprecations —
  tts, lite-tts, live and live-extended-thinking, shutdown dates still pending — plus the Shopify
  POS staffMemberId removal and the Theme CLI 3.83.x password-store cutoff. The knowledge base is
  now 315 change records across 27 providers, with 113 fixtures, and validate reports no errors.

• The site says what it actually does. Every built feature is named, linked and presented as
  available rather than coming-soon. The Teams page links the GitHub App's install page directly,
  explains what an ingest token is and when you need one, and says why Send a test is unavailable
  instead of simply disabling it.

• A documentation claim that was the wrong way round. docs/08-features.md said the fix
  dispatch carries "the evidence with snippets". It carries structural locators only — path, line,
  column — and deliberately so: that payload crosses into another repository's CI, and the snippet
  is attacker-controlled text when the scanned repository is public. The code was already right;
  the docs would have invited someone to reintroduce the snippets.

Binaries for Linux x64, macOS arm64 and Windows x64, with checksums.txt. Each one is smoke-tested
outside the repository before publication and must report its own version, which is the check that
caught a release claiming to be its predecessor once before.