Fix: Resolve modules paths relative to project root #6
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.
Modules were being resolved relative to each file's grandparent directory, causing the same file to appear under different module names (e.g., 'auth' vs 'workspace.auth'). This led to false positives in scattered functionality detection where imported functions were counted as local definitions.
This PR adds _find_project_root to detect the actual project root by scanning upwards for project indicators (pyproject.toml, setup.py, etc.) and resolves all module names relative to this consistent root.