docs: make ReliAPI beta claims verifiable

[kiku-jw]

Summary

• add the canonical, Open Graph, and Twitter metadata for the GitHub Pages site
• describe the current self-hosted beta baseline: HTTP/LLM proxying, Redis-backed caching, non-streaming LLM idempotency, and budget guardrails
• remove unsupported production, savings, benchmark, competitor, failover, retry, and circuit-breaker claims
• remove stale JSON-LD/FAQ and Product Hunt creative that repeated those claims
• update current /v1/proxy/* routes, localhost SDK examples, documentation URLs, and a working Compose-based self-hosting path

No reliability code or runtime behavior is changed. Real retry/circuit and HTTP idempotency defects remain tracked in #26 and #27.

Verification

• make lint — pass
• targeted CI suite — 54 passed
• inline JavaScript syntax and DOM-id references — pass
• exact title/description/canonical/H1 gates — pass
• git diff --check — pass

Risk boundary

The site now labels ReliAPI as beta and does not promise an SLA, managed fallback, exactly-once execution, quantified savings, or performance targets. Stronger claims remain gated on dated end-to-end traces.

Tracked from kiku-jw/kikuai-project-map#13.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.