Standardize the supported website deployment path

[jaavid]

Related: #1

What changed

• makes npm run build the canonical Next.js static production build
• makes GitHub Pages workflow use that same canonical build
• classifies Vinext/Wrangler paths under explicit *:sites internal tooling
• documents production ownership, release evidence and rollback
• adds canonical static-artifact CI validation
• separates the legacy Sites Worker test under test:sites

Root cause fixed

The previous rendered-HTML test imported dist/server/index.js, coupling the production gate to the internal Vinext/Sites Worker artifact. The supported Next.js static build correctly produces out/index.html, so the old test failed despite a successful production build.

The production test now validates out/index.html; the Worker-specific test remains available only through test:sites.

Validation

• clean checkout: npm ci — passed
• npm run lint — passed with one pre-existing @next/next/no-img-element warning
• npm test — Next.js 16.2.11 build/typecheck/static export passed; 1/1 static HTML test passed
• GitHub Website CI run بازطراحی روایت محصول و تجربه صفحه اصلی #5 — passed:
  https://github.com/CoreLinkPlatform/website/actions/runs/31103313713

After merge, retain the exact-main Deploy to GitHub Pages run before closing WEB-01.

[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.