🚀 Establish production-grade release and distribution pipeline

[szmyty]

Description

Refactor and complete Renderflow's release and distribution pipeline so that a single version bump and tag produces a fully reproducible public release.

The project already contains most of the required infrastructure (version bumping, changelog generation, GitHub Releases, package definitions, Homebrew formula, Scoop manifest, Chocolatey package, Snap package, Debian/RPM packaging, etc.), but these pieces should operate as one cohesive release system instead of a collection of independent workflows.

The goal is to make releasing Renderflow a one-command, production-grade experience.

---

Goals

• establish a fully automated release pipeline
• ensure GitHub Releases are the canonical distribution point
• eliminate manual release steps
• ensure every supported package manager is updated automatically
• improve workflow reliability and maintainability
• simplify future releases

---

Requirements

Release Architecture

• review and refactor the existing release workflow into a cohesive release pipeline
• separate CI concerns from release concerns where appropriate
• reduce duplication across workflows
• document the release process

---

Versioning

• establish a single source of truth for version numbers
• ensure version bumping updates all required project files
• automatically create and push release tags
• validate semantic versioning

---

GitHub Releases

• automatically create GitHub Releases from version tags
• publish generated release notes
• upload all release artifacts
• publish SHA256 checksums
• verify release assets before publishing

---

Binary Distribution

Ensure release binaries are produced for all supported targets.

Validate:

• Linux (musl)
• Linux (GNU)
• macOS (Intel)
• macOS (Apple Silicon)
• Windows

Verify artifact naming consistency.

---

Package Distribution

Ensure the release process updates all supported package ecosystems.

Including:

• Homebrew
• Scoop
• Chocolatey
• Snap
• Debian (.deb)
• RPM
• AUR

Verify version numbers, download URLs, and checksums remain synchronized.

---

Repository Metadata

Ensure release automation updates:

• CHANGELOG.md
• GitHub Release notes
• package manifests
• Homebrew formula
• release metadata

---

Validation

Create automated verification that:

• release artifacts exist
• package manifests reference the correct release
• checksums match uploaded binaries
• download URLs are valid

---

Documentation

Update repository documentation to describe:

• release workflow
• version bump process
• release lifecycle
• supported distribution channels

---

Acceptance Criteria

• version bump triggers complete release pipeline
• GitHub Release is automatically created
• release notes are generated automatically
• binaries are uploaded for every supported platform
• package managers are updated automatically
• manifests and checksums remain synchronized
• release workflow is documented
• release process requires no manual intervention
• Renderflow has a complete, reproducible, production-grade release pipeline