graphify-clilisted

# Graphify CLI Reusable contract for querying a Graphify code graph. The graph is read-only material: this skill covers finding it, querying it, and degrading gracefully — never building it. The division of paths is fixed: | Graph | Path | Who | |---|---|---| | Repository's own (`.ai/graphify-out/graph.json`) | `graphify` MCP tools (`query_graph`, `get_neighbors`, …) | Agents | | Cross-repository global (`~/.graphify/global-graph.json`) | `graphify-global` MCP tools + `~/.graphify/global-manifest.json` | Agents | | Either graph, by hand | Read-only CLI with explicit `--graph` | Humans only | | Lifecycle (first indexing, refresh) | `/graphify-index` command + `graphify-init` plugin | Human and plugin only — never agents | ## Availability detection 1. The per-repository graph lives at `.ai/graphify-out/graph.json` (repo root). Check that literal path. If the file exists and parses, the graph is available; record `graphify: available`. 2. If the graph file is missing, record `graphify: absent` and skip Graphify entirely. Do not build it: first indexing is human-gated behind the `/graphify-index` command, and the `graphify-init` OpenCode plugin owns refreshes afterwards. Mention `/graphify-index` to the user once as the way to enable the graph, then continue without it. 3. Check freshness: compare the graph's `built_at_commit` with `git rev-parse HEAD`, and check whether `.ai/graphify-out/.opencode-extract-lock` exists (a refresh is in flight). On a commit mismatch or a prese