Repository navigation
feat: enforce local module dependency boundaries - #10
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
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.
Changes
Anatomy can validate directory layout and function exports but cannot currently stop a module from importing another module's private implementation. Add optional
dependenciesrules to Anatomy definitions so a scan can block or warn on direct local imports between path groups.scanAnatomyand the new data-onlycheckAnatomyDependenciesSDK API.import "."), JavaScript-to-TypeScript extension substitution and explicit aliases. Report the rule, original specifier, resolved target and source line/column.Validation
bun run qualitypassed on the rebased branch: structure/source-role audit, types, lint, 427 tests and builds.docs/per repository policy and are not included in the PR.Scope
Rules check direct local edges, including type-only references and re-export statements, without tracing symbols through public barrel chains or judging wrapper semantics. Workspace aliases must be explicit; unmapped bare imports are external. There is no automatic tsconfig inheritance or package-exports discovery, and target code is never executed. Structural/query-only APIs retain their existing scope.
Based on the latest main; the already-merged multi-placeholder implementation is not repeated in this PR.