GoLand macOS Debugging Limit: Delve Signing Behavior Across Releases

GoLand supports debugging Go programs on macOS through the bundled Delve debugger, but the debugger binary must carry the com.apple.cs.debugger entitlement to launch. The IDE attempts to sign the bundled Delve automatically when a debug session starts; however, success depends on the macOS version, keychain state, and whether the user approves the signing prompt, so the outcome is not deterministic across machines. When automatic signing fails, the documented fallback is manual signing of the Delve binary, yet the boundary between automatic and manual signing for supported configurations remains unclear. This behavior is version-sensitive for both the IDE and the operating system, and it surfaces as a debugger launch failure rather than a build error, which can obscure the underlying OS trust issue.

Does GoLand's automatic Delve signing reliably succeed on current macOS releases, or is manual signing the expected path for certain configurations? Where does the documented support boundary lie between re-signing the bundled binary, configuring a separately signed Delve path, or accepting that debugging is unavailable? How does this behavior differ across GoLand versions given that Delve is bundled and updated with IDE releases?