Use file url for import path (fixes #9471)

Editor assessment

The config scope earns its place here—import path resolution is a config-domain concern—and the subject is specific, lowercase, and imperative. The notable stylistic wrinkle is the inline issue closure, '(fixes #9471)', wedged between the description and the PR reference; the spec's preferred home for issue links is a footer such as 'Fixes #9471' after a blank line, which keeps the subject a clean description and lets tooling associate the issue reliably. Cramming both references into the header also pushes the line toward 60 characters. The complete absence of a body means the why—presumably Windows or POSIX path handling rejecting relative imports—lives only in the PR. As a fix it correctly signals a patch-level bump. Functional and parseable, but the reference placement is a habit worth unlearning.