chore: drop Rust from claw server release name

[Nikhil (shadowfax92)]

Summary

• Rename the BrowserClaw server release workflow without the obsolete Rust qualifier
• Use the same single-server name for release titles, initial notes, and release preparation
• Update the existing workflow assertion

Design

This changes only the public release display name. Rust-specific crate names, workflow filenames, artifact names, tags, and R2 paths remain unchanged for compatibility.

Test plan

• bun test scripts/release/release-claw-server-rust-workflow.test.ts
• actionlint .github/workflows/release-claw-server-rust.yml

[Nikhil (shadowfax92)]

Greptile (@greptileai) review

[Nikhil (shadowfax92)]

Claude (@claude) review

[claude]

Claude finished Nikhil (@shadowfax92)'s task in 1m 54s —— View job

---

Review complete ✅

• Gather context (read changed files, diff)
• Understand the request (code review of merged PR chore: drop Rust from claw server release name #2089)
• Review changes for correctness, safety, consistency
• Post review feedback

Summary

This is a small, low-risk chore that renames the public release display name from "BrowserClaw Server (Rust)" to "BrowserClaw Server" in three places, while intentionally leaving tags, file/artifact names, R2 paths, and the Cargo-based crate untouched — exactly as described in the PR's Design section. I verified --release-name is only used for display purposes (git tag annotation message, gh release create/edit title, log text) in prepare-server-bundle-release.sh, so this rename is safe and doesn't affect tag/artifact naming or CDN paths.

Finding: one leftover "Rust" mention in a still-public string

.github/workflows/release-claw-server-rust.yml:580 (in the "Summarize published resource keys" step) still emits:

echo "### BrowserClaw Server Rust resource publish"

This heading is written to $GITHUB_STEP_SUMMARY, which is public-facing (shown on the Actions run summary page), same category as the release title/notes this PR intentionally updated. It wasn't caught because release-claw-server-rust-workflow.test.ts has no assertion covering the "Summarize published resource keys" step. Every other "Rust" occurrence in the workflow (Setup Rust, Run Rust workspace tests, Build Rust binary, Rust server resource zip, etc.) legitimately refers to the Rust toolchain/implementation and should stay as-is — only this one heading is a stray product-name mention that should probably read ### BrowserClaw Server resource publish for consistency with the new naming.

Fix this →

Everything else checks out

• Workflow name: field, initial-release changelog text, and the TITLE= used in gh release create/edit are all consistently updated.
• prepare-claw-server-rust-release.sh's --release-name default and the corresponding test assertion match.
• No functional/tag/path changes — confirmed release_name in prepare-server-bundle-release.sh only feeds display strings (tag annotation message and log output), never the tag itself or R2/artifact paths.

Since this PR is already merged, the leftover string at line 580 would need a small follow-up commit/PR if you want to fix it — happy to open one if you'd like.

[greptile-apps]

Greptile Summary

This PR consistently removes the obsolete Rust qualifier from the public BrowserClaw server release name while preserving compatibility-sensitive workflow, tag, artifact, crate, and storage identifiers.

• Renames the GitHub Actions workflow and generated GitHub release titles.
• Updates initial release notes and release-preparation metadata.
• Adjusts the workflow assertion to expect the new display name.

Confidence Score: 5/5

The PR appears safe to merge because the display-name changes are internally consistent and leave release routing and artifact identities unchanged.

The workflow, preparation wrapper, and test agree on the new BrowserClaw server display name, while operational identifiers such as tag prefixes and workflow filenames remain intact.

Important Files Changed

Filename	Overview
.github/workflows/release-claw-server-rust.yml	Consistently removes the Rust qualifier from the workflow name, initial notes, and GitHub release title without changing release mechanics.
packages/browseros-agent/scripts/release/prepare-claw-server-rust-release.sh	Updates only the public release name passed to the shared preparation script while retaining compatibility-sensitive component and tag configuration.
packages/browseros-agent/scripts/release/release-claw-server-rust-workflow.test.ts	Updates the workflow-name assertion to match the intended public display name.

_{Reviews (1): Last reviewed commit: "chore: drop Rust from claw server releas..." | Re-trigger Greptile}

[github-actions]

✅ Tests passed — 2540/2544

Suite	Passed	Failed	Skipped
✅ agent	367/367	0	0
✅ build	34/34	0	0
✅ claw-app	294/294	0	0
✅ claw-mcp	109/109	0	0
✅ claw-onboard	87/87	0	0
✅ claw-server-rust-quality	passed	0	0
✅ claw-server-rust	555/555	0	0
✅ server-agent	313/313	0	0
✅ server-api	170/170	0	0
✅ server-browser	10/10	0	0
✅ server-integration	10/10	0	0
✅ server-lib	299/300	0	1
✅ server-root	38/41	0	3
✅ server-tools	254/254	0	0

passed = ran successfully but emits no JUnit counts (a lint/format gate).

View workflow run