chore: prepare v0.4.5 release

[ovaso]

Summary

• correct repository metadata, installer, release, attestation, changelog, and schema URLs
• make the Release badge follow the latest semantic-version tag
• document that GitHub Releases are separate from GitHub Packages and that the crate is not yet on crates.io
• bump the package and documentation version to 0.4.5
• synchronize automation contracts, the repository-local skill, and schema black-box coverage

Validation

• cargo fmt -- --check
• cargo test --locked
• cargo clippy --all-targets --all-features -- -D warnings
• cargo build --locked --release
• installer shell syntax, Cargo metadata, YAML syntax, and local Markdown links

Risk and rollback

Documentation, package metadata, installer endpoints, and schema identifier updates only. No Git operation, manifest, scheduler, or runtime behavior changes.

[chatgpt-codex-connector]

💡 Codex Review

batch-git-rs/src/commands/automation_commands.rs

Line 152 in b3e9a56

"$id": "https://github.com/ovaso/batch-git-rs/schemas/operation-result-v1.json",

Preserve the v1 schema identifiers

For automation that keys schema caches or allowlists by $id, changing both identifiers in a 0.4.x release makes the unchanged v1 schemas appear to be entirely different schemas. This contradicts the evolution rule in docs/ARCHITECTURE.md:112-114, which permits only new optional fields within the same major version, while docs/AUTOMATION_CONTRACTS.md:253-256 explicitly describes $id as stable. Preserve the existing v1 IDs when moving repository URLs, or introduce newly versioned schema identifiers.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".