[WEB-04] Add accessibility, performance, SEO, analytics privacy, and release checks

[jaavid]

Background

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

Problem

The organization does not yet have verified, consistently maintained evidence for this outcome: Add accessibility, performance, SEO, analytics privacy, and release checks.

Goal

Add accessibility, performance, SEO, analytics privacy, and release checks and make the result the authoritative, reviewable baseline for all affected repositories.

Parent

• Primary Product Epic: EPIC-08
• Backlog ID: WEB-04

Scope

• Deliver the stated outcome in website.
• Reconcile affected organization policy, product claims, ownership, security, release, documentation and repository maturity.
• Retain acceptance evidence for the Beta gate.

Out of Scope

• Runtime feature implementation in this Issue.
• Duplicating the product roadmap in repository README files.
• Presenting scaffolds or planned capability as a supported release.

Acceptance Criteria

• Accessibility, SEO, analytics-privacy, and performance checks are implemented in the canonical website test path.
• Canonical metadata, robots.txt, sitemap.xml, keyboard/focus behavior, reduced-motion handling, and release-evidence guidance are implemented.
• Ownership, review and exception paths are explicit and reconciled with the supported WEB-01 release path.
• The final deployed website is validated with retained production deployment evidence.
• Security/privacy and release implications are reviewed against the deployed result.
• Acceptance evidence is linked and the parent Epic is updated.

Implementation Evidence

• PR #8 merged on 2026-08-07 as 28a68581f40b2718ebed6b2bc405baff983a7bec.
• Clean-checkout validation recorded in PR Add website accessibility, performance, SEO, and privacy gates #8: npm ci, lint, Next static build/typecheck, static routes, and 5/5 quality tests passed.
• Merge/local validation is not deployment acceptance; exact deployed-site evidence remains required.

Technical Notes

The old GitHub Actions/Pages incident cited in PR #8 is no longer a valid generic blocker. WEB-04 remains open because production/deployed evidence and release-path reconciliation are still incomplete, not because Actions are assumed unavailable.

Dependencies

• Active prerequisite: WEB-01 must establish and evidence the supported production build/deployment path.
• Implementation completed: PR Add website accessibility, performance, SEO, and privacy gates #8 delivered the static quality gates.
• Blocks: EPIC-08 website release-quality acceptance and reliable production website evidence.
• Cross-repository: Link concrete affected Issues; do not duplicate implementation.
• Current dependency state: See the CoreLink Product organization Project.

Planning Metadata

• Type: Technical Task
• Priority snapshot: P1
• Product milestone snapshot: Beta
• Domains snapshot: website, observability
• Area snapshot: frontend
• Complexity: M
• Created in status: Triage
• Current status and DRI: See the CoreLink Product organization Project.
• Intended repository labels: type:technical-task

Definition of Done

• Acceptance criteria demonstrated.
• Implementation PR is merged and linked.
• Required production/deployment evidence passes and is retained.
• Organization and repository links are updated.
• Security/privacy and release implications are reviewed.
• Parent Epic acceptance record is reconciled.