feat: report external tooling drift in sync checks - #51
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.
What changed
Adds a read-only external tooling checker for gh-axi, lavish-axi, chrome-devtools-axi, and no-mistakes. It compares npm CLI versions or the authoritative no-mistakes GitHub stable release and reports safe-anytime versus needs-quiet-fleet coordination.
Wires the checker into syncfirstmate check mode and the weekly heartbeat, with focused behavioral coverage.
How to test
The no-mistakes pipeline was explicitly skipped; independent review is requested.
Security / PHI check
Read-only tooling checks only. No secrets or PHI added, no installs or daemon updates performed.