refactor: change data directory from .coin-hunter to .coinhunter

- Update SKILL.md references to use ~/.coinhunter/
- Update user-data-layout.md with new directory paths
- Update init_user_state.py ROOT path
- Unify naming convention with .stockbuddy style

SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: coin-hunter
+name: Coin Hunter
 description: Hunt, triage, and compare speculative crypto coins — especially meme coins, 妖币-style runners, fake-hype pumps, and possible rug/scam setups. Use when a user wants to actively search for coins with breakout potential, rank a shortlist, ask whether a coin still has "妖性", or check whether a token looks late, fragile, manipulated, or likely to be a scam.
 ---
 
@@ -62,7 +62,7 @@ Preferred source order:
 - **CoinGecko** for market-cap, rank, and metadata cross-check
 - **web_search** for discovery, narratives, and scam-discussion context
 
-Private user state must live outside the skill directory under `~/.coin-hunter/`, not inside `skills/coin-hunter/`.
+Private user state must live outside the skill directory under `~/.coinhunter/`, not inside `skills/coinhunter/`.
 Read `references/provider-playbook.md` when choosing which source to trust first.
 Read `references/user-data-layout.md` when adding or updating personal accounts, positions, watchlists, or notes.
 Use `scripts/market_probe.py` for deterministic provider lookups.
@@ -217,8 +217,8 @@ If the user wants runners, meme coins, or small-cap candidates:
 `market_probe.py birdeye-token <address>` requires `BIRDEYE_API_KEY` in the environment. If it is not configured, say so briefly and continue with DexScreener + CoinGecko + web search.
 
 ### Private portfolio state
-If the user wants account, position, watchlist, or thesis tracking for coin-hunter:
-1. initialize `~/.coin-hunter/` with `python3 scripts/init_user_state.py`
+If the user wants account, position, watchlist, or thesis tracking for coinhunter:
+1. initialize `~/.coinhunter/` with `python3 scripts/init_user_state.py`
 2. store private data only there
 3. never place personal holdings inside the skill folder
 4. treat the skill folder as logic only, and the user-data directory as state only
@@ -289,7 +289,7 @@ If the user wants more depth, expand in this order:
 ## References
 
 Read `references/provider-playbook.md` for source selection and provider roles.
-Read `references/user-data-layout.md` for private state layout under `~/.coin-hunter/`.
+Read `references/user-data-layout.md` for private state layout under `~/.coinhunter/`.
 Read `references/radar-checklist.md` for a quick scoring framework.
 Read `references/search-workflow.md` for active discovery.
 Read `references/output-templates.md` for compact response structure.