Lead with verification in the README

[Shakargy]

Why

The README still opened as a concept scanner (the v0.1 identity) while the sharpest thing DevTime does is now verification. Two concrete problems:

1. The hero promised "helps a codebase explain itself from evidence" - vague to a first-time visitor.
2. The 60-second path ended on dtc concepts, which returns 0-2 concepts on many real repos. dtc verify now returns a concrete finding on nearly any repo with routes, so we were leading people with the weaker command.

Changes

• Hero: "DevTime verifies what your repository can actually prove", opening with the stripe/webhook.ts stub that looks like proof and isn't
• Hero animation is now the verify lifecycle (SUPPORTED → CONTRADICTED → STALE); the scan tour moves down to illustrate the concept layer, so both demos earn their place
• Quickstart ends with dtc verify, states what the demo repo actually returns, then points the reader at their own repo
• Verify section moved above the fold with the five statuses and a real contradiction example; freshness and diff impact summarized
• Capability list leads with verification and freshness
• Dropped stale "V0" phrasing

Verification

Every output quoted in the README was captured from the published 0.5.0 package in a clean environment, not written by hand: billing SUPPORTED, JWT SUPPORTED, 2 of 3 routes have a referencing test.

Docs only. No code changes.