1.10.9 1.10.10 2026-05-15 2026-05-16 1 $CLAUDE_PLUGIN_ROOT/CHANGELOG.md Render an AskUserQuestion to confirm whether the user wants to see the changelog for this SPT plugin update. Before invoking AskUserQuestion, write one short pre-question line that names the version transition (and dates if both and are non-empty), e.g. "SPT plugin updated v1.10.9 → v1.10.10. Print changelog?" (released 2026-05-15 → released 2026-05-16). Then invoke AskUserQuestion with EXACTLY these three options (labels verbatim, do not paraphrase): 1. "Yes, full changelog" — On selection: read $CLAUDE_PLUGIN_ROOT/CHANGELOG.md and print every H2 section where 1.10.9 < version <= 1.10.10, verbatim markdown (preserve the original H2 lines, bullet structure, and any H3 subsections). Render in the order they appear in the file (newest first). Do not summarize, do not paraphrase. 2. "Yes, highlights only" — On selection: read $CLAUDE_PLUGIN_ROOT/CHANGELOG.md and synthesize 2-5 highlight bullets across the H2 sections where 1.10.9 < version <= 1.10.10. Pick 2-5 most impactful feature adds and fixes across the range. Prefer items that change user-facing behavior. Skip purely-internal refactors and test-only changes. Append exactly this pointer at the end: "See $CLAUDE_PLUGIN_ROOT/CHANGELOG.md for full detail." 3. "Skip" — On selection: take no action. Acknowledge briefly ("OK, skipping.") and continue with the user's prior intent. If the user provides freeform input via AskUserQuestion's "Other" option, treat all continuation phrases (later / not now / ignore / stop asking / no) as "Skip". When the question text mentions multiple versions (step_count > 1), the multi-version skip rendering applies: "Yes, full changelog" prints ALL interim H2 sections (not just the endpoints). After completing the user's choice, return control to whatever the user was working on before this prompt.