refresh-stacklisted

# Refresh Stack The LLM-assisted update leg of the freshness loop. Detection is mechanical (`check_versions.py`); **this command does the reasoning** — reading changelogs and deciding what, if anything, the guidance should say differently. Never auto-apply guidance edits; propose, then let the user approve. The `stack.toml` and scripts live in the sibling `python-engineering` skill of this plugin — resolve it as `${CLAUDE_PLUGIN_ROOT}/skills/python-engineering/` (fall back to the path relative to this file if the variable isn't set). ## Workflow 1. **Detect.** Run the version check and capture JSON: ```bash python "${CLAUDE_PLUGIN_ROOT}/skills/python-engineering/scripts/check_versions.py" --json ``` The `behind` flag marks any tool whose pinned floor is behind a newer major/minor. If `behind_count` is 0, report "stack current" and stop. 2. **Read the changes.** For each behind tool, fetch its changelog / release notes for the range between `pinned_min` and `latest` (WebFetch the project's releases page or changelog; use context7 for library docs). Do not guess from the version number alone. 3. **Classify each delta** into one of three buckets: - **version-only** — no behavior or guidance impact; just a newer release. Action: bump `pinned_min` in `stack.toml`. - **guidance-affecting** — the release changes a recommendation, renames a rule/flag, deprecates an API, or adds a pattern the skill should mention (e.g. a ruff rule ren