graphify-wrapper-querylisted

# /graphify-wrapper-query Traverse a domain's graph to answer an architecture/navigation question, instead of grepping the whole subtree. ```bash . .better-dev/bin/bd-gfx 2>/dev/null || . "${CLAUDE_PLUGIN_ROOT}/scripts/bd-gfx" name="$1"; shift graph=$(gfx_ensure_graph "$name") || exit 1 # builds registry/domain/graph if missing ``` `gfx_ensure_graph` is the whole entry condition. It heals a missing registry, a repo with no domain carved yet, and a worktree with no graph built - each with an AST-only build that costs no LLM call and no API key. The old behaviour exited 1 on any of the three, and the caller fell back to grep; three dead ends deep, no repo ever built a graph at all. **A first question is allowed to be the thing that wires the index up.** A `--semantic` layer stays deliberate (`/graphify-wrapper-sync --semantic`) - a question never triggers LLM spend. Healing the registry is the one machine-global write this skill makes (D26). When it prints `graphify: created registry <dir>`, say so with the answer and give the undo: `rm -rf` that directory. Never name a shell variable `path` in these blocks. zsh ties `path` to `PATH`, so the assignment wipes command lookup and every later `graphify`/`jq`/`git` call dies with "command not found" - the failure that kept this wrapper from ever running on macOS. `bd-package-check` gates it now; `idx_path` is the convention. ## Dispatch Pick the graphify verb from the flags (default: `query`): - default - `graphify query "