Problem
The authoritative type checker cannot resolve quoted Home imports that already include a source extension. For a kernel entry at src/main.home, an import such as import "core/kernel_init.home" as kernel_init is searched as src/core/kernel_init.home.home, so home build src/main.home --kernel fails before it can validate the kernel corpus.
Evidence
Against current origin/main, running the Home compiler on the home-os kernel entry reports Cannot resolve import 'core/kernel_init.home': FileNotFound plus 130 more import errors. The parser's module resolver understands file-like imports, but TypeChecker.resolveModulePath independently appends .home to every path and resolves package roots rather than the importing file's directory.
Scope
- Resolve a single quoted file path relative to the importing source file.
- Preserve
.homeand.hmextensions instead of appending another extension. - Keep package-style imports and their existing fallback order unchanged.
- Add a kernel-shaped regression fixture and exercise it through the authoritative checker.
Acceptance criteria
import "core/kernel_init.home"fromsrc/main.homeresolvessrc/core/kernel_init.home.- Existing package-style import tests remain green.
- The home-os kernel corpus advances past its root import-resolution failures.
Links
Blocks the remaining kernel-corpus acceptance item in #787. Part of #814.