[wchwawa]

Related Issue

No issue: this is a release-tooling chore, which the template exempts. It blocks the Homebrew half of the 0.12.0 release.

Summary

• scripts/release/README.md says either release workflow may create the GitHub release, and each adds only its own immutable assets. The Homebrew publish step instead assumed that an existing release already held its archive, manifest, and SHA256SUMS.
• For v0.12.0 the Python SDK workflow created the release first. The Homebrew run then passed both macOS install gates but failed to publish with no assets match the file pattern (run 39564170939), so it skipped the tap update PR.
• The step now mirrors the Python SDK step: it compares each Homebrew asset the release already has byte for byte, and uploads the ones it lacks.
• The workflow test now also requires the upload path.

Scope

• This PR changes one logical boundary only.
• No unrelated refactor, benchmark, metadata model, Holt layout,
  object-store, agent interface, or docs change is mixed in.
• The linked issue describes the user-visible problem, design decision, or
  maintenance task this PR resolves (release chore; see above).
• Any breaking change is intentional and documented (none).
• No compatibility shim, deprecated alias, or forwarding wrapper was added without a removal condition.

Change Size And Review

• I checked GitHub's additions plus deletions for this pull request.
• If the total is more than 5,000 lines, one core maintainer other than the
  current-head pusher approved the exact current head commit. Not applicable: under 5,000 lines.
• This change is still small enough for a focused review; approval count is
  not being used to justify mixed package or lifecycle boundaries.

Code Contract (Code Changes Only)

• Not applicable; this is a docs/config-only change.

Claims and Evidence

• User-facing documentation distinguishes current, experimental, and
  planned capabilities (no documentation change).
• Security claims do not treat a Workbench root or Agent scope as tenant
  authentication or authorization (no security claims).
• Performance claims state the topology, comparison boundary, cache state,
  run count, and raw-evidence location (no performance claims).
• Benchmark-only behavior does not alter product semantics.

Validation

• Command and result: python3 scripts/release/test_homebrew_source_release.py passes with the new assertion, and the workflow YAML parses.
• Not run (with reason): actionlint, which is not installed locally. The release path itself runs when the workflow is dispatched again for v0.12.0 after this merges.

Contributor Sign-off

• Every commit in this PR includes a DCO Signed-off-by trailer.