[WEB-01] Select and document one supported build and deployment path

[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: Select and document one supported build and deployment path.

Goal

Select and document one supported build and deployment path and make the result the authoritative, reviewable baseline for all affected repositories.

Parent

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

Scope

• Inventory the current website build and deployment paths.
• Select one supported production path that is reproducible from a clean checkout.
• Remove, repair, or explicitly classify alternative paths as internal or unsupported.
• Document ownership, release checks, rollback behavior, and evidence expectations.
• Retain acceptance evidence for the Foundation gate.

Out of Scope

• Runtime product-feature implementation in this Issue.
• Duplicating the product roadmap in repository README files.
• Treating a successful repository-specific command as proof that every advertised build path is supported.

Acceptance Criteria

• One production build and deployment path is explicitly designated as supported.
• The supported path succeeds from a clean checkout using documented prerequisites.
• Alternative build paths are removed, repaired, or explicitly marked internal/unsupported.
• Ownership, release checks, failure handling, and rollback expectations are documented.
• Evidence from at least one real deployment workflow is linked.
• The parent Epic is updated with retained evidence.

Technical Notes

npm run build:github has previously succeeded while npm run build was not reproducible in the validation environment because of the generated build/sites-vite-plugin dependency. Merge or local success is not closure evidence until the supported path and its prerequisites are unambiguous.

Dependencies

• Active prerequisite: Complete and verify the current website deployment/tooling inventory.
• Blocks: WEB-04 release checks and reliable website release evidence for EPIC-08.
• 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: P0
• Product milestone: Foundation
• Domains: website, deployment
• Area: infra
• 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.
• 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]

Build-path evidence update — website PR #5

PR #5 verified npm run build:github, but the generic npm run build path still depends on a generated build/sites-vite-plugin file and did not complete in the local validation environment.

This confirms that multiple build semantics still exist and WEB-01 remains open. Closure requires one explicitly supported production build/deployment path, reproducible from a clean checkout, with the alternative path either removed or clearly classified as internal/unsupported. Link: #5

[jaavid]

Deployment-path evidence update — PR #6

PR #6 merged on 2026-08-06 and materially resolves the earlier build-path inconsistency recorded in this Issue:

• npm run build is now the canonical Next.js static production build.
• GitHub Pages uses that same canonical build path.
• Vinext/Wrangler paths are explicitly classified as internal *:sites tooling.
• clean-checkout validation and Website CI passed before merge.

The previous comment about npm run build depending on build/sites-vite-plugin is therefore historical rather than the current implementation state.

WEB-01 should remain open until the exact deployed production/Pages result is retained and reconciled with the Issue acceptance criteria. Merge/CI evidence is necessary but is not itself deployment acceptance.