feat(clusters): drop the unwired card metadata row and head the Clusters and Organizations pages with a plain title

[DavidCockerill]

Cluster cards no longer show the Instances / Regions / Harper version row: the organization response the list is built from carries no instances, so the instance count and version cells could only ever show a dash. The Clusters and Organizations pages now open with one plain heading in the primary colour instead of a slogan-and-tagline hero box, so the first row of cards sits about 120px higher. These are the same commits already on epic/pricing-updates, landed on stage ahead of the epic.

Closes #1770

Before and after

Dark mode, 1440px, mocked API (the anon e2e fixtures). Light captures were taken too and look the same apart from the palette.

Clusters, before	Clusters, after

Organizations, before	Organizations, after

For the human reviewer

1. Regions left the card with the row. The review's one surviving finding: the Regions cell did show real data (plan region labels resolved through the region catalog), and the region filter and the search box still match on region, so a filtered card no longer shows the region it matched on. Chosen: remove the whole row, as on the epic, and correct the design note so it no longer claims the row was all dashes. Alternative: keep a single region line on the card next to the hosting line. Reversing is a line or two of JSX; the model still derives regions for the filter. Cost of a "no": one extra commit here and a matching change on the epic.
2. Requirement. Removing the row is warranted: two of its three cells are a dash on every card today, and the central-manager endpoint that would populate them is not scheduled. The alternative is to leave the row until that endpoint exists, which keeps dashes in production for an unknown time.
3. Plain headings instead of the hero copy. Chosen: one h1 per page, no slogan or tagline. Cheap to reverse apart from the three e2e locators. The copy goes for three reasons:
   • It is a landing-page device on a work page. A slogan and tagline suit someone arriving cold; people who reach the clusters list already know what it is and come back many times a day, paying the same 120px on every visit for nothing.
   • It takes space from the thing the page is for. On a laptop the hero plus the new filter bar pushes the first row of cards near the fold, and the cards are the content.
   • The words fade fast. "At a glance" and "in one place" read fine once; by the twentieth visit they are wallpaper. Information-free text trains people to stop reading the top of the page, which then hurts anything real put there later, such as the expiry banner.
4. Verbatim cherry-picks, not a squash. Five commits are cherry-pick -x copies of the epic commits, byte-identical, so the epic's next rebase onto stage drops them by patch-id. Squashing would leave the epic five conflicting commits to resolve by hand. Cost of a "no": one squash commit here and a manual conflict pass on the epic later.
5. Model fields kept. clusterListModel.ts still derives instanceCount and version although nothing renders them. Removing them would touch a file the epic also changes and would turn restoring the row into a model change. Cost of a "no": two unrendered fields and their tests until the row returns.

Changes

• src/features/clusters/components/ClusterCard.tsx: the CardContent holding the three-cell dl is removed; the header and the progress/actions block are unchanged.
• src/features/clusters/ClustersList.tsx: the hero box (gradient card, eyebrow, slogan, tagline) becomes a plain header with one h1 reading Clusters in the primary colour, violet in dark mode, keeping the New Cluster button.
• src/features/organizations/index.tsx: the same treatment, an h1 reading Organizations replaces the eyebrow, slogan and tagline block.
• src/features/layouts/Dashboard.css: the .studio-shell .cluster-overview-hero override goes with the hero box it neutralised.
• src/features/clusters/DESIGN.md: the note no longer says the card shows instance count and version; it says the model derives them, that only those two cells were always a dash because the organization response does not currently expand instances, and that the Regions cell went with the row.

Verification

• pnpm exec tsc -b, pnpm lint, dprint check: clean.
• pnpm test:coverage: 381 files, 3522 tests passed, 11 skipped. ClusterCard.test.tsx no longer expects the region label or the two "Not reported" cells.
• pnpm build: built.
• End to end: the anon Playwright project run against this worktree's dev server, 48 passed, 1 skipped. clusters.anon.spec.ts, global-search.anon.spec.ts and organizations.anon.spec.ts assert the new Clusters and Organizations headings; the clusters spec still exercises the region filter and card navigation. Three failures in sign-in.anon.spec.ts and verifying.anon.spec.ts reproduce on a clean origin/stage checkout: getByLabel('Email') also matches the TanStack Router devtools button labelled /_authLayout/verify-email, which only renders on the pnpm dev server with VITE_DISABLE_DEVTOOLS unset. Not caused by this branch.
• e2e is not part of verify-pr; the trusted lane runs these specs against the deployed dev app after the merge to stage.

Complexity: easy

_{Review-Coverage: authored=claude; ran=gemini,codex; adjudicated=domain; declined=cursor-grok,cursor-composer,cursor-kimi,cursor-muse; rounds=1; full=1 @ 27078c7}

_{Human-Review-Need: 3 (decisions: drop-card-regions, keep-dead-model-fields, plain-page-headings) @ 22524e5}

[gemini-code-assist]

Code Review

This pull request simplifies the user interface by streamlining the headers on the Clusters and Organizations pages, removing the hero banners, sub-headings, and descriptions in favor of clean, direct titles. Additionally, it removes the Instances, Regions, and Harper version metadata fields from the ClusterCard component since the organization response does not provide instance data, preventing empty or placeholder values from being displayed. Corresponding updates have been made to the E2E tests, unit tests, CSS styles, and design documentation to reflect these changes. I have no feedback to provide as the changes are clean and consistent.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	66.43%	9854 / 14833
🔵	Statements	66.62%	10526 / 15799
🔵	Functions	59.67%	2534 / 4246
🔵	Branches	61.22%	7440 / 12152

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
src/features/clusters/ClustersList.tsx	96.66%	93.93%	93.33%	96.15%	128
src/features/clusters/components/ClusterCard.tsx	52.43%	82.35%	25.92%	53.16%	101-113, 117-118, 121, 124-155, 247-276, 351, 425-464
src/features/layouts/Dashboard.css	0%	0%	0%	0%
src/features/organizations/index.tsx	0%	0%	0%	0%	34-362

Generated in workflow #2037 for commit 27078c7 by the Vitest Coverage Report Action