feat(partners): add Concentrate and Exa to partner roster

[kevincodex1]

Summary

• Add Concentrate (https://concentrate.ai/) and Exa (https://exa.ai/) to the Partners section, rebalancing the README table to two rows of five.
• Mirror both entries in web/src/data/partners.ts so the landing page partner strip renders them with the theme-aware light/dark swap.
• Self-host light + dark logo variants in docs/assets/ and web/public/partners/:
  • Concentrate: official dot-cluster mark from their site favicon (#0D0E10 light variant; recolored #FFFFFF dark variant, matching their own black-on-light / white-on-dark treatment). Mark-only, same convention as Bankr — the table prints the partner name beneath.
  • Exa: official logo pair from their docs site (blue-E/black wordmark for light, all-white for dark) — no hand recoloring needed.

Impact

• README and web landing page only; no runtime/CLI code changes.
• README ↔ partners.ts rosters stay in sync (both updated in this PR).

Testing

• bun run typecheck in web/ (0 errors)
• bun run build in web/ — verify-dist: ok — navigation, buddy, and partners verified
• bun test web/scripts/verify-dist.test.ts (13 pass, 0 fail)
• Rendered all four SVGs on white and #0d1117 backgrounds via headless Chrome — both themes legible, no white matte

Notes

• Concentrate is also a gateway provider as of 084bc534, so the partner listing matches the product integration.
• Site deploy is separate: after merge, vercel --prod from web/ (assets live under web/public/, so the standalone deploy picks them up).

Summary by CodeRabbit

• New Features

  • Added Concentrate and Exa to the partner roster.
  • Added partner logos, links, and display details for light and dark themes.

• Documentation

  • Updated the README with Concentrate and Exa partner information.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9f6871c0-0bdb-43bd-b459-6bc24bd68685

📥 Commits

Reviewing files that changed from the base of the PR and between 645d596 and 242347f.

⛔ Files ignored due to path filters (8)

• docs/assets/concentrate-logo-dark.svg is excluded by !**/*.svg
• docs/assets/concentrate-logo.svg is excluded by !**/*.svg
• docs/assets/exa-logo-dark.svg is excluded by !**/*.svg
• docs/assets/exa-logo.svg is excluded by !**/*.svg
• web/public/partners/concentrate-logo-dark.svg is excluded by !**/*.svg
• web/public/partners/concentrate-logo.svg is excluded by !**/*.svg
• web/public/partners/exa-logo-dark.svg is excluded by !**/*.svg
• web/public/partners/exa-logo.svg is excluded by !**/*.svg

📒 Files selected for processing (2)

• README.md
• web/src/data/partners.ts

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (2)

• GitHub Check: smoke-and-tests (22)
• GitHub Check: smoke-and-tests (24.11.x)

🧰 Additional context used

📓 Path-based instructions (5)

**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

• TypeScript with strict mode and ESM imports.

**/*.{ts,tsx}: check for correctness, not just whether it compiles
Typecheck (enforced by the dedicated typecheck CI job):

Files:

• web/src/data/partners.ts

**/*

📄 CodeRabbit inference engine (AGENTS.md)

**/*: - Keep changes focused on one problem.

• Prefer existing patterns in the file or nearby module.
• Avoid unrelated formatting, renames, dependency changes, or broad rewrites.
• Add or update tests when behavior changes.
• Update docs when setup, commands, provider behavior, or user-facing behavior changes.
• chalk for terminal color.
• commander for CLI argument parsing.
• execa for child processes.

3. Check existing provider implementations before adding a new pattern.
4. Test the exact provider/model path you changed when possible.
5. Avoid breaking third-party providers while fixing first-party behavior.

• Do not change the Node runtime or Bun development workflow without prior maintainer agreement.
• Do not introduce dependencies without clear project benefit.
• Do not skip tests for behavior changes.
• Do not silently change provider tags; maintainers control them during review.
• Do not add a manually maintained release-notes data source to the static site; link to GitHub Releases instead.

**/*: Add or update tests when the change affects behavior.
Update docs when setup, commands, or user-facing behavior changes.
Preserve existing repo patterns unless the change is intentionally refactoring them.
Follow the existing code style in the touched files.
Prefer small, readable changes over broad rewrites.
Do not reformat unrelated files just because they are nearby.
Keep comments useful and concise.
Website release notes live on GitHub Releases. Do not add manually maintained release-note data to the static site.
Before contributing provider changes, review the relevant documentation to ensure your implementation follows the expected patterns:
be explicit about which providers are affected
avoid breaking third-party providers while fixing first-party behavior
test the exact provider/model path you changed when possible
verify style consistency with the rest of the codebase
remove unnecessary changes or auto-generated noise
confirm adherence to the p...

Files:

• web/src/data/partners.ts
• README.md

---

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

• web/src/data/partners.ts
• README.md

web/**/*

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Web (if touching web/):

Files:

• web/src/data/partners.ts

web/**

⚙️ CodeRabbit configuration file

web/**: Review browser extension changes for content-script isolation, message validation, cross-origin assumptions, permission surfaces, and failures that could leak prompts or credentials.

Files:

• web/src/data/partners.ts

{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}

⚙️ CodeRabbit configuration file

{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}: Review docs for accuracy against current code behavior. Flag security or provider claims that overpromise, stale install commands, missing setup caveats, and instructions that could push users toward unsafe credential handling. Keep purely wording-level suggestions non-blocking.

Files:

• README.md

🔇 Additional comments (2)

web/src/data/partners.ts (1)

41-54: LGTM!

README.md (1)

91-113: LGTM!

---

📝 Walkthrough

Walkthrough

Added Concentrate and Exa to the partner data roster and README, including URLs, light/dark logos, display heights, and partner-name links.

Changes

Partner roster updates

Layer / File(s)	Summary
Add partner listings web/src/data/partners.ts, README.md	The partner roster includes Concentrate and Exa with URLs, light/dark logo paths, and display heights. The README includes linked logo cells and partner names.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 24234

This PR adds two partner listings and their light/dark logo assets to the README and landing page without changing runtime behavior; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• Gitlawb/openclaude#2060: Extends the same partner roster in web/src/data/partners.ts.
• Gitlawb/openclaude#2121: Updates the same partner listings in README.md and web/src/data/partners.ts.

Suggested reviewers: jatmn, chioarub, techbrewboss

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, scoped to partners, and accurately describes adding Concentrate and Exa to the partner roster.
Description check	✅ Passed	The description covers the summary, impact, testing, and notes, with clear scope and validation results.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Risk Surface Disclosed	✅ Passed	The exact HEAD^..HEAD diff contains only README, partner data, and SVG assets; it does not touch any risk surface listed by this check, so disclosure is not applicable.
No Hidden Policy Change	✅ Passed	The parent-to-HEAD diff changes only README roster markup, partner data, and self-hosted SVG assets; it adds no product, trust, routing-default, telemetry/network, or permission-policy behavior.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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