chore: finalize single-bundle release from develop to main

[Christiantyemele]

Summary

Finalizes the release strategy around a single openflows release that bundles all three shipped binaries (openflows, openflows-doctor, openflows-harness), with develop as the default branch and only develop merged into main to trigger the release.

Changes

• Default branch: develop is now the default branch on GitHub (already done via repo settings).
• .github/workflows/release-branch.yml: Restricts PRs to main to develop and release-plz-* only. Removes the old release/vX.Y.Z release-branch allowance.
• .github/workflows/release.yml: Updated comments to clarify main is release-only and develop is the default; release-plz release-pr runs on every merge to main.
• release-plz.toml: Documented the develop→main release flow.
• RELEASING.md: Rewrote the branching model and "cutting a release" steps to match the actual flow: only develop merges into main (guarded), which triggers release-pr; the resulting release-plz-* PR merges back into main and fires the tag + single GitHub Release with the cross-platform tarball bundling all three binaries.

Release flow (as configured)

feature/* ──PR──▶ develop          (default branch, integration)
develop ──PR merge──▶ main          (release-only; guard enforces develop-only)
                     │  push to main → release-plz release-pr
                     ▼
        release-plz-* PR (version bump + CHANGELOG) ──▶ main
                     │  merge of that PR → release-plz release
                     ▼
        tag openflows-X.Y.Z + single GitHub Release (no `v`)
                     ▼
        release-assets → attach openflows-<X.Y.Z>-<target>.tar.gz
                         (bundles openflows, openflows-doctor, openflows-harness)

[greptile-apps]

Greptile Summary

This PR finalizes the documented single-bundle release process and narrows the permitted sources for pull requests into main.

• Makes develop the documented integration and default branch while reserving main for releases.
• Allows only develop and same-repository release-plz-* branches through the release-branch guard.
• Documents the two-stage develop → main → release-plz PR release sequence.
• Retains one tagged GitHub Release containing all three shipped binaries.

Confidence Score: 5/5

The PR appears safe to merge because no eligible blocking failure remains.

No blocking failure remains.

Important Files Changed

Filename	Overview
.github/workflows/release-branch.yml	Narrows accepted pull-request source branches for main to develop and same-repository release-plz-* branches.
.github/workflows/release.yml	Updates workflow commentary to describe main as release-only and explain the intended two-push release sequence.
RELEASING.md	Rewrites release instructions around the develop-to-main flow and the single bundled GitHub Release.
release-plz.toml	Documents how release-plz participates in the revised branching and release model.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  F[feature branches] -->|PR| D[develop]
  D -->|release PR| M[main]
  M -->|release-plz release-pr| R[release-plz-* PR]
  R -->|merge| M
  M -->|release-plz release| T[openflows-X.Y.Z tag]
  T --> A[Single GitHub Release]
  A --> B[Bundled openflows binaries]

Loading

_{Reviews (2): Last reviewed commit: "chore: finalize single-bundle release fr..." | Re-trigger Greptile}