chore: tidy up readme and docs

Author: m0n0x41d

README.md

@@ -15,90 +15,6 @@ Instead of jumping to conclusions and solutions, your AI generates competing hyp
 No more archaeology in chat history. Decisions live in `.quint/` —
 queryable, auditable, yours.
 
----
-
-### Example: Handling Payment Confirmations
-
-Your checkout works. Stripe charges the card.
-But three weeks later, finance finds $12,000 in "ghost payments" —
-customers charged but never got access.
-
-The webhook endpoint returned 200. Logs look clean.
-What went wrong?
-
-#### Without Quint
-
-Your AI suggests: *"Just add a webhook endpoint that activates the subscription"*
-
-You ship it. It works in testing. Production looks fine.
-
-Until it doesn't. Webhooks fail silently. Your endpoint timed out during a DB hiccup. Stripe retried, you processed it twice. A network blip ate three webhooks completely.
-
-Now you're debugging production with no record of why you built it this way.
-
-#### With Quint
-
-```bash
-$ q1 hypothesize "handle stripe payment confirmation"
-```
-
-AI generates competing approaches:
-
-| # | Approach | Risk | Recovery |
-|---|----------|------|----------|
-| H1 | Webhook-only | Silent failures, no detection | None without manual audit |
-| H2 | Webhook + sync processing | Timeout = lost event, retries = duplicates | Stripe retry (3 days) |
-| H3 | Webhook → Queue + Polling backup | Complex, two code paths | Self-healing |
-
-```bash
-$ q2 verify
-```
-
-AI checks each hypothesis:
-- **H1 fails:** "No mechanism detects missed webhooks"
-- **H2 partial:** "Idempotency key needed, still misses network failures"
-- **H3 passes:** "Polling catches what webhooks miss, queue handles spikes"
-
-```bash
-$ q5 decide
-```
-
-```
-Decision: H3 — Async queue + 15-min polling reconciliation
-
-Rationale:
-- Webhook acknowledges immediately (200 in <100ms)
-- Background job processes with idempotency check
-- Polling job catches silent failures
-- Accepted tradeoff: 15-min max delay for edge cases
-
-Evidence: Stripe docs recommend polling backup.
-Review trigger: If webhook success rate drops below 99%
-```
-
-#### 3 weeks later
-
-Finance asks: *"Why do we poll every 15 minutes? Can we remove it?"*
-
-```bash
-$ q query "payment confirmation architecture"
-```
-
-```
-Decision: 2024-01-15 — H3 selected over webhook-only
-
-Key evidence:
-- Stripe admits webhook delivery "not guaranteed"
-- Polling catches ~0.3% of transactions (measured)
-- Removing polling = ~$400/month in silent failures
-
-Recommendation: Keep polling. Document in runbook.
-```
-
-**The decision context survives. No archaeology needed.**
-
----
-
 ## Quick Start
 
 ### Step 1: Install the Binary