"unresolved extern crate" for rustc crate dependencies while workspace is loading

When opening the Miri workspace with the src/lib.rs file open, I get "unresolved extern crate" error while RA is loading:

Those errors disappear if I wait a while and then switch to a different file in vscode. However, it is quite confusing to see these errors during loading since it looks like something permanent, but is apparently just an artifact of the crate graph not being fully loaded yet.

rust-analyzer version: rust-analyzer version: 0.3.2519-standalone [/home/r/.vscode-oss/extensions/rust-lang.rust-analyzer-0.3.2519-linux-x64/server/rust-analyzer]

rustc version: rustc 1.89.0-nightly (255aa2208 2025-06-19)

editor or extension: VSCodium, extension 0.3.2519

relevant settings:

{
    "rust-analyzer.rustc.source": "discover",
    "rust-analyzer.linkedProjects": [
        "Cargo.toml",
        "cargo-miri/Cargo.toml",
        "miri-script/Cargo.toml",
    ],
    "rust-analyzer.check.invocationStrategy": "once",
    "rust-analyzer.check.overrideCommand": [
        "./miri",
        "clippy",
        "--message-format=json",
    ],
    "rust-analyzer.cargo.extraEnv": {
        "MIRI_AUTO_OPS": "no",
        "MIRI_IN_RA": "1",
    },
    // Contrary to what the name suggests, this also affects proc macros.
    "rust-analyzer.cargo.buildScripts.invocationStrategy": "once",
    "rust-analyzer.cargo.buildScripts.overrideCommand": [
        "./miri",
        "check",
        "--message-format=json",
    ],
}

repository link (if public, optional): https://github.com/rust-lang/miri/

Reproduce the report with the Miri workspace, opening src/lib.rs in VSCodium while rust-analyzer loads and using the linked-project and override-command settings shown. Trace how unresolved extern crate diagnostics are produced during workspace loading. Done means transient loading errors no longer appear as misleading persistent diagnostics, while genuine diagnostics remain visible after loading completes.