ci: anchor demo freshness to shared main - #23
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
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.
Summary
mainWhy
PR #22 passed its three-platform matrix, but the exact merge-commit integrity job could not resolve capture commits that existed only on the pre-squash branch. The shared checkpoint is the tree-identical, validated merge commit from PR #22; original capture SHAs remain recorded and are not rewritten.
Validation
Validated commit:
ad9022d5246d186fa46916798d0dc112e53e61f6node scripts/demo-freshness-audit.mjs --target HEAD --strictnode scripts/documentation-consistency-audit.mjsnpm run smoke:governancegit diff --checknpm install && npm run release:check:macos— passed on macOS arm64, Node v24.14.0 (131.0s)Risk
Release-governance behavior only; no product runtime, capture schema, package contents, or Viewer behavior changes.