fix: track exported symbols that use changed internal symbols

[EladBezalel]

Summary

Implements deterministic reference tracking for internal (non-exported) symbols, matching TypeScript's findAllReferences behavior. This partially addresses #16 by implementing the "exported container" concept.

Problem

When an internal function changes, domino would only look for direct cross-file references. Since internal functions aren't exported, it would find 0 references and stop, missing the entire dependency chain.

Example scenario:

// Internal function changes
function getHelperValue() { return 'modified'; }  // ← Changed

// Used by exported component
export function ExportedComponent() {
  return getHelperValue();  // ← Uses internal function
}

// Imported elsewhere
import { ExportedComponent } from './module';

Before this fix: Domino stops at getHelperValue, doesn't detect affected consumers
After this fix: Domino finds ExportedComponent uses it, tracks its references

Solution

Implemented two algorithms from TypeScript's findAllReferences:

1. Exported Container Tracking

When an internal symbol has no cross-file references and isn't exported:

• Find which exported symbols in the same file use it
• Recursively track references to those exported symbols

2. Dynamic Import File Processing

When a file is conservatively affected (dynamic imports with line=0 sentinel):

• Process all exports from that file
• Continue the dependency chain

Changes

src/semantic/analyzer.rs:

• Added is_symbol_exported() - checks if a symbol is exported
• Added find_exported_symbols_using() - finds which exported symbols depend on an internal symbol

src/core.rs:

• Modified process_changed_symbol() to handle internal symbols
• Added special handling for line=0 sentinel (conservatively affected files)

tests/integration_test.rs:

• Added test_internal_function_affecting_exported_component()

Testing

✅ Unit tests pass
✅ New integration test added
✅ Verified to match traf's behavior in real-world monorepos

Related to Issue #16

This PR partially addresses #16 by implementing:

• ✅ Exported container concept - Finding which exported symbols contain references to changed internal symbols
• ✅ Infrastructure for write vs read tracking - Identifying container symbols that reference changed symbols
• ✅ Dynamic import edge cases - Conservative processing of exports from dynamically imported files

Remaining items from #16 (for future PRs):

• Type vs Value distinction (namespace tracking)
• Shorthand property handling
• Explicit write vs read access flags
• Scope-bounded search optimizations

---

This is a critical correctness fix that ensures domino detects all affected projects when internal implementation details change.

[github-actions]

📦 Preview Release Available

A preview release has been published for commit 12d09d3.

Installation

npm install https://github.com/frontops-dev/domino/releases/download/pr-18-12d09d3/front-ops-domino-0.3.4.tgz

Details

• Release: pr-18-12d09d3
• Direct URL: https://github.com/frontops-dev/domino/releases/download/pr-18-12d09d3/front-ops-domino-0.3.4.tgz