fix(finance): label OHIO_SOS as "Ohio Secretary of State"

[shu1513]

What

FINANCE_SOURCE_LABELS in packages/api-client/src/format.ts had no OHIO_SOS entry, so the finance summary source line fell through to the fallback title-caser and rendered "Ohio Sos" in both the web and mobile UI. Ohio finance shipped in #545/#546 and is live in prod, so this was user-visible today.

Adds OHIO_SOS: "Ohio Secretary of State", placed alphabetically between NEW_MEXICO_CFIS and OKLAHOMA_GUARDIAN, and extends the existing financeSourceLabel test.

The key matches the backend enum in backend/src/pipeline/address/ballotLookupFinanceShared.ts:95. Mobile shares the same FinanceSummaryCard and api-client, so it picks up the fix too.

Testing

• npm run typecheck in frontend/ — passes
• npm test in frontend/ — 460 tests / 41 files pass (the api-client tests run through frontend's vitest config)
• Verified in the browser against local Ohio data: the finance card now reads "Source: Ohio Secretary of State · 2026 cycle"

Note

OHIO_CAMPAIGN_FINANCE_ENABLED was missing from the local backend/.env (not in this repo), which hides the Ohio finance card locally. Added out-of-band along with the sync flag — prod was unaffected since render.yaml already sets it.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@shu1513, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: bc0cb657-c29a-4804-ad73-54c2a070412b

📥 Commits

Reviewing files that changed from the base of the PR and between aee455b and fbde2bb.

📒 Files selected for processing (2)

• packages/api-client/src/format.test.ts
• packages/api-client/src/format.ts

---

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.}