resolve-questionslisted

# resolve-questions Interactive walk-through for `~/knowledge/wiki/_pending_questions.md`. Each entry is a contradiction or ambiguity the librarian flagged for human review. Some entries carry an Opus-backed proposed resolution (issue #126); some don't. The user is the final authority — never resolve without confirmation. ## Surface - CLI: `athenaeum questions count|next|list [--with-proposal] [--json]` - MCP tools: `list_pending_questions`, `resolve_question(id, answer)` - Snooze file: `~/.cache/athenaeum/pending-questions-snoozed-until` (ISO-8601 UTC) ## Flow (six steps) 1. Run `athenaeum questions count --json`. If `count` is 0, tell the user "no pending questions" and stop. 2. Loop. On each iteration call `athenaeum questions next --with-proposal --json`. The result has the shape `{id, entity, source, question, conflict_type, description, created_at, proposal}`. Render it to the user as a short block: - entity, question, conflict_type - description (verbatim) - the proposal block when non-empty 3. Ask the user one of four choices: - **accept** the proposed resolution - **override** with a different answer - **defer** (snooze) — stop now, surface again tomorrow - **stop** — stop now without snoozing 4. **accept**: call the `resolve_question` MCP tool with `id` and the proposed action (extract the action from the `**Proposed resolution**:` line in the proposal block, e.g. `keep_a`, `merge`, `retain_both_with_context`). The