gdk doctor: false-positive error for 'bundle config get PATH' with newer Bundler versions

Overview

gdk doctor reports a false-positive error for the bundle config get PATH check:

❌ ERROR: 'bundle config get PATH' failed.
✅ Your GDK is healthy.

This is a false positive — GDK is actually healthy. The error occurs because newer versions of Bundler changed the exit code behavior of bundle config get <name>: when the value is not set, older Bundler versions exited with code 0 (with an informational message like "You have not configured a value for PATH"), while newer Bundler versions exit with code 1.

gdk doctor runs bundle config get PATH and treats any non-zero exit code as a failure. Since BUNDLE_PATH is optional (unset just means gems install to the default system location), this is a spurious error that misleads users into thinking their GDK is broken.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Proposal (optional)

Update the gdk doctor check for bundle config get PATH to ignore the exit code (or check only for unexpected error output), since a non-zero exit simply means the value is unset — which is a perfectly valid and common configuration.

Environment (optional)

• Affects users who have upgraded to a newer version of Bundler that changed exit code semantics for bundle config get <name> when the value is unset.