Patch Release: Alias-Aware Code Maps

Forgeflow 4.3.6 makes code topology more useful across TypeScript and frontend projects by resolving common alias imports and literal dynamic imports when they point to real source files. The resolver stays conservative: package-style aliases remain external unless Forgeflow can prove a local source target.

Code-Map Resolution

• Reads tsconfig.json and jsconfig.json path aliases, excluding broad catch-all * mappings that can turn package imports into false positives.
• Resolves common @/ and ~/ aliases to the nearest src/ root when the target source file exists.
• Turns literal dynamic imports such as import("@/routes/dashboard") into graph edges when they resolve to source files.
• Keeps non-literal dynamic imports visible as skipped runtime imports.

Downstream Validation

• Dry-run validation against GSD-CIC resolved the remaining aliased lazy route review gaps.
• Needs-review import gaps dropped from 5 to 0.
• Remaining gaps are expected asset/data imports, test fixtures, and non-literal runtime imports.
• Static local edges increased from 7,294 to 9,196, giving agents a richer project topology without adding review noise.