Upload leaf_prover and recursive_tree arch binaries

[YairVaknin-starkware]

What

Add build + upload steps for the two additional binaries, mirroring the existing stwo_run_and_prove flavors so the backend can pull CPU-optimized builds:

• leaf_prover: generic (x86_64) + 6 CPU targets (znver3/4/5, emeraldrapids, sapphirerapids, graniterapids).
• stwo_run_and_prove_recursive_tree: 6 CPU targets (the generic build is already uploaded).

All land under sharp-binary-artifacts/<product>_artifacts/<hash>/release, consistent with the single-bucket layout.

Naming notes

• leaf-prover's Cargo bin target is hyphenated (like stwo-run-and-prove), so the x86_64 build is renamed to leaf_prover before upload; the build-arch-binary action derives the underscore name for the arch builds.
• stwo_run_and_prove_recursive_tree's bin target already uses underscores (explicit [[bin]]), so it's passed as-is.

Consumer side

The backend wiring that pulls and selects these (consts.bzl / WORKSPACE / BUILD / Python CPU selection) is a separate starkware-side change; it depends on these buckets/folders being populated by this workflow first.

🤖 Generated with Claude Code

---

This change is 

[cursor]

PR Summary

Low Risk
CI-only changes that add artifact upload steps; no runtime application or security-sensitive logic is modified.

Overview
Extends Upload-Artifacts so leaf_prover and stwo_run_and_prove_recursive_tree get the same GCS publishing pattern as stwo_run_and_prove.

The workflow now uploads a generic x86_64 leaf_prover (renamed from the leaf-prover Cargo bin) to sharp-binary-artifacts/leaf_prover_artifacts/<hash>/release. It also runs build-arch-binary for six CPU targets (znver3/4/5, emeraldrapids, sapphirerapids, graniterapids) for both leaf-prover and stwo_run_and_prove_recursive_tree, matching the existing arch artifact layout.

Note: The push trigger currently includes branch yairv/add_new_bins_to_ul_workflows in addition to main (likely for testing this PR).

^{Reviewed by Cursor Bugbot for commit ef420cc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ef420cc. Configure here.}

[cursor]

Upload workflow missing main trigger

High Severity

The push trigger lists only yairv/add_new_bins_to_ul_workflows and no longer includes main. After merge, pushes to main will not run Upload-Artifacts, so release binaries (including the new leaf_prover and arch stwo_run_and_prove_recursive_tree uploads) would stop being published from the default branch.

 

^{Reviewed by Cursor Bugbot for commit ef420cc. Configure here.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.86%. Comparing base (4c777d3) to head (ef420cc).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #410   +/-   ##
=======================================
  Coverage   67.86%   67.86%           
=======================================
  Files          42       42           
  Lines        5459     5459           
=======================================
  Hits         3705     3705           
  Misses       1754     1754           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.