Indexing failure in Go Modules integration for internal packages

GoLand utilizes a proprietary indexing engine to synchronize project structures with go.mod and go.sum files. This process relies on the correct mapping of GOPATH and GOROOT within the IDE settings to ensure external libraries are correctly resolved.

A specific design constraint exists regarding the handling of internal packages. When these packages are accessed from outside the intended module hierarchy, there is a tension between the Go compiler's strict visibility rules and the IDE's indexing behavior, which may lead to inconsistent navigation or completion results.

Given a project utilizing Go Modules (version 1.21+), what is the expected indexing behavior when a module attempts to reference an internal package from a separate module hierarchy? Does the IDE prioritize the go mod dependency tree or the physical directory structure during this resolution?