fix(bounties): stop the board skeleton reading its grid class across the client boundary

[jwalkingjew]

Stacked on #2478 — merge that first, then this. The diff against it is the bounties change alone.

The bug

app/bounties/loading.tsx is a Server Component. BountyBoardSkeleton puts BOARD_GRID_CLASS straight into a className, and that constant was declared in board-bounty-card.tsx, which is 'use client'.

Every export of a client module is a client reference on the server rather than the value it looks like — React writes it into the flight payload as an opaque placeholder. So the loading grid rendered with no grid classes at all, six placeholder blocks stacked in a column, until hydration replaced the whole loading state. BOARD_CARD_HEIGHT_PX went the same way into a style.

Found by the guard in #2478, where it was the one live case on the known-debt list.

The fix

Both constants move to board-layout.ts, which carries no directive.

That pulled the card heights along: BOARD_CARD_HEIGHT_PX is AVAILABLE_CARD_HEIGHT_PX, declared in bounty-card.tsx — also a client module — so putting the board's constants somewhere server-safe while leaving their input behind would have fixed nothing. The three sibling heights (COMPLETED_ / IN_PROGRESS_ / AVAILABLE_) go to bounty-card-layout.ts together, rather than splitting a set of three across two files for the next reader to puzzle over.

Both original modules re-export what they used to declare, so every existing importer — and every test that mocks them — is untouched. The only import that actually changes is the skeleton's, which is the one that crossed the boundary.

Verification

• 102 tests across partials/bounties, partials/community-tab and the guard pass; lint and tsc clean.
• The two entries come off test: guard against server components reading client-module values #2478's KNOWN list, and that test's staleness check is what enforces they had to — a fix that left them listed would fail it.
• The guard now protects the fix. Point the skeleton's import back at board-bounty-card and it fails with exactly the pair again:

partials/bounties/bounty-board-skeleton.tsx -> BOARD_CARD_HEIGHT_PX  (from partials/bounties/board-bounty-card.tsx)
partials/bounties/bounty-board-skeleton.tsx -> BOARD_GRID_CLASS      (from partials/bounties/board-bounty-card.tsx)

What I did not check

I have not watched the bounties loading state render, before or after. The mechanism is confirmed by inspection and by the same flight-payload evidence that motivated #2478, but the visual symptom — a brief unstyled flash on a route behind a testnet gate and a feature flag — I am taking on reasoning. Worth ten seconds from someone who can open the board.

[vercel]

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

Project	Deployment	Actions	Updated
geogenesis	Ready	Preview	Sep 25, 2026 1:25am UTC

[Copilot]

Copilot review overview

🟢 Approval recommended

The constants now cross the server boundary safely while preserving existing client-facing imports.

Review effort: Balanced
Findings: None

What changed in this PR

Moves bounty layout constants into server-safe modules, fixing the server-rendered loading skeleton.

Changes:

• Extracts card heights and board layout constants.
• Preserves existing imports through re-exports.
• Removes resolved cases from the server/client boundary guard.

File	Description
client-values-in-server-boundaries.test.ts	Removes fixed boundary violations.
bounty-card.tsx	Imports and re-exports extracted heights.
bounty-card-layout.ts	Defines server-safe card heights.
bounty-board-skeleton.tsx	Uses server-safe board constants.
board-layout.ts	Defines board grid and height constants.
board-bounty-card.tsx	Uses and re-exports extracted constants.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.