fix(reporter): Report file name collisions cause silent overwrites for files with identical basenames

[CodeMaverick-143]

Problem Description

In insight/reporter.py, reports are named purely by os.path.basename:

filename = os.path.basename(file_info["file"]) + ".md"
filepath = os.path.join(output_dir, filename)

In almost every non-trivial project, multiple files share identical basenames across different directories:

• pkg_a/__init__.py and pkg_b/__init__.py
• models/user.py and routes/user.py
• components/Button.tsx and legacy/Button.tsx
• src/index.js and test/index.js

Impact

1. Each subsequent file with the same basename silently overwrites the report generated for earlier files.
2. In summary.md, multiple entries point to the same overwritten file.
3. Historical analysis of overwritten files is permanently lost.

Affected Files

• insight/reporter.py:3-35

Proposed Solution

Option A (Preserve Directory Tree):
Mirror the source directory structure under report/ (e.g. report/models/user.py.md and report/routes/user.py.md).

Option B (Path Sanitization):
Convert relative paths into unique flat filenames (e.g. report/models_user.py.md and report/routes_user.py.md).

[mikemikimike]

Implemented and opened PR #39: #39

The reporter now derives report filenames from the normalized source path, so files with identical basenames from different directories are preserved instead of silently overwriting one another. The summary links use the same unique filenames, and a regression test covers both generated files and links.

Local validation:

• .venv\Scripts\python.exe -m pytest --basetemp=.pytest-tmp-full tests/ -q — 1 passed.
• Explicit py_compile for setup.py and all insight/*.py files — passed.
• import insight — passed.
• Changed-test Ruff and formatting checks — passed.
• Targeted reporter Ruff check, excluding the pre-existing import-order finding — passed.

CI status: the repository CI workflow created run https://github.com/ferrix-lab/Insight-Py/actions/runs/34127649496 for this PR, but GitHub completed it as action_required with zero jobs because this pull request originates from a fork and requires upstream approval. No CI test job executed; this is an external approval gate rather than a test failure. The full-repository Ruff baseline still contains pre-existing findings outside this change.