Repository navigation
feat(web): v0.26 refresh — buddy page, changelog, partners, provider … - #2060
Conversation
…catalog - Single-source the site version from the root package.json (never stale again) - New /buddy/ page: all 7 hero sprites rendered as animated SVGs generated from src/buddy/pixelSprites.ts, attack descriptions, commands, hatch lore, plus a dedicated 1200x630 OG image composed from the real sprites - New /changelog/ page: curated release highlights 0.19 -> 0.26 from a typed releases.ts data file - Landing: buddy teaser section, partners strip (GitLawb, Bankr, Atomic Chat, Xiaomi MiMo, Atlas Cloud, AI/ML API, Novita AI) with self-hosted logos, community links, refreshed provider strip, node >= 22 fix - Providers docs rebuilt as grouped catalog (39 providers: subscriptions, gateways, vendors, local, custom) incl. xAI OAuth, AI/ML API, Cloudflare Workers AI, NVIDIA NIM, Kimi K3, GPT-5.6, Opengateway free models - Data refresh vs v0.26.0 source: 16 new slash commands, pdf skill, new CLI flags + 10 subcommands, modelLimits/providerFallbackChain/agentRouting settings, corrected env vars (GEMINI_API_KEY, OPENGATEWAY_API_KEY, ...) - Nav/footer/docs sidebar link the new pages; JSON-LD breadcrumbs on both Co-Authored-By: OpenClaude <openclaude@gitlawb.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (3)
🧰 Additional context used📓 Path-based instructions (4)**/*.{ts,tsx}📄 CodeRabbit inference engine (AGENTS.md)
Files:
**/*📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
⚙️ CodeRabbit configuration file
Files:
web/**/*.{ts,tsx}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
web/**⚙️ CodeRabbit configuration file
Files:
🔇 Additional comments (1)
📝 WalkthroughWalkthroughAdds Buddy and changelog pages, expands homepage content and navigation, reorganizes provider documentation into grouped catalogs, and updates documented CLI commands, flags, configuration, environment variables, and skills. ChangesSite experience
Provider documentation
CLI reference content
Estimated code review effort: 4 (Complex) | ~60 minutes 🚥 Pre-merge checks | ✅ 5 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
web/src/data/site.ts (1)
1-14: 📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy liftAdd coverage for the new TypeScript-driven public behavior.
The changed datasets drive site versioning, navigation, and three public routes, but this PR includes no test update. Add narrow tests using the existing web-test pattern for the rendered
/,/buddy/, and/changelog/routes, including version propagation and the new navigation links.
web/src/data/site.ts#L1-L14: verifySITE.versionmatches the root package version in rendered metadata/content.web/src/data/docsNav.ts#L31-L37: verify the flattened navigation exposes/changelog/and/buddy/.web/src/data/releases.ts#L5-L124: verify changelog entries render with their release URLs.web/src/data/buddy.ts#L5-L100: verify Buddy data renders on/buddy/.web/src/data/partners.ts#L4-L36: verify partner and community links render on/.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web/src/data/site.ts` around lines 1 - 14, Add narrow tests following the existing web-test pattern for the rendered /, /buddy/, and /changelog/ routes. In web/src/data/site.ts lines 1-14, verify SITE.version matches the root package version in rendered metadata/content; in web/src/data/docsNav.ts lines 31-37, verify flattened navigation includes /changelog/ and /buddy/; in web/src/data/releases.ts lines 5-124, verify changelog entries render their release URLs; in web/src/data/buddy.ts lines 5-100, verify Buddy data renders on /buddy/; and in web/src/data/partners.ts lines 4-36, verify partner and community links render on /.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/src/data/cliFlags.ts`:
- Line 118: Update the description of the --disable-slash-commands entry in the
CLI flags definition to state that it disables slash commands rather than
skills. Keep the flag name and behavior unchanged.
---
Outside diff comments:
In `@web/src/data/site.ts`:
- Around line 1-14: Add narrow tests following the existing web-test pattern for
the rendered /, /buddy/, and /changelog/ routes. In web/src/data/site.ts lines
1-14, verify SITE.version matches the root package version in rendered
metadata/content; in web/src/data/docsNav.ts lines 31-37, verify flattened
navigation includes /changelog/ and /buddy/; in web/src/data/releases.ts lines
5-124, verify changelog entries render their release URLs; in
web/src/data/buddy.ts lines 5-100, verify Buddy data renders on /buddy/; and in
web/src/data/partners.ts lines 4-36, verify partner and community links render
on /.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5ed17a45-402c-481a-8d32-a22ee82c1fca
⛔ Files ignored due to path filters (17)
web/public/buddy/corsair.svgis excluded by!**/*.svgweb/public/buddy/ember.svgis excluded by!**/*.svgweb/public/buddy/kage.svgis excluded by!**/*.svgweb/public/buddy/kaio.svgis excluded by!**/*.svgweb/public/buddy/merlin.svgis excluded by!**/*.svgweb/public/buddy/robinhood-action.svgis excluded by!**/*.svgweb/public/buddy/robinhood.svgis excluded by!**/*.svgweb/public/buddy/strawhat.svgis excluded by!**/*.svgweb/public/og/buddy.pngis excluded by!**/*.png,!**/*.pngweb/public/partners/aimlapi-logo-dark.svgis excluded by!**/*.svgweb/public/partners/aimlapi-logo.svgis excluded by!**/*.svgweb/public/partners/atlas-cloud.pngis excluded by!**/*.png,!**/*.pngweb/public/partners/atomic-chat-logo.pngis excluded by!**/*.png,!**/*.pngweb/public/partners/bankr.svgis excluded by!**/*.svgweb/public/partners/gitlawb.pngis excluded by!**/*.png,!**/*.pngweb/public/partners/mimo.svgis excluded by!**/*.svgweb/public/partners/novita-logo.pngis excluded by!**/*.png,!**/*.png
📒 Files selected for processing (16)
web/src/components/Footer.astroweb/src/components/Nav.astroweb/src/data/buddy.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/data/configuration.tsweb/src/data/docsNav.tsweb/src/data/partners.tsweb/src/data/providers.tsweb/src/data/releases.tsweb/src/data/site.tsweb/src/data/skills.tsweb/src/pages/buddy.astroweb/src/pages/changelog.astroweb/src/pages/docs/providers.astroweb/src/pages/index.astro
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
- GitHub Check: smoke-and-tests (22)
- GitHub Check: smoke-and-tests (24.11.x)
- GitHub Check: typecheck
🧰 Additional context used
📓 Path-based instructions (4)
**/*
📄 CodeRabbit inference engine (CONTRIBUTING.md)
**/*: Preserve existing repository patterns unless intentionally refactoring them.
Keep changes small, readable, and focused; avoid broad rewrites or unrelated cleanup.
Do not reformat unrelated files, and keep comments useful and concise.
Update documentation when setup, commands, or user-facing behavior changes.
Review AI-generated changes for correctness, style consistency, unnecessary noise, and adherence to project architecture before submitting them.
Provider changes must follow the documented integration patterns indocs/integrations/overview.mdand the focused guides underdocs/integrations/how-to/.
When changing provider behavior, avoid breaking third-party providers and test the exact provider/model path changed when possible.
Provider pull requests must explicitly identify affected providers, limitations, and follow-up work.
Run the narrowest meaningful validation command for the touched area, and ensure relevant CI checks pass before merging.
Usebun installto install dependencies and the repository's Bun scripts for building, testing, smoke testing, and development.
Dependency changes require a concrete project benefit such as a bug fix, security issue, or approved feature; preference alone is insufficient.
Do not change the project's language, core runtime, or dependency stack, or introduce a new runtime, without prior maintainer agreement.
Keep each pull request focused on one issue or clearly scoped improvement and avoid bundling unrelated fixes, features, or refactors.
Files:
web/src/components/Footer.astroweb/src/data/site.tsweb/src/pages/changelog.astroweb/src/data/releases.tsweb/src/data/buddy.tsweb/src/data/partners.tsweb/src/components/Nav.astroweb/src/data/docsNav.tsweb/src/pages/docs/providers.astroweb/src/pages/index.astroweb/src/data/skills.tsweb/src/data/configuration.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/pages/buddy.astroweb/src/data/providers.ts
⚙️ 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/components/Footer.astroweb/src/data/site.tsweb/src/pages/changelog.astroweb/src/data/releases.tsweb/src/data/buddy.tsweb/src/data/partners.tsweb/src/components/Nav.astroweb/src/data/docsNav.tsweb/src/pages/docs/providers.astroweb/src/pages/index.astroweb/src/data/skills.tsweb/src/data/configuration.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/pages/buddy.astroweb/src/data/providers.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/components/Footer.astroweb/src/data/site.tsweb/src/pages/changelog.astroweb/src/data/releases.tsweb/src/data/buddy.tsweb/src/data/partners.tsweb/src/components/Nav.astroweb/src/data/docsNav.tsweb/src/pages/docs/providers.astroweb/src/pages/index.astroweb/src/data/skills.tsweb/src/data/configuration.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/pages/buddy.astroweb/src/data/providers.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
TypeScript code in this repository must use strict mode and ESM imports.
**/*.{ts,tsx}: Add or update tests when a TypeScript or TSX change affects behavior.
Run the relevant TypeScript validation checks for changed code, includingbun run typecheckand, when applicable,bun run typecheck:type-tests.
Files:
web/src/data/site.tsweb/src/data/releases.tsweb/src/data/buddy.tsweb/src/data/partners.tsweb/src/data/docsNav.tsweb/src/data/skills.tsweb/src/data/configuration.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/data/providers.ts
web/**/*.{ts,tsx}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
When changing the web application, run
bun run web:typecheckandbun run web:build.
Files:
web/src/data/site.tsweb/src/data/releases.tsweb/src/data/buddy.tsweb/src/data/partners.tsweb/src/data/docsNav.tsweb/src/data/skills.tsweb/src/data/configuration.tsweb/src/data/cliFlags.tsweb/src/data/commands.tsweb/src/data/providers.ts
🔇 Additional comments (11)
web/src/data/commands.ts (2)
63-98: LGTM!Also applies to: 100-101, 111-113, 132-132, 144-145, 157-159
99-99: 🎯 Functional CorrectnessAlign or explicitly scope the effort-level contract.
The three catalogs list different accepted values. Verify the actual implementation and make the documentation consistent, or clearly explain why slash commands, CLI flags, and persisted settings intentionally support different levels.
web/src/data/commands.ts#L99-L99: confirm whetherautoandultracodeare valid slash-command values.web/src/data/cliFlags.ts#L57-L57: confirm whetherautoshould be documented for--effort.web/src/data/configuration.ts#L44-L44: confirm whetherultracodeand/orautoare valid foreffortLevel.web/src/data/cliFlags.ts (1)
48-48: LGTM!Also applies to: 75-75, 116-117, 119-121, 125-181
web/src/data/configuration.ts (1)
45-58: LGTM!Also applies to: 69-82
web/src/data/skills.ts (1)
2-2: LGTM!Also applies to: 16-17, 29-39
web/src/data/providers.ts (4)
1-20: LGTM!Also applies to: 22-48, 373-375
91-97: 🎯 Functional Correctness | ⚡ Quick winMissing
envVarswhere setup text says "env vars".
zai(Line 94:setup: '/provider or env vars') andcloud-routes(Line 343:setup: 'env vars') both point users at env vars but list noenvVarsarray, unlike every other entry using this setup string (e.g.dashscope,xiaomi-mimo-token). A reader following the "env vars" path here has nothing to go on.🩹 Suggested fix
{ id: 'zai', name: 'Z.AI GLM Coding Plan', group: 'subscriptions', setup: '/provider or env vars', + envVars: ['ZAI_API_KEY'], notes: 'GLM coding subscription endpoint; defaults to glm-5.2.', },{ id: 'cloud-routes', name: 'Bedrock / Vertex / Foundry', group: 'custom', setup: 'env vars', + envVars: ['CLAUDE_CODE_USE_BEDROCK', 'CLAUDE_CODE_USE_VERTEX'], notes: 'Anthropic-family cloud routes. Vertex is for Claude on Vertex AI, not arbitrary Model Garden models.', },(Adjust to the actual var names — verify against the real integration source.)
Also applies to: 339-345
106-114: 🗄️ Data Integrity & IntegrationTwo catalog entries share the same
MIMO_API_KEY, both badged 'sponsor'.
xiaomi-mimo-token(subscriptions) andxiaomi-mimo(vendors) list identicalenvVars: ['MIMO_API_KEY']but describe different endpoints (subscription plan vs. explicithttps://api.xiaomimimo.com/v1). If the underlying provider resolves by env var alone, settingMIMO_API_KEYcan't disambiguate which of the two profiles/base-URLs a user gets. Confirm this is intentional (e.g. distinguished by a separate base-URL var) rather than accidental duplication of one provider listed twice.Also applies to: 265-273
167-174: 🗄️ Data Integrity & IntegrationSkip this change —
BNKR_API_KEYis the correct Bankr env var. The repo uses it consistently in the Bankr integration and generated manifest.> Likely an incorrect or invalid review comment.web/src/pages/docs/providers.astro (2)
30-33: 🗄️ Data Integrity & IntegrationVerify
providerFallbackChainexists in the settings schema.This paragraph introduces a new settings key (
providerFallbackChain) that isn't defined anywhere in this file set. Since the configuration/CLI-reference layer (web/src/data/configuration.ts) is a separate cohort in this PR stack, confirm the key name and behavior described here (auto-retry on next profile) match what's actually documented/implemented there before this ships.
3-17: LGTM!Also applies to: 35-66, 82-97
…ation - Correct --disable-slash-commands description: the flag empties the entire slash-command list (REPL.tsx filters all commands), not just skills; the upstream help string "Disable all skills" is the misleading one - Add scripts/verify-dist.ts, wired into `bun run build` (so the existing CI web job runs it): asserts SITE.version matches the root package.json in the rendered pages, nav exposes /buddy/ and /changelog/, every release renders with its GitHub URL, every hero renders with its sprite asset, partner and community links render on the landing page, and the sitemap covers the new routes Co-Authored-By: OpenClaude <openclaude@gitlawb.com>
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/scripts/verify-dist.ts`:
- Around line 80-86: Add focused fixture-based tests for the verify-dist script,
covering missing or empty pages, stale links, missing sprites, and sitemap
failures. Exercise the failure aggregation and nonzero-exit behavior in the
verification flow, while preserving the existing successful verification path.
- Around line 39-44: Update the navigation verification loop for `/buddy/` and
`/changelog/` to assert that each route appears in the rendered docs navigation
output, rather than relying only on `docsPages.some(...)` and the landing-page
`expect(index, ...)` check. Reuse the existing rendered navigation content and
failure-reporting pattern in `verify-dist.ts`, while preserving the route
existence checks.
- Around line 16-27: Update expect() so content assertions run for empty HTML
strings instead of being skipped by the current truthiness check. Preserve the
existing missing-page failure behavior in page(), and ensure empty or
present-but-empty pages still produce a missing-needle failure when the expected
content is absent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 40b2ed46-defa-4da4-8d56-4699a45bf8b7
📒 Files selected for processing (3)
web/package.jsonweb/scripts/verify-dist.tsweb/src/data/cliFlags.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
- GitHub Check: smoke-and-tests (22)
- GitHub Check: smoke-and-tests (24.11.x)
- GitHub Check: typecheck
🧰 Additional context used
📓 Path-based instructions (4)
**/*
📄 CodeRabbit inference engine (CONTRIBUTING.md)
**/*: Preserve existing repository patterns unless intentionally refactoring them.
Keep changes small, readable, and focused; avoid broad rewrites or unrelated cleanup.
Do not reformat unrelated files, and keep comments useful and concise.
Update documentation when setup, commands, or user-facing behavior changes.
Review AI-generated changes for correctness, style consistency, unnecessary noise, and adherence to project architecture before submitting them.
Provider changes must follow the documented integration patterns indocs/integrations/overview.mdand the focused guides underdocs/integrations/how-to/.
When changing provider behavior, avoid breaking third-party providers and test the exact provider/model path changed when possible.
Provider pull requests must explicitly identify affected providers, limitations, and follow-up work.
Run the narrowest meaningful validation command for the touched area, and ensure relevant CI checks pass before merging.
Usebun installto install dependencies and the repository's Bun scripts for building, testing, smoke testing, and development.
Dependency changes require a concrete project benefit such as a bug fix, security issue, or approved feature; preference alone is insufficient.
Do not change the project's language, core runtime, or dependency stack, or introduce a new runtime, without prior maintainer agreement.
Keep each pull request focused on one issue or clearly scoped improvement and avoid bundling unrelated fixes, features, or refactors.
Files:
web/package.jsonweb/scripts/verify-dist.tsweb/src/data/cliFlags.ts
⚙️ 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/package.jsonweb/scripts/verify-dist.tsweb/src/data/cliFlags.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/package.jsonweb/scripts/verify-dist.tsweb/src/data/cliFlags.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
TypeScript code in this repository must use strict mode and ESM imports.
**/*.{ts,tsx}: Add or update tests when a TypeScript or TSX change affects behavior.
Run the relevant TypeScript validation checks for changed code, includingbun run typecheckand, when applicable,bun run typecheck:type-tests.
Files:
web/scripts/verify-dist.tsweb/src/data/cliFlags.ts
web/**/*.{ts,tsx}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
When changing the web application, run
bun run web:typecheckandbun run web:build.
Files:
web/scripts/verify-dist.tsweb/src/data/cliFlags.ts
🔇 Additional comments (7)
web/src/data/cliFlags.ts (1)
118-118: LGTM!web/package.json (1)
8-8: LGTM!web/scripts/verify-dist.ts (5)
4-14: LGTM!
29-37: LGTM!
46-52: LGTM!
54-61: LGTM!
63-78: LGTM!
…nav check, tests - page() now records a failure for a present-but-empty file, so '' is only ever returned alongside a recorded failure and skipped assertions can no longer mask a blank page - assert the rendered docs sidebar (dist/docs/) links every docsNav route, not just the source data array and the landing nav - extract pure verifyDist(dist) and add 9 fixture-based bun tests covering missing/empty pages, lost sidebar links, missing sprites, stale partner links, missing release URLs, and sitemap regressions; discovered by the root `bun test` run in CI, no workflow changes needed Co-Authored-By: OpenClaude <openclaude@gitlawb.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/scripts/verify-dist.test.ts`:
- Around line 90-92: Update the “flags a missing sprite asset” test to select an
existing hero from the heroes collection, derive its sprite filename and
expected failure path from that hero’s ID, and remove the hard-coded
robinhood.svg reference while preserving the verifyDist() assertion.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 25fe3d08-fc6d-4738-81d7-937053ff13d6
📒 Files selected for processing (2)
web/scripts/verify-dist.test.tsweb/scripts/verify-dist.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
- GitHub Check: smoke-and-tests (24.11.x)
- GitHub Check: typecheck
- GitHub Check: smoke-and-tests (22)
🧰 Additional context used
📓 Path-based instructions (4)
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
TypeScript code in this repository must use strict mode and ESM imports.
**/*.{ts,tsx}: Add or update tests when a TypeScript or TSX change affects behavior.
Run the relevant TypeScript validation checks for changed code, includingbun run typecheckand, when applicable,bun run typecheck:type-tests.
Files:
web/scripts/verify-dist.test.tsweb/scripts/verify-dist.ts
**/*
📄 CodeRabbit inference engine (CONTRIBUTING.md)
**/*: Preserve existing repository patterns unless intentionally refactoring them.
Keep changes small, readable, and focused; avoid broad rewrites or unrelated cleanup.
Do not reformat unrelated files, and keep comments useful and concise.
Update documentation when setup, commands, or user-facing behavior changes.
Review AI-generated changes for correctness, style consistency, unnecessary noise, and adherence to project architecture before submitting them.
Provider changes must follow the documented integration patterns indocs/integrations/overview.mdand the focused guides underdocs/integrations/how-to/.
When changing provider behavior, avoid breaking third-party providers and test the exact provider/model path changed when possible.
Provider pull requests must explicitly identify affected providers, limitations, and follow-up work.
Run the narrowest meaningful validation command for the touched area, and ensure relevant CI checks pass before merging.
Usebun installto install dependencies and the repository's Bun scripts for building, testing, smoke testing, and development.
Dependency changes require a concrete project benefit such as a bug fix, security issue, or approved feature; preference alone is insufficient.
Do not change the project's language, core runtime, or dependency stack, or introduce a new runtime, without prior maintainer agreement.
Keep each pull request focused on one issue or clearly scoped improvement and avoid bundling unrelated fixes, features, or refactors.
Files:
web/scripts/verify-dist.test.tsweb/scripts/verify-dist.ts
⚙️ 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/scripts/verify-dist.test.tsweb/scripts/verify-dist.ts
web/**/*.{ts,tsx}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
When changing the web application, run
bun run web:typecheckandbun run web:build.
Files:
web/scripts/verify-dist.test.tsweb/scripts/verify-dist.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/scripts/verify-dist.test.tsweb/scripts/verify-dist.ts
Hard-coding robinhood.svg would make the test throw during fixture mutation if that hero were renamed, instead of exercising verifyDist(). Co-Authored-By: OpenClaude <openclaude@gitlawb.com>
…ne#2065) Partial port (2/6 files): logo.svg + openclaude.png applied. The 4 og/{default,docs,commands,buddy}.png are skipped — og/buddy.png is new in Twigpine#2060 (v0.26 refresh) and OpenCC web/ hasn't ported the v0.26 batch yet. When 0f76b54 lands these 4 og/ files will arrive as part of that bigger port. Co-authored-by: Kevin Codex <kevin@gitlawb.com>
1 participant
Summary
package.json— the site hard-coded v0.18.0 while the product shipped v0.26.0; now it can never drift again/buddy/page: all 7 hero sprites rendered as animated SVGs generated fromsrc/buddy/pixelSprites.ts(pixel-identical to the terminal), attack descriptions, command reference, hatch/rarity lore, plus a custom 1200×630 OG card composed from the real sprites in Geist Mono/changelog/page: curated release highlights 0.19 → 0.26 from a typedreleases.ts, linking to GitHub releasesnode ≥ 22fixGEMINI_API_KEYnotGOOGLE_API_KEY, MiMo base URL, LM Studio env)/buddy,/ctx,/repomap, bughunters, …),pdfskill, 7 new CLI flags + 10 subcommands (auth xai,skills,doctor, …), new settings (modelLimits,providerFallbackChain,agentModels/agentRouting), corrected env vars; removed deprecated/hidden entries (output-style,keybindings-help,--max-budget-usd)Impact
pixelSprites.ts, don't hand-edit); web-only change, CLI untouchedTesting
bun run buildbun run smokebun run checkweb/only —bun run typecheck(astro check, 0 errors),bun run build(13 pages), linkinator full crawl (33/33 links 200), headless-Chrome screenshots of landing / buddy / changelog / providers in dark themeNotes
The root-repo checks are left unticked deliberately — this PR doesn't touch the CLI, and only the web-specific checks were actually run.
Summary by CodeRabbit
New Features
/buddyexperience (hero forms, stats/rarities, and ready-to-use/buddycommands) with a dedicated landing page./changelogpage with curated release highlights and deep links.Updates
Tests / Chores