Skip to content

Align frontend subtree linkage under guardex#175

Merged
NagyVikt merged 1 commit intomainfrom
agent/codex/link-frontend-under-guardex
Apr 20, 2026
Merged

Align frontend subtree linkage under guardex#175
NagyVikt merged 1 commit intomainfrom
agent/codex/link-frontend-under-guardex

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Summary

  • add \ (Node 22 hint)
  • update \ to lockfile v2 for broader detector compatibility
  • keep parent guardex frontend subtree aligned with already-published frontend compatibility patch

Verification

  • git -C frontend status --short --branch (clean)
  • npm run lint (frontend)
  • npm run build (frontend)

Notes

  • This follows the repo's documented subtree+mirror model (not submodule conversion).

…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
@NagyVikt NagyVikt merged commit 1def551 into main Apr 20, 2026
@NagyVikt NagyVikt deleted the agent/codex/link-frontend-under-guardex branch April 20, 2026 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant