Best possible solution:

If maintainers want clearer macOS release logs, land this narrow logging change after normal required checks complete; no broader packaging redesign is needed.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR is an observability cleanup, not a bug report. Source inspection of current main confirms the repeated Swift app/helper builds that the new log lines describe.

Is this the best way to solve the issue?

Yes. Logging immediately before the two existing swift build commands is the narrowest maintainable way to distinguish product and architecture phases without changing packaging behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 552ec2b49d4a.

Label justifications:

• P3: This is low-risk release-script observability cleanup, not a user-facing runtime regression.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply because this PR is authored by a repository member and only changes release-script logging.

PR surface:

Other +2. Total +2 across 1 file.

What I checked:

• Live PR metadata: Live GitHub metadata shows this PR is open, mergeable, authored by a MEMBER, and labeled maintainer, which requires explicit maintainer handling rather than cleanup close. (ccbcdb6a91fa)
• Repository policy: Root and scripts AGENTS.md were read fully; the relevant guidance is to review beyond the diff, respect scripts-area workflow expectations, and keep protected maintainer items in maintainer handling. (AGENTS.md:1, 552ec2b49d4a)
• Current main build loop: Current main already builds both the OpenClaw app and openclaw-mlx-tts helper inside the architecture loop; the PR only labels those existing phases. (scripts/package-mac-app.sh:194, 552ec2b49d4a)
• PR diff: The PR adds one echo line before each existing Swift build command and does not change command arguments, dependency sources, outputs, signing, or packaging flow. (scripts/package-mac-app.sh:197, ccbcdb6a91fa)
• Caller and release context: scripts/package-mac-dist.sh invokes scripts/package-mac-app.sh after setting release defaults, so clearer per-architecture build logs apply to the existing distribution packaging path. (scripts/package-mac-dist.sh:137, 552ec2b49d4a)
• Adjacent docs: The macOS README documents scripts/package-mac-app.sh as the packaging flow that creates and signs dist/OpenClaw.app, matching the script surface touched by the PR. (apps/macos/README.md:17, 552ec2b49d4a)

Likely related people:

• cgdusek: Authored merged universal-binary packaging work that changed scripts/package-mac-app.sh and the architecture behavior this PR logs. (role: feature-history contributor; confidence: medium; commits: 8c798d40b7b7, 833d5173bb69, 1c15b88682a4; files: scripts/package-mac-app.sh, docs/platforms/mac/release.md)
• osolmaz: Authored merged macOS release automation work that touched scripts/package-mac-app.sh and the release workflow context for this script. (role: release automation contributor; confidence: medium; commits: 36372687a6a1, 889f3426a864, cc571684e9df; files: scripts/package-mac-app.sh, .github/workflows/macos-release.yml, docs/reference/RELEASING.md)
• ImLukeF: Authored the merged MLX Talk provider work adjacent to the helper product named by the added build log. (role: adjacent MLX Talk contributor; confidence: low; commits: d4360c3e7480, ff4f984f052d, 7bb4012db56a; files: apps/macos/Package.swift, apps/macos/Sources/OpenClaw/TalkMLXSpeechSynthesizer.swift, apps/macos/Sources/OpenClaw/TalkModeRuntime.swift)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.