[WEB-02] Align product claims with implemented, beta, and planned capability status

[jaavid]

Background

CoreLink is managed as one product across multiple implementation boundaries. This work is owned by website under EPIC-01.

Problem

The public website must not imply that scaffolded, experimental, beta, or planned capabilities are already supported product functionality.

Goal

Align every material website claim with the authoritative capability inventory and make maturity, support, and release status reviewable across repositories.

Parent

• Primary Product Epic: EPIC-01
• Backlog ID: WEB-02

Scope

• Reconcile website claims with runtime, contract, SDK, documentation, device-support, deployment, and release evidence.
• Distinguish Scaffold, Experimental, Alpha, Beta, Stable, Deprecated, and Planned status consistently.
• Link material claims to an authoritative repository or product-planning source where practical.
• Define an owner and review path for future claim changes.
• Retain acceptance evidence for the Foundation gate.

Out of Scope

• Implementing missing runtime capabilities in this Issue.
• Treating copy changes alone as proof that the underlying capability is supported.
• Duplicating repository roadmaps or creating an independent website roadmap.

Acceptance Criteria

• A current authoritative capability inventory is identified and linked.
• Material website claims are mapped to implemented evidence or explicitly marked by maturity/status.
• API, SDK, device compatibility, deployment, security, and production-readiness claims are reconciled.
• Unsupported or ambiguous claims are removed or qualified.
• Ownership, review cadence, and exception handling are explicit.
• The deployed website is checked and evidence is linked to the parent Epic.

Technical Notes

Website PR #5 materially improved product wording and status clarity, but merge completion is not equivalent to acceptance. Closure requires reconciliation against actual repository and release evidence plus validation of the deployed result.

Dependencies

• Active prerequisite: Maintain and verify the current cross-repository capability inventory.
• Blocks: Reliable public product positioning, Foundation governance acceptance, and downstream trust/release information in WEB-03.
• Cross-repository: Link concrete affected Issues; do not duplicate implementation.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Feature
• Priority: P0
• Product milestone: Foundation
• Domains: website, governance
• Area: frontend
• Complexity: L
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:feature

Definition of Done

• Acceptance criteria demonstrated.
• Required reviews and retained evidence pass.
• Organization and repository links are updated.
• Security and policy implications are reviewed.
• Documentation and release notes are updated where applicable.
• Pull request or configuration change is linked.

[jaavid]

Evidence update — website PR #5

PR #5 (بازطراحی روایت محصول و تجربه صفحه اصلی) materially advances this Feature:

• product and SDK maturity claims were clarified;
• device compatibility language was made more defensible;
• product narrative, CTA hierarchy, metadata, accessibility behavior, and the design audit were updated;
• npm run lint and npm run build:github passed.

This is implementation evidence, not yet full Feature acceptance. Keep WEB-02 open until the updated public claims are reconciled against the current capability inventory and reviewed in the deployed production page. Link: #5