Repository navigation
Clarify tri-27 snapshot ownership and scope Queen checks - #2
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.
The apex publisher still builds
gHashTag/trinity@main/apps/website, while tri-27 described itself as the live site and treated its extracted Queen page as production acceptance. This makes tri-27's ownership explicit: an extracted snapshot and design lab, with the live source and the verified publisher revision linked in both READMEs. The source table and publishing diagram now match that relationship; a future cutover requires a separate explicit migration.The old page/recording comparison is retained as
npm run check:queen-snapshotwith a visible scope label. It leaves default CI and pre-push hooks, and the former six-hour drift workflow becomes a manual, offline snapshot check with read-only permissions. It no longer creates production-contract incidents from this frozen page. The production publisher, Trinity's acceptance checks, and all application code remain untouched. This does not resolve the supervisor outage tracked in #1.Validation: the optional snapshot check passes all 25 fields; the English-only ratchet passes; both edited JavaScript files pass
node --check; all three changed YAML files parse; package/workflow/hook/fixture references agree;git diff --checkpasses. No UI rendering code changed, so a full site build was not run locally; normal CI still builds and renders the snapshot.References gHashTag/trinity#974.