[Phase 5] Build production GitHub Actions and static deployment #36

New issue

Closed

opened 2026-07-25 21:57:44 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:57:44 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #5, #31, #33, #34, #35

Scope

Add production workflows for validation, static build, artifact retention, and deployment.
Deploy the main branch to GitHub Pages with correct repository-base routing and service-worker scope.
Produce a downloadable static-site archive for alternate hosting.
Add preview artifacts for pull requests without publishing untrusted code to the production site.
Verify cache headers, content types, CSP delivery strategy, source-map policy, and rollback procedure.

Acceptance criteria

A tagged or approved main-branch build deploys reproducibly.
Direct navigation and refresh work under the repository subpath.
The deployed PWA passes smoke, offline, and update checks.
Failed validation cannot publish production assets.
A documented rollback can restore the previous known-good artifact.

Parent: #2 Depends on: #5, #31, #33, #34, #35 ## Scope - Add production workflows for validation, static build, artifact retention, and deployment. - Deploy the main branch to GitHub Pages with correct repository-base routing and service-worker scope. - Produce a downloadable static-site archive for alternate hosting. - Add preview artifacts for pull requests without publishing untrusted code to the production site. - Verify cache headers, content types, CSP delivery strategy, source-map policy, and rollback procedure. ## Acceptance criteria - A tagged or approved main-branch build deploys reproducibly. - Direct navigation and refresh work under the repository subpath. - The deployed PWA passes smoke, offline, and update checks. - Failed validation cannot publish production assets. - A documented rollback can restore the previous known-good artifact.