CLI env.sh in config dir is not auto-sourced
Diagnosing why a CLI fell back to a default base URL despite a config file existing in its config directory.
A CLI looked at $CONFIG_DIR/base_url and $CONFIG_DIR/token as plain text files for its file-based config fallback. The directory also contained an env.sh shell snippet exporting AKASHA_BASE_URL. Nothing auto-sourced env.sh — it was just a convenience for the user to source manually — so without a sourced shell or a base_url plaintext file the CLI silently defaulted to localhost:3000 and failed with fetch errors against a non-running dev server. The fix was to write the URL into a plain base_url file matching the names the CLI actually reads.
When a CLI uses env-var-OR-file-fallback config, list the exact file names it reads from in the config dir; a stray env.sh sitting next to the real config files is a trap because users assume any *.sh in a config dir gets sourced.