What does this PR do?

save_config_value() uses user_config_path if user_config_path.exists() else project_config_path to choose where to write. On first run, when ~/.hermes/config.yaml does not exist yet, this falls back to writing into the repo's cli-config.yaml. The comment at line 1751 says "Ensure parent directory exists (for ~/.hermes/config.yaml on first use)" but the mkdir runs after config_path is already chosen as the project fallback.

This PR makes save_config_value() always target user_config_path for writes. The fallback to project config should only apply to reads (which load_cli_config() already handles).

Related Issue

Fixes #14714

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• cli.py: Changed save_config_value() to always target user_config_path for writes. The existing mkdir(parents=True, exist_ok=True) handles creating ~/.hermes/ if needed, and the existing "Load existing config" block handles the case where the file does not yet exist.

How to Test

Tests: tests/cli/test_cli_save_config_value.py — 3 new tests in TestSaveConfigValueWriteTarget:

1. Config is created in ~/.hermes/ when it does not exist
2. Repo cli-config.yaml is never modified
3. Values round-trip through a freshly created user config

Tested on macOS (Python 3.11).

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS (Python 3.11)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

pytest tests/cli/test_cli_save_config_value.py::TestSaveConfigValueWriteTarget -q
3 passed