kb-qalisted

# kb-qa — post-publish / pre-save QA report Run broad QA over the published vault or a pre-save candidate: coverage, evidence spot-checks, formula screenshot spot-checks, concept pollution, an ljg-qa-style Q-chain. Produces a report and Review-Queue proposals only; it does not edit content pages. ## 1. Triggers / Non-triggers - **Triggers:** "run a KB QA", "audit coverage", "spot-check evidence", "run the Q-chain", "check for concept pollution", "pre-save QA". - **Non-triggers:** "semantic health check", "find contradictions", "does the comparison cover the key dimensions", "Q2 added value" belong to `wiki-lint-semantic`; handling an existing Review-Queue uses `kb-review`; read-only Q&A uses `kb-query`; a new source uses `ingest`. kb-qa and `wiki-lint-semantic` are **mutually exclusive** on triggers. ## 2. Inputs - Scope: whole vault, a domain, a source, a query-session, or a proposed write candidate. - Read: `wiki/index.generated.md`, `wiki/concepts/_registry.yaml`, and the relevant source/concept/topic/comparison/synthesis/lesson pages. - May read: `pipeline-workspace/query-sessions/<run_id>/`, `wiki/Review-Queue/`, the deterministic `lint` result. ## 3. Outputs - `pipeline-workspace/reports/kb-qa/<run_id>.md`: the QA report. - For actionable findings, write `wiki/Review-Queue/kb-qa-<YYYY-MM-DD>.md` proposals; no direct content-page edits. - The report covers scope, the Q-chain, sampled items, findings, risk level, and the suggested follow-up skill (usually `kb-revie