chore(tooling): add structural lint guardrails#170
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.
Issue
Structural architecture conventions were documented but not fully enforced by blocking checks. Runtime/test warning paths also produced noisy output, making failures harder to spot.
Solution
sgconfig.ymland make structural violations faillint:structure.Screenshots
N/A — tooling, guidance, and runtime warning-path changes only.
Testing
Added structural-lint rule fixtures covering valid and invalid examples for each new ast-grep rule.
Added regression coverage for warning-path behavior around GLTF preloading, Three.js test setup, haptics, and interaction prompts.
Validated the full local quality gate before pushing.