Refine locate tooling notes based on hands-on testing

eza 的 --tree 在没有路径参数时会静默输出空结果，实测踩坑，需
明确写出必须加 `.`；broot 实测需要 TTY 且首次运行会改 shell rc，
对 CLI/Claude Code 没有增量价值，标注跳过避免后续误用。

CLAUDE.md

@@ -29,8 +29,9 @@ Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-s
 1. **Locate**: find the relevant files, functions, call sites, and tests. Quote or cite the existing code before proposing changes. If you can't locate it, say so — don't guess.
    - For mature/unfamiliar repos, prefer structured scans:
      - `repomix -o /tmp/x.xml` (or `repomix <subdir>`) — full-repo LLM pack; slice by subdir if > 100k tokens
-     - `eza --tree --git-ignore --level=3` for layout; `fd <pat>` for files; `rg <sym>` for call sites
+     - `eza --tree --git-ignore --level=3 .` for layout (⚠️ path arg required, omitting it silently prints nothing); `fd <pat>` for files; `rg <sym>` for call sites
      - `git ls-files` when tokens are tight
+     - skip `broot` — interactive-only, no value in CLI/pipeline context
 2. **Plan**: state the intended change in one or two sentences. List assumptions and open questions. Give a rough estimate of **token consumption** (reads + writes + tool calls) and **wall-clock time** so the user can redirect early if the scope is off. If uncertain, ask before writing code.
 3. **Execute**: make the minimal edit that matches the plan. Deviations require a new plan, not silent improvisation.