Align website claims with implemented capability maturity

[jaavid]

Related: #2

What changed

• adds the missing TypeScript prerelease SDK and corrects Python from Planned to Prerelease Alpha
• marks Java/CLI/MCP/mock as Scaffold / Planned
• replaces unsupported 250+/15000+ support-style claims with current contract/SDK evidence
• makes device/protocol lists evaluation examples rather than blanket support claims
• qualifies White-label, capability-layer and Media maturity
• records an evidence-backed public capability inventory
• validates claims in the canonical static out/index.html artifact

Validation

• local lint: passed with one pre-existing @next/next/no-img-element warning
• Next.js 16.2.11 build:github: build/typecheck/static export passed
• rendered static HTML test: 1/1 passed
• GitHub Website CI run [WEB-04] Add accessibility, performance, SEO, analytics privacy, and release checks #4 — passed:
  https://github.com/CoreLinkPlatform/website/actions/runs/31103307732

Merge order

Keep this PR Draft until WEB-01 / PR #6 is merged. WEB-01 owns the canonical website CI and build-path change. After #6 lands, revalidate this PR against updated main, then merge and retain deployed-site evidence before closing WEB-02.

[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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.