kb-querylisted

# kb-query — read-only query + query-session persistence Answer the user's questions about existing KB content. **Read-only: it writes no file under `wiki/`**, but it must persist a query-session for later `kb-save` and for audit. The execution layer is `scripts/pipeline.py`; this skill only orchestrates, surfaces acceptance, and constrains artifacts. ## 1. Triggers / Non-triggers - **Triggers:** "what does the KB say about X", "search my wiki", "what was that Y I learned", "has Z ever been covered". - **Non-triggers:** ingesting a new source (use `ingest`); writing a query result back (use `kb-save`); working the Review-Queue (use `kb-review`); a semantic health check (use `wiki-lint-semantic`); plain summary/translate/explain of external text (a normal answer — no query-session unless the user explicitly queries the wiki). ## 2. Inputs - The user's question; optional domain, concept name, source name, page path, or time range. - Read: `wiki/index.generated.md`, `wiki/concepts/_registry.yaml`, and the relevant concept/topic/comparison/synthesis/source/lesson pages. - If the answer might be worth saving, read `docs/skill-runtime/save-back-policy.md` to decide whether to emit a save candidate. ## 3. Outputs - An in-chat answer citing the relevant vault pages (wikilinks) and source location (source §section / page). - The query-session files under `pipeline-workspace/query-sessions/<run_id>/`. - It does not write `wiki/`, does not touch `log.md`, does not promote, does n