kb-reviewlisted

# kb-review — Review-Queue processing Work `wiki/Review-Queue/` and `review_proposals` items one by one. By default it only analyzes and suggests; **the final accept/reject is the user's.** The execution layer is `scripts/pipeline.py`; this skill only orchestrates, surfaces acceptance, and marks failure stops. ## 1. Triggers / Non-triggers - **Triggers:** "work the review queue", "look at the pending items", "what's in the Review-Queue", "walk me through the review backlog", "handle the lint failures / cross-domain promotions / overwrite proposals". - **Non-triggers:** ingesting a new source (use `ingest`); read-only queries (use `kb-query`); saving a query result (use `kb-save`); a whole-vault semantic check (use `wiki-lint-semantic`); never accept a proposal or edit a human page without user confirmation. ## 2. Inputs - `wiki/Review-Queue/*.md`: lint failure lists, `promotion-*.md`, `*-proposal.md`, semantic-lint reports. - The machine ledger: the `review_proposals` table, via `python scripts/pipeline.py status` or related CLI state. - Relevant vault pages, the concept registry, source state. ## 3. Outputs - For each item: a classification, the risk, a suggested fix, and whether a user decision is needed. - After the user confirms, execute the matching fix/promotion/marking; without confirmation, do not edit the target. - Append `> handled: <conclusion>` to a processed Review-Queue item, or note that it still awaits the user. ## 4. Dependencies - CLI: `status`, `li