Remove legacy Pages site - #39
Merged
Merged
Conversation
0x0bug
marked this pull request as ready for review
July 21, 2026 22:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
site/tree now maintained in0x0bug/wdt-sitewdt-sitecheckout fixture instead ofsite/run.ps10x0bug/wdt-siteWhy
Production
https://wdt.digital/is now served by0x0bug/wdt-site. Keeping another site copy and Pages workflow in the WDT code repository creates drift and an obsolete deployment path.Impact
WDT retains the canonical
scripts/bootstrap/run.ps1,scripts/Sync-WdtSiteBootstrap.ps1, release checks, diagnostic tests, and all non-site validation. The canonical bootstrap is unchanged at SHA-256fd1f9bc55fe8665c4a2d4706728eff16723a4c62fffd57baeb9c697b35a77bc6.This PR does not change DNS, custom domains, GitHub Pages settings,
wdt-site, WDT Releases,dist/, or the bootstrap logic.Validation
Passed locally in PowerShell 7.5.8 and Windows PowerShell 5.1.26100.8875:
tests/bootstrap-sync.tests.ps1tests/readme.tests.ps1tests/release.tests.ps1tests/validate-ast.tests.ps1scripts/validate.ps1reported zero parser, safety, and module-layout issues in both engines. It returned non-zero only for two pre-existing generated reports underWindowsDiagnosticsReports/; those user files were not modified or deleted.Preflight confirmed that production remains healthy on
0x0bug/wdt-site: apex HTTP 200,wwwredirects to apex, certificate approved, HTTPS enforced, direct GitHub Pages DNS, and production bootstrap hash equal to the canonical file.