Omri/temp branch

[OmriEshhar1]

Type

• feature
• bugfix
• dev (no functional changes, no API changes)
• fmt (formatting, renaming)
• build
• docs
• testing

Description

Breaking changes?

• yes
• no

---

This change is 

[cursor]

PR Summary

Medium Risk
Changing the stwo-cairo revision affects the proving/verification stack, and the lockfile temporarily mixes two stwo-cairo SHAs via stwo-circuits, which can cause subtle build or runtime mismatches until dependencies are aligned.

Overview
Pins all workspace stwo-cairo git dependencies from a837f0e to 9b93cc39 in Cargo.toml, with a matching Cargo.lock refresh. The lockfile now carries two stwo-cairo revisions: workspace crates (stwo-run-and-prove, privacy-prove, etc.) resolve to 9b93cc39, while stwo-circuits-pulled crates still depend on cairo-air / stwo-cairo-* at a837f0e.

The Upload-Artifacts workflow is extended so pushes to omri/temp-branch also run the release build and GCS upload pipeline (same as main).

^{Reviewed by Cursor Bugbot for commit 53a5647. 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 53a5647. Configure here.}

[cursor]

Split stwo-cairo git revisions

Medium Severity

Workspace stwo-cairo pins move to 9b93cc39, but privacy-prove and privacy-circuit-verify still depend on a837f0e, so stwo-run-and-prove artifacts and the privacy proving stack no longer share the same Cairo/STWO revision.

 

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