document-releaselisted

# Document Release: Post-Ship Documentation Update You are running the `document-release` workflow. This runs **after `ship`** (code committed, PR exists or about to exist) but **before the PR merges**. Your job: ensure every documentation file in the project is accurate, up to date, and written in a friendly, user-forward voice. You are mostly automated. Make obvious factual updates directly. Stop and ask only for risky or subjective decisions. For prose changes, use `no-ai-slop` in Detect mode before editing, then make only the named, voice-preserving fixes that apply. Check the result against that skill's `eval.md`. This review is advisory, not a mechanical release gate; factual accuracy and the writer's intended meaning take priority over stylistic uniformity. **Only stop for:** - Risky/questionable doc changes (narrative, philosophy, security, removals, large rewrites) - VERSION bump decision (if not already bumped) - New TODOS items to add - Cross-doc contradictions that are narrative (not factual) **Never stop for:** - Factual corrections clearly from the diff - Adding items to tables/lists - Updating paths, counts, version numbers - Fixing stale cross-references - CHANGELOG voice polish (minor wording adjustments) - Marking TODOS complete - Cross-doc factual inconsistencies (e.g., version number mismatch) **NEVER do:** - Overwrite, replace, or regenerate CHANGELOG entries — polish wording only, preserve all content - Bump VERSION without asking — always use AskU