Add unresolved import and load inspection

docs/BUILD_PLAN.md

@@ -172,7 +172,7 @@ Each phase has a machine-checkable gate. Do not advance without a green gate.
 | **5** | Completion (keywords, directives, module names, visible declarations, parameters, module aliases, incomplete-expression recovery), rename, find-usages | Tier 4 fixture tests — **done** (84-test suite) |
 | **5a** | Configurable Jai module/import roots and indexed external search scope | Tier 4 settings, resolution, completion, navigation, and find-usages tests — **done** (93-test suite) |
 | **6** | Formatter, code style settings | Formatter round-trip — **done**, formatting all 714 corpus files is idempotent |
-| **7** | Inspections (e.g. `#must` misuse), quick fixes, live templates | Tier 4 + `verifyPlugin` |
+| **7** | Inspections, quick fixes, live templates | Tier 4 + `verifyPlugin` — initial unresolved `#import`/`#load` path inspection implemented |
 | **8** | Optional: run-configuration to invoke the `jai` compiler, parse its error output | Integration test against `~/.local/jai/bin` |
 
 Phase 6's idempotence check (format twice, assert no change) is another
@@ -218,6 +218,6 @@ currently a committed milestone.
    setup, works today), or install a system JDK via Homebrew? I'd default to the
    wrapper.
 
-Phases 0–6 are implemented and verified headlessly. The next decision is
-whether to continue with the optional inspections and compiler integration work
-in Phases 7–8.
+Phases 0–6 are implemented and verified headlessly. Phase 7 has an initial
+unresolved `#import`/`#load` path inspection; additional inspections and
+compiler integration remain optional follow-up work.