fix(ci): propagate retried build failures

[TimeToBuildBob]

Problem

The Tauri build uses nick-fields/retry with a custom Bash command that did not enable fail-fast behavior. When make build failed, the trailing pip freeze returned zero, so the retry action treated a partial build as successful.

This happened in the macOS Intel job of TimeToBuildBob/activitywatch run 32205310837: aw-tauri failed before the root Makefile restored the local aw-client checkout, pip freeze showed aw-client 0.5.14, and the next step ran checkout tests against that stale installed package.

Fix

Enable Bash errexit inside the retried Build command. A failed install or build now reaches the retry action immediately, and tests only run after the complete build path succeeds.

I deliberately kept the aw-client tests unchanged: switching them to force source imports would silence this useful packaging-environment canary.

Verification

• Parsed release.yml as YAML and located the single retried Build command.
• Executed its set -e preamble against a failing command; the shell returned nonzero and did not execute the trailing marker.
• Reproduced the original signature separately: bare pytest with aw-client 0.5.14 installed failed the same two tests, while python -m pytest against the checkout passed.
• Local pre-PR quality gate: 100/100.

[greptile-apps]

Greptile Summary

This PR makes the retried Tauri build command fail immediately when any setup, installation, or build command returns nonzero.

• Enables Bash errexit at the start of the retried build command.
• Prevents a successful trailing pip freeze from masking poetry install or make build failures.
• Preserves the cross-platform virtualenv activation fallback.

Confidence Score: 5/5

The PR appears safe to merge because the new errexit behavior correctly propagates failed build commands across the release matrix.

The activation fallback remains valid as an || list under Bash errexit, while failures from environment creation, dependency installation, and compilation now stop the command before the trailing diagnostic can overwrite their exit status.

Important Files Changed

Filename	Overview
.github/workflows/release.yml	Adds set -e to the Tauri build retry command so failures propagate to the retry action without breaking the Bash virtualenv fallback.

_{Reviews (1): Last reviewed commit: "fix(ci): propagate retried build failure..." | Re-trigger Greptile}

[TimeToBuildBob]

Greptile is 5/5 and the affected macOS Intel Tauri build passed. The remaining Windows and Qt matrix jobs are still running, so there is no additional fix to make yet; waiting for CI completion and maintainer review.