oc-releasing-versionslisted

# Releasing-Versions — release-please first, manual PR flow as the fallback This skill has **two regimes**, and the regime is **detected, never assumed**: - **Release-please regime** — the project has release-please configured. The action owns the CHANGELOG, the version and the tag. You only write conventional commits. - **Manual regime (fallback)** — the project does NOT have release-please. The release-PR flow at the end of this file applies. The governing rule is `rules/releases.md`, section "Release-please (fonte primaria quando configurado)". On any divergence, the rule wins. All git mechanics conform to `AGENTS.md` §4 (Conventional Commits; never commit to `main`; selective stage; never a `Co-Authored-By` trailer). ## 0. Detect the regime (ALWAYS the first step) ```bash ROOT=$(git rev-parse --show-toplevel) || exit 1 RP="" [ -f "$ROOT/release-please-config.json" ] && RP="config" [ -z "$RP" ] && [ -f "$ROOT/.release-please-manifest.json" ] && RP="manifest" [ -z "$RP" ] && grep -rq "release-please-action" "$ROOT/.github/workflows/" 2>/dev/null && RP="workflow" echo "${RP:-manual}" ``` - Output `config` / `manifest` / `workflow` → **RELEASE-PLEASE REGIME** → follow sections 1 to 4. The manual fallback **does not apply**; do not even read it. - Output `manual` → **MANUAL REGIME** → jump straight to the fallback at the end of the file. Two non-negotiables in this step: - **Check all THREE forms.** release-please can be configured by workflow input alone, with no con