bump-versionlisted

# Bump Version (Sessions Chronicle) ## Overview Update release metadata consistently for this Meson + Flatpak project. Core principle: one `new_version`, one approved note, one successful Flatpak build. ## When to Use - User asks to bump app version (`0.x.y`) for a release. - Version metadata must stay aligned across `Cargo.toml`, `meson.build`, `src/config.rs.in`, and metainfo releases. - Release notes are missing and need a generated draft before writing. ## When NOT to Use - User only wants a local Rust build check (no release metadata changes). ## Required Input - `new_version` (required): semantic version like `0.3.5`. - `release_notes` (optional): short paragraph + bullets for metainfo. Validation: - Reject if `new_version` is missing. - Reject if `new_version` does not match `^\d+\.\d+\.\d+$`. ## Quick Reference | File | Expected change | |---|---| | `Cargo.toml` | Set `[package].version = "<new_version>"` | | `meson.build` | Set `project(..., version: '<new_version>', ...)` | | `src/config.rs.in` | Keep `pub const VERSION: &str = @VERSION@;` (never edit `src/config.rs`) | | `data/dev.maciz.sessionschronicle.metainfo.xml.in.in` | Add newest `<release version="<new_version>" date="YYYY-MM-DD">...</release>` | ## Implementation Workflow 1. Validate `new_version` format. 2. Update `Cargo.toml` version. 3. Update `meson.build` project version. 4. Verify `src/config.rs.in` still uses `@VERSION@` placeholder. 5. Prepare release notes for metainfo: - If `relea