release-preplisted

# Release Prep Checklist Validates that the repository is in a clean, releasable state. Does **not** create tags, bump versions, or push commits — release-please automation manages all of that from `main`. The only action this skill takes beyond validation is offering to open a PR, and only after every gate passes and the user explicitly approves. Run these steps in order. **Stop immediately and report findings to the user if any step fails.** Do not proceed to the next step. ## Step 1 — Validate All Skills and Version Sync Run `/validate-skills`. This validates both public skills (`skills/*/SKILL.md`) and internal skills (`.claude/skills/*/SKILL.md`), and also runs the version-sync check (`scripts/check-version-sync.py`). If any **errors** are reported from skill validation: stop. Report the list of errors to the user. Do not proceed until they are resolved. Warnings must be reviewed; fix any that relate to skills being changed in this branch. If version sync fails: stop. Report which files differ and what their versions are. Do not proceed. ## Step 2 — Security Scan Run `/security-auditor`. If any Critical or High finding remains open after the scan: stop. Report the findings to the user. Do not proceed. ## Step 3 — Documentation Accuracy Run `/doc-auditor`. If any Critical finding remains open: stop. Report the findings. High findings (missing API/boundary docs) must also be resolved before proceeding. Medium and below may be deferred but must be tracked in `doc