The diagnostic report falsely reported chrome_binary as not found when
the config used ~ (e.g. ~/.chrome-for-testing/...). PathBuf::from()
treats ~ as a literal directory name, so existence checks always failed.
Add shellexpand::tilde() at the entry point of run_diagnostics() to
expand ~ before passing to downstream check functions. The original
unexpanded value is preserved for display in the report summary.
Runs automatically when --chrome-headless flag is used, checking:
- ChromeDriver installation and PATH
- Chrome/Chromium installation
- Chrome and ChromeDriver version compatibility
- config.toml chrome_binary setting
- Chrome for Testing installation
- ChromeDriver executable permissions (macOS quarantine)
Displays a detailed report with:
- Summary of detected versions and paths
- Pass/warning/error status for each check
- Specific fix suggestions for any issues found
Users can then ask g3 to help fix any detected issues.
