modding with absolute path disables autocomplete

rust-analyzer version: 0.3.1850-standalone (68c506fd6 2024-02-19)
rustc version: rustc 1.77.0-nightly (30dfb9e04 2024-01-14)

I'm writing a build script that automatically mods some other files. The build script generates it's output to some directory which then is included with the include! macro. The main file behaves correcty, the autocomplete treats the injected code as if the include macro didn't exist (which is expected). In the included files compile-errors are displayed correctly as well. Just autocomplete is not working. When modding the file manually in main.rs autocomplete starts working. Note that the modded file is in a different directory than src (still within the same vscode session tho)

Start with the reported setup: a build script generates files outside src, main.rs includes them with include!, and another file is modded using an absolute path. Reproduce the difference between generated and manually declared modules in VS Code, then trace rust-analyzer's module-file discovery; done means autocomplete works in the externally generated modded files while existing diagnostics remain correct.