Document regex code navigation workflow

AGENTS.md

@@ -66,9 +66,12 @@ cmake --build --preset windows-msvc-default --config Debug --target clean
 Codex has a repo-specific skill named `panopainter-code-navigation`. Use it when
 following C++ symbols, finding symbol families with regular expressions, tracing
 service/interface wiring, or checking platform/backend boundary usage.
-Reach for `--name-regex`, `--detail-regex`, or `--path-regex` before broad
-`rg` searches when a refactor depends on symbol identity, generated-style name
-families, signatures, or platform/backend path slices.
+For C++ refactors, use the skill before broad `rg` searches when the question
+depends on symbol identity rather than plain text. Reach for `--name-regex`,
+`--detail-regex`, or `--path-regex` when looking for generated-style name
+families, override groups, command/service families, signatures, or
+platform/backend path slices. Use normal `rg` for docs, build files, comments,
+string literals, generated command names, or exact non-C++ text.
 
 Prefer compiler-aware navigation when following C++ symbols across the legacy
 flat source tree and extracted components:

docs/modernization/build-inventory.md

@@ -109,6 +109,10 @@ Known local toolchain state:
   `python scripts/dev/clangd_nav.py self-test`, also registered as
   `panopainter_clangd_nav_regex_self_test`, so regex filter behavior can be
   validated without clangd or a compile database.
+  Use the repo skill `panopainter-code-navigation` before broad text searches
+  when a C++ refactor needs symbol-family lookup, generated-style names,
+  signatures, override groups, or platform/backend path slices. Keep `rg` for
+  docs, build files, string literals, comments, and exact non-symbol text.
   Reference lookup is guarded because a one-shot clangd process may not have a
   complete project index: pass `--background-index` for broader best-effort
   results or `--allow-incomplete-references` for explicitly