Summary

Fix ZSH config edit action opening the wrong file by resolving the config path dynamically via forge config path instead of hardcoding ~/forge/.forge.toml.

Context

The ZSH shell plugin's _forge_action_config_edit function had a hardcoded path of ~/forge/.forge.toml. This was incorrect for users whose config lives at the new canonical location ~/.forge/.forge.toml, or in a custom path set via FORGE_CONFIG. As a result, running the config edit action from ZSH would open (or create) the wrong file, silently ignoring any existing configuration.

Changes

• ZSH plugin: _forge_action_config_edit now calls forge config path to resolve the correct config file path at runtime, respecting FORGE_CONFIG, the new ~/.forge location, and the legacy ~/forge fallback
• CLI: Added forge config path subcommand that prints the resolved path to the global config file
• CLI: Added forge config migrate subcommand to migrate the legacy ~/forge directory to ~/.forge
• UI: Reformatted migration output to use writeln_title and TitleFormat for consistent styling
• Workspace init: Removed the -y/--yes flag from workspace init — confirmation is now always prompted

Key Implementation Details

forge config path is the single source of truth for where the config file lives. The ZSH plugin shells out to it and fails fast with a clear error if the binary is unavailable or returns an empty path. Directory creation also uses the dynamically resolved path rather than the hardcoded one.

Testing

# Verify the new subcommand prints the correct path
forge config path

# In ZSH with the plugin loaded, open the config editor
# (should open the file reported by `forge config path`)
forge config edit

# Test migration from legacy path
forge config migrate

Links

• PR: fix(zsh): resolve config path dynamically to open the correct file for editing #2919