fix(affected): unresolved result for TypeScript workspaces — affected_count always 0

[Wolfvin]

Bug

codelens affected returns affected_count: 0 and puts the workspace path in unresolved[] when run against a TypeScript project. The command is essentially a no-op for TS.

Reproduction

# After running scan on a TS workspace:
codelens affected /path/to/ts-workspace "auth/google-auth-cache.ts"

Actual output:

{
  "s": "ok",
  "changed_files": ["auth/google-auth-cache.ts"],
  "unresolved": ["/path/to/ts-workspace"],
  "d": 5,
  "st": {
    "changed_count": 1,
    "unresolved_count": 1,
    "affected_count": 0,
    "affected_test_count": 0,
    "affected_source_count": 0,
    "visited_total": 1
  }
}

Expected: list of files that import (directly or transitively) from auth/google-auth-cache.ts.

Root Cause Hypothesis

The affected command likely does a BFS/DFS traversal on the graph edges, but the edge lookup for TS files is not finding the correct node IDs. Possible causes:

• Path normalization mismatch: the input "auth/google-auth-cache.ts" does not match the node ID format stored after scan (which may use backslashes on Windows, e.g. auth\google-auth-cache.ts, or includes a full prefix)
• The reverse-dependency index (edges pointing to the changed file) is not being built correctly for js_backend file type (TypeScript is classified as js_backend in scan output)
• Node lookup in commands/affected.py returns empty set, so BFS never starts

Investigation Entry Point

1. After scan, query the SQLite graph directly:

   codelens query-graph /path/to/workspace "MATCH (n) WHERE n.id CONTAINS 'google-auth-cache' RETURN n.id LIMIT 5"

   This will reveal the actual node ID format stored for TS files.

2. Compare that format against what affected passes as the starting node key.

3. Fix the path normalization in commands/affected.py so the input filename resolves correctly against the stored node IDs.

Definition of Done

• codelens affected <workspace> "auth/google-auth-cache.ts" returns the correct list of transitively affected files
• Works on both Unix (/) and Windows (\) path separators
• unresolved[] is empty when the input file exists in the scan graph
• Test: add a test in tests/ that scans a small TS fixture, then asserts affected for a known file returns its known dependents

Labels

type: bug-fix exec: sequential

[Wolfvin]

🔄 Taking this issue

Mengerjakan issue ini -- 2026-07-03T08:54:22Z

[Wolfvin]

PR siap review

PR: #184 — fix(affected): resolve TypeScript workspaces + path normalization (closes #176)
Branch: fix/issue-176-affected-typescript
Summary: Fixed codelens affected returning affected_count=0 for TypeScript workspaces. Three root causes: (1) argparse greedy-absorbed all positional args into files leaving workspace=None, (2) lstrip("./") is a char-set strip that corrupted ../foo.ts into foo.ts, (3) path separator mismatch between os.path.relpath (backslash on Windows) and user input (forward slash). Fix: workspace detection heuristic in execute(), while loop prefix strip, forward-slash normalization with norm_to_orig mapping.
Tests: 146 passed, 0 skipped, 0 failed (test_cli + test_doctor + test_affected_command + test_command_registry + test_command_count). 8 new tests in TestIssue176TypeScriptAffected.