SafiandClaude Opus 4.8
be3dcfca08
The query skill was split across two fragments so no platform got both capabilities: Claude had the vocab/IDF query-expansion step but no fallback if the CLI was unavailable; every other platform had the inline NetworkX fallback but the weaker raw-question matcher. Merge into one unified query reference + stub (Step 0 expansion -> CLI traversal -> inline NetworkX fallback, plus path/explain inline) shipped to all hosts. Remove the query_variant enum, its toml field, and the _CLI_ONLY_QUERY_HEADINGS coverage-audit exemption. Re-render all skill artifacts and re-bless expected/. skillgen check/audit-coverage/ monolith-roundtrip/schema-singleton all pass. Refs #1325. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
751 B
751 B
When graphify-out/graph.json already exists and the user asks a question about the corpus, answer from the graph rather than rebuilding it:
graphify query "<question>"
Before traversal, expand the question against the graph's own vocabulary so a wording mismatch does not collapse the answer to noise. If the graphify query CLI is unavailable, fall back to an inline NetworkX traversal of graphify-out/graph.json. Answer using only what the graph output contains, and quote source_location when citing a specific fact. For that vocab-expansion step, the BFS/DFS traversal modes, the --budget cap, the NetworkX fallback, save-result feedback, and the /graphify path and /graphify explain flows, see references/query.md.