Consolidate community configuration and independent verified releases - #1
Merged
Merged
Conversation
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.
Shared application improvements previously existed only on the Kingston branch. Move Kingston configuration and unchanged reviewed data into deployments/kingston, keep Exampleville as the neutral starter, and use explicit per-community release pointers so merging shared code validates communities without publishing them.
This also fixes strict security headers on normalized/error routes, keeps crawler-only files out of atomic offline installation, makes Windows/Linux output deterministic, pins deployed source links, restores a generic optional analytics boundary while leaving Kingston collection disabled, and adds the tested static legacy-worker retirement helper and maintenance/licensing documentation.
Validation: npm run check -- --all passed: 54 unit/output contracts and 64 Chromium/Firefox/WebKit browser checks; eight intentional skips cover Chromium-only lifecycle/cold-restart cases. Includes selected Kingston/Exampleville isolation, LF/CRLF artifact equality, no-JavaScript/print, accessibility/mobile/enlarged text, cold offline restart, failed installation, update/multiple tabs, rollback and legacy retirement. Kingston resource JSON is unchanged. Production verification and conditional legacy redirects follow after this merge; private hosting receipts remain outside the repository.