Align frontend subtree linkage under guardex#175
Merged
Conversation
…adata The frontend compatibility fallback was already published in the standalone frontend repo, but parent guardex still had unstaged subtree drift. This commit records the same lockfile/node-version metadata in the parent tree so guardex tracks frontend state consistently. Constraint: guardex uses tracked frontend subtree plus mirror workflow, not submodule wiring Rejected: Convert frontend to git submodule | conflicts with documented mirror-subtree model in README Confidence: high Scope-risk: narrow Reversibility: clean Directive: For frontend runtime metadata updates, keep both standalone frontend repo and parent frontend subtree in sync Tested: git -C frontend status --short --branch Tested: npm run lint (frontend) Tested: npm run build (frontend) Not-tested: GitHub Actions mirror workflow run after this parent push
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
Verification
Notes