fix(app): mark OpenWork Connect as beta

[reachjalil]

Summary

• mark OpenWork Connect as Beta across the desktop settings navigation, empty-state pitch, and connection card/detail badges
• align desktop Connect eval assertions and voiceovers with the Beta label
• add a focused server-rendered regression test for the navigation badge, pitch, and connection card

Why

• OpenWork Connect is already presented as Beta on the Den/server surfaces, but the desktop client still rendered Alpha

Issue

• N/A

Scope

• OpenWork app client copy and presentation
• desktop-facing eval expectations

Out of scope

• server or Den behavior
• updater-channel and unrelated Alpha labels

Testing

Ran

• ./bin/openwork-hub run desktop openwork-connect-beta -- pnpm --filter @openwork/app exec bun test --isolate tests/openwork-connect-beta-badge.test.tsx
• ./bin/openwork-hub run desktop openwork-connect-beta -- pnpm --filter @openwork/app typecheck
• node --check evals/flows/connect-tab-beta.flow.mjs
• node --check evals/flows/connections-beta-desktop.flow.mjs
• node --check evals/flows/extensions-legacy-rename.flow.mjs

Result

• pass: 1 focused test, 5 assertions
• pass: app TypeScript check
• pass: all three updated eval files parse

CI status

• in progress: OpenWork Tests (Ubuntu and macOS), i18n Audit
• pass: Vercel Preview Comments
• code-related failures: none reported
• external/env/auth blockers: Vercel previews for openwork-app, openwork-den, openwork-den-worker-proxy, and openwork-diagnostics report authorization-link failures; openwork-landing is pending

Manual verification

Not run — developer verification deferred.

1. Open Settings in the desktop app.
2. In the Cloud group, confirm OpenWork Connect shows a BETA badge.
3. Open OpenWork Connect with the organization capability disabled and confirm the pitch says Connect (beta).
4. Inspect a beta organization connection card/detail view and confirm the release-stage badges say Beta.

Evidence

• focused server-rendered regression test; no post-change video or screenshot captured

Risk

• low: presentation-only label and test/eval expectation changes; no runtime contracts or behavior changed

Rollback

• revert commit 5a51eb98a021e7db61e3dc1308d257ec3e069645

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Jul 22, 2026 7:49am

[vercel]

@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.