ci(ui-e2e-gate): wire the two orphaned cloud e2e runners

[lalalune]

Summary

Fixes a develop-red: packages/scripts/__tests__/ui-e2e-runner-coverage.test.ts (the ratchet ensuring every packages/ui __e2e__ runner has a package.json script + CI leg) was FAILING 1/1 on pristine origin/develop, found while verifying the #11628 CI-coverage sweep.

Two runners landed with no wiring:

• packages/ui/src/cloud/organization/__e2e__/run-credentials-e2e.mjs (feat(cloud-ui): org credentials tab + connect-link invite flow (#11332) #11488 org credentials tab)

• packages/ui/src/cloud/applications/__e2e__/run-frontend-hosting-e2e.mjs (Cloud apps platform review: make frontend/backend hosting, domains, analytics, SEO, ads & content-gen general for all users #10690 hosting work / feat(ui,app,plugins): UI/mobile gap burndown — slash-menu touch safety, spatial/tap-target gates, hosting UI, cloud-agent cold-boot, inbox port, lifecycle honesty (8 verified legs) #11425)

• Added test:credentials-e2e / test:frontend-hosting-e2e scripts to packages/ui/package.json, following the existing test:<name>-e2e convention.

• Added matching legs to .github/workflows/ui-e2e-gate.yml, after the existing runner legs, plus their output dirs to the artifact-upload path list. This workflow already triggers on packages/ui/src/** (ci(ui-e2e-gate): trigger on all of packages/ui/src — fixture runners bundle the whole tree #11628), so no path-filter changes were needed.

Local runner results (real headless-Chromium runs, real mock cloud stack — PGlite + Hono + live key-probe stub)

• bun run --cwd packages/ui test:frontend-hosting-e2e → ALL GREEN. Publish → v1 live → v2 live → rollback confirm → rolled-back-to-v1 → delete confirm → after-delete, desktop + mobile, plus the cloud-inactive (502) → retry-recovers assertion. Orange-accent / darker-orange-hover / no-blue aesthetic assertions all passed.
• bun run --cwd packages/ui test:credentials-e2e → ALL GREEN. Empty state → contribute (probe FAIL then probe PASS) → masked list row → disable/enable toggle → invite & connect link → connect-link landing → remove-confirm → delete, desktop + mobile, with the same aesthetic assertions plus "plaintext key never appears in the DOM" and "server confirms pool is empty after remove".

Neither runner needed any fix — both were fully working, just CI-orphaned.

Verification

• bun test packages/scripts/__tests__/ui-e2e-runner-coverage.test.ts → 1 pass / 0 fail (was failing on pristine develop before this change).
• actionlint .github/workflows/ui-e2e-gate.yml → clean.

Test plan

• Ratchet test passes locally
• Both new runners executed locally end-to-end, ALL GREEN
• actionlint clean on the modified workflow
• CI (rarely completes per repo convention; this local run is the merge gate)

🤖 Generated with Claude Code

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 50699c9b-1ccd-4854-869d-ee925b96ec52

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/wire-orphaned-ui-e2e-runners

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[lalalune]

Fable-5 takeover re-verification (post-rebase onto develop 7acf5a4a1a, new head 31a00d358b):

• Premise re-confirmed: on pristine origin/develop, both runner files exist but have 0 references in packages/ui/package.json and 0 in any .github/workflows/*.yml → ratchet red 1/1.
• Both runners re-run end-to-end by the verifier (headless Chromium, real mock cloud stack):
  • test:frontend-hosting-e2e → ALL GREEN (13 screenshots incl. 502 cloud-inactive → retry-recovers)
  • test:credentials-e2e → ALL GREEN (14 screenshots incl. probe-fail 401 inline, masked-key/no-plaintext-in-DOM, invite-link-carries-no-key-material, empty-pool-after-remove)
• bun test packages/scripts/__tests__/ui-e2e-runner-coverage.test.ts → 1 pass / 0 fail on the rebased head.
• actionlint .github/workflows/ui-e2e-gate.yml → clean.
• Legs sit after the ensure-shared-i18n-data + Playwright-install steps; artifact-upload paths match the runners' real outDirs (output-frontend-hosting, output-credentials).

No code changes were needed — rebase only. Verdict: READY_TO_MERGE.

🤖 Generated with Claude Code

[lalalune]

Same-account review note (no independent approval from me).

Local sparse validation on 31a00d358b:

• bun test packages/scripts/__tests__/ui-e2e-runner-coverage.test.ts -> 1 pass / 0 fail.
• git diff --check origin/develop...HEAD -> clean.
• Parsed .github/workflows/ui-e2e-gate.yml as UTF-8 YAML and verified the ui-fixture-e2e job has steps for:
  • bun run --cwd packages/ui test:frontend-hosting-e2e
  • bun run --cwd packages/ui test:credentials-e2e
• Verified packages/ui/package.json scripts point at the two existing runners:
  • packages/ui/src/cloud/applications/__e2e__/run-frontend-hosting-e2e.mjs
  • packages/ui/src/cloud/organization/__e2e__/run-credentials-e2e.mjs
• Verified artifact upload includes the two new output directories.

No findings. I did not rerun the two long browser e2e flows locally in this pass; I treated the PR's recorded green runs plus the ratchet as the relevant review signal here.

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.