Fix #648: Wire TsconfigResolver in CLI commands

[kishansaaai]

Summary

This PR fixes the false-positive unreachable_file reports for TS/JS projects using path aliases (like @/components) in CLI commands.

The root cause was that TsconfigResolver was only being wired up during the pipeline ingestion phase. Any CLI command that rebuilt the graph in-memory without this phase (such as dead-code, health, and workspace) would fail to resolve aliases, leaving valid targets with in_degree=0.

Changes:

• Extracted wire_tsconfig_resolver helper function in repowise.core.ingestion.tsconfig_resolver.
• Refactored repowise/core/pipeline/phases/ingestion.py to use the shared helper.
• Added resolver wiring calls right before graph_builder.build() in dead_code_cmd.py, health_cmd.py, and workspace_cmd.py.

Related Issues

Fixes #648

Test Plan

• Tests pass (pytest)
• Lint passes (ruff check .)
• Web build passes (npm run build) (if frontend changes)

Added a dedicated regression test (test_tsconfig_cli_repro.py) that mimics the CLI command's in-memory graph rebuild with a mock @/* alias to ensure it properly connects to its target and suppresses the false unreachability finding.

Checklist

• My code follows the project's code style
• I have added tests for new functionality
• All existing tests still pass
• I have updated documentation if needed

[repowise-bot]

✅ Health: 7.6 (unchanged)
_{5 hotspots · 5 hidden couplings · 5 with fix history · 1 dead-code finding}

⚠️ Change risk: moderate _{(riskier than 41% of this repo's commits · raw 8.4/10)}
This change's risk is driven by:

• more lines added than baseline
• more scattered than baseline

🩹 Review priority _{(files here with the most recent bug-fix history — defects cluster, so review these first)}

• .../commands/dead_code_cmd.py — fixed 3× in the last ~6 months
• .../commands/workspace_cmd.py — fixed 3× in the last ~6 months
• .../ingestion/tsconfig_resolver.py — fixed 2× in the last ~6 months
• .../phases/ingestion.py — fixed 2× in the last ~6 months
• .../commands/health_cmd.py — fixed 2× in the last ~6 months

🔥 Hotspots touched (5)

• .../commands/dead_code_cmd.py — 7 commits/90d, 2 dependents · primary owner: Raghav Chamadiya (94%)
• .../commands/workspace_cmd.py — 11 commits/90d, 7 dependents · primary owner: Raghav Chamadiya (97%)
• .../ingestion/tsconfig_resolver.py — 4 commits/90d, 4 dependents · primary owner: Raghav Chamadiya (97%)

2 more

• .../commands/health_cmd.py — 14 commits/90d, 3 dependents · primary owner: Raghav Chamadiya (99%)
• .../phases/ingestion.py — 7 commits/90d, 3 dependents · primary owner: Swati Ahuja (51%)

🔗 Hidden coupling (2 files)

• .../commands/workspace_cmd.py co-changes with these files (not in this PR):
  • docs/CLI_REFERENCE.md (5× — 🟢 routine)
  • .../routers/workspace.py (4× — 🟢 routine)
• .../commands/health_cmd.py co-changes with these files (not in this PR):
  • .../health/engine.py (5× — 🟢 routine)
  • docs/CODE_HEALTH.md (5× — 🟢 routine)
  • .../refactoring/__init__.py (4× — 🟢 routine)

💀 Dead code (1 finding)

• 💀 .../phases/ingestion.py _parse_one (confidence 0.65)

---

📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-03 20:27 UTC
_{Silence on a single PR with [skip repowise] in the title · Per-repo toggle on repowise.dev/settings?tab=bot}

[swati510]

The dead-code and health wirings are in place. Those are two of the three CLI commands that build a GraphBuilder, and both read include_submodules/include_nested_repos from state before the call.

The blocker is the third site. workspace_cmd.py:685 passes include_submodules=… and include_nested_repos=… to _generate_docs_for_added_repo, and that function takes neither parameter. It raises NameError and crashes repowise workspace add for every repo. The error fires before the TS-language guard, so even non-TS repos hit it. That function never resolved those flags, so calling wire_tsconfig_resolver(graph_builder, repo_path) with the defaults matches its existing behavior.

A test that invokes the workspace path would catch this. The current regression test only exercises the helper on its own. Once that's fixed and green, this is ready.