Patch Release: Import-Gap Triage

Forgeflow 4.3.4 turns raw static import-gap counts into categorized guidance for maintainers and agents. The goal is to distinguish likely expected topology gaps from gaps that deserve review.

Import-Gap Triage

• Code map now groups import gaps into likely expected gaps and gaps needing review.
• Categories include asset/data imports, dynamic package imports, runtime dynamic imports, local/alias dynamic imports, source suffix resolution gaps, alias resolution gaps, local missing modules, and test fixtures.
• Each category includes an action hint so users can decide whether to inspect project code, update resolver support, or treat the gap as expected static-graph noise.

Where It Appears

• /forgeflow-code-map shows detailed triage categories and examples.
• /forgeflow-trends --refresh carries the same expected vs needs-review rollup.
• /forgeflow-smoke includes the triage totals in the code-map check.
• /forgeflow-report includes import-gap triage in project trends.
• Context packs include the triage summary so review agents receive the signal.

Downstream Validation

• Verified on GSD-CIC after /update-forgeflow pulled commit 46141ac.
• GSD-CIC import gaps were split into 23 needing review and 17 likely expected.
• The two local missing icon barrel exports remained clearly surfaced as worth verifying, while source suffix resolver limitations were grouped separately.