prepare-releaselisted

# Prepare Release Guided workflow to prepare a versioned release with a manually curated changelog. ## Quick start 1. Confirm the target repository and desired version number. 2. Create a release branch from the default branch. 3. Bump the version in all version-bearing files. 4. Review git history since the last tag and draft the changelog together with the user. 5. Commit and open a PR to the default branch. ## Workflow ### 1. Gather inputs Ask the user (skip when already clear from context): - **Target repository**: Which repo are we releasing? - **Version**: Exact version number (e.g. `1.2.3`). Follow the project's existing convention. - **Release type** (alternative): `patch`, `minor`, or `major`. If given, read the current version and compute the next one with semver rules instead of asking for an explicit version number. Before proceeding, verify that no git tag exists for the target version: ```bash git tag -l "v<VERSION>" "v*<VERSION>*" ``` Warn the user and stop if a matching tag is found. ### 2. Create the release branch - Ensure the local default branch (`main` or `master`) is up to date from the remote. - Create and switch to `release/v<VERSION>` (e.g. `release/v1.2.3`). - If a `release/` prefix conflicts with the repository's convention, adopt its existing pattern instead. ### 3. Bump the version Identify every version-bearing file in the repository. Common patterns: | Ecosystem | Files | |------------