Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document
Next.js Live Cutover
web-next-cutover.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw fileNext.js Live Cutover
This note records the completed transition from the old docs/ entry surface to the new apps/web Next.js export at the repo root.
Current Truth
- The repo root now serves the
apps/webstatic export as the live reviewer-facing surface. docs/remains available as the archive and raw-reference surface.apps/webnow includes:- legacy
?page=compatibility at the root route - curated
/documents/routes for reviewer and trust packets - broad
/viewer/routes for repository markdown parity - The Next.js app supports:
/PrivateDAObase path for GitHub Pages- root-domain export for a future
.xyzdeployment
Export Commands
From repo root:
npm run web:build
npm run web:build:github
npm run web:build:root
npm run web:bundle:github
npm run web:bundle:rootGenerated artifacts:
dist/web-mirror-github/dist/web-mirror-github.tar.gzdist/web-mirror-root/dist/web-mirror-root.tar.gz
Completed Cutover Checks
The root publication now verifies:
//command-center//proof//proof/?judge=1/documents//viewer//security//diagnostics//services//awards/- legacy
?page=entrypoints routing through the Next root surface - reviewer and judge links resolving under the GitHub Pages base path
Remaining Boundary
Do not interpret this completed cutover as a .xyz domain cutover.
What is complete now:
- GitHub Pages root publication from
apps/web - legacy query compatibility through the new root
- curated
/documentsroutes - broad
/viewerparity for repository markdown
What remains optional and external:
.xyzDNS and HTTPS mapping- deciding whether
.xyzbecomes the primary production hostname