## Why
The DotSlash configs require Bazel assets that are absent from the Cargo-only release asset fixture for `0.167.0-alpha.2`.
## What changed
Remove the Bazel outputs for Codex, the Windows command runner and sandbox setup, and provisioned macOS packages from the release configs.
## Testing
Add regression tests using the release asset fixture to verify that every configured output has a matching asset and that missing Codex and provisioned macOS package assets are detected.
GitOrigin-RevId: ed10a56717e0a7c6c566087b64621bd3ff042412
## Why
Desktop consumers require successful Cargo and Bazel release artifacts, so Bazel release jobs must no longer be advisory.
## What changed
- Remove Bazel-specific `continue-on-error` settings from release build, signing, packaging, symbol, and macOS verification jobs.
- Add `codex-bazel`, `codex-command-runner-bazel`, and `codex-windows-sandbox-setup-bazel` DotSlash outputs for the corresponding Bazel release assets.
- Extend provisioned macOS signing and verification to both Cargo and Bazel packages on both architectures, keeping Bazel artifacts and reports distinct with a `-bazel` suffix.
- Add a `codex-provisioned-bazel` DotSlash output for provisioned macOS packages.
## Testing
Run the existing provisioned package smoke tests, including sandboxed code mode, for each build system using its matching CLI, app-server, and symbols archives.
GitOrigin-RevId: c951a3eb4557b539d53a12040237d5ef947f6bdf
## What changed
- When `CODEX_PROVISIONED_MACOS_CANDIDATE` is `true`, require the provisioned macOS job to succeed and upload its verified packages as release assets. Allow releases to proceed when the job is disabled and skipped.
- Include provisioned archives in `codex-package_SHA256SUMS` and remove per-architecture `SHA256SUMS` files before upload.
- Publish a `codex-provisioned` DotSlash manifest for macOS ARM64 and x86_64 packages, pointing to `bin/codex`.
GitOrigin-RevId: 7e36df484a3b7da6b66180fa31418a6958d1fe77
Felipe Coury