Thanks for the v0.2.0. Wanted to share some fresh upgrade experience:

• If one has TRY_PATH set, the whole flow of config load/upgrade is not triggered at all...
• On Mac the change of base path for config would obviously break the migration, but that seems like a minor issue since the tool is very new
• The use of Application Support on Mac OS is debatable. Mac OS since Sonoma? has some serious restrictions on that folder, which, e.g. prevents usage of symlink in dotfiles. I'd vote to keep the config in ~/..config/try
• Also, having a possibility to have no config is always great. Since the tool only needs two values now, maybe worth adding TRY_SHELL? I'd love to avoid having additional config in dotfiles and using env vars. While config may be more convenient for others

Happy to ask Claude for a PR to add env var and make config merging more consistent. The latter should probably always load config, then apply possible overrides via env vars, and only then check if a setup guide needs to be invoked.

As for the config path - that's an opinionated choice of course