[bug] Impact radius analysis overestimates affected files for Vue component changes

[1109138797]

Problem Description

When analyzing the impact radius of a Vue single-file component change, the tool reports an overly broad scope.

Scenario:

• Modified file: CustodianAccount.vue (a child component)
• Expected affected files: Only the parent component that directly imports it (BankAccount.vue), plus maybe router config (~1-3 files)

Actual output:

• Direct impact: 10 nodes ✅
• Indirect impact: 143 nodes ❌
• Affected files: 83 files ❌

The tool seems to be propagating dependencies in the wrong direction. Modifying a child component should NOT affect unrelated utility components (AmPagination, AmButton), service layer files (api.service.ts), or architecture layer files (App.vue, main.ts).

Expected vs Actual

	Expected	Actual
Affected files	1-3	83
Indirect nodes	0-5	143

Additional Context

• Framework: Vue 3 with TypeScript
• File type: .vue single-file component
• Tool version: v2.3.2

Suggestion

The "blast radius" analysis should distinguish between:

• Callers (files that import this component) → should be included ✅
• Callees (files this component imports) → should NOT be included ❌

Currently it seems to be counting both directions.