Version Formula branches by rendered content

[0x77dev]

Includes the rendered Formula blob ID in App-authored release branch names. An immutable release can now recover after a generated Formula is corrected without reusing a closed PR branch; identical retries still converge on one branch.\n\nVerified: actionlint .github/workflows/ci.yml; git diff --check.

[greptile-apps]

Confidence Score: 5/5

Safe to merge based on the exercised release-branch behavior.

The changed branch-selection logic was exercised with a local bare Git remote across branch creation, reuse, corrected Formula content, and mismatched-content rejection.

Files Needing Attention: No files need additional attention.

T-Rex Logs

What T-Rex did

• The isolated bare-remote release-branch harness script was run to exercise the release-branch naming and remote validation behavior.
• The harness demonstrated that identical Formula content reused its release branch, changed content at the same version created a distinct branch, and a same-named branch with a mismatched Formula blob was rejected.
• Harness source trex-artifacts/pr145-release-branch-harness.sh and its execution log trex-artifacts/pr145-release-branch-output.log were collected for review.
• The executed log showed the command exited with code 0 after all assertions passed.
• Artifacts presented for reviewer include the Release branch workflow harness source and the Release branch workflow harness output.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Version Formula branches by rendered con..." | Re-trigger Greptile}