chore(brand): refresh the snapshot — the markers were rendering a stale catalog - #374
Merged
Merged
Conversation
…le catalog Opened by brand/fanout-brand-numbers.mjs. brand-numbers.json here was behind the published artifact, so every br: marker in this repo rendered a number that is no longer true. The markers did their job — they rendered the input they were given. --check is offline on purpose so PR CI stays deterministic, which means it validates against this repo's own snapshot, and only --refresh updates that snapshot. This job is what runs it. Produced by --refresh, not by hand.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe change updates model counts and MCP context values in ChangesMetadata updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to This refreshes published model and context metadata with matching README formatting; no current merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
The brand fan-out bumped models.image 9 -> 10 inside a markdown table cell. One extra digit widened the column, which this repo's `format:check` (prettier --check .) rejects — the PR was red on formatting, not on content. README.md is prettier-clean on main, so the break came from the refresh, not from something pre-existing. `prettier --write README.md` realigns the table across 9 lines; both marker values (10) and brand-numbers.json are untouched and still read 10. Worth knowing for the next catalog change that crosses a digit boundary: the fan-out edits marker CONTENT and cannot know a consumer enforces table alignment. Any consumer with a format check will red the same way on 9->10, 99->100 and so on. The fix is mechanical; the surprise is not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GJ6wG4k5TgeUgYneCMz1oc
VickyXAI
pushed a commit
that referenced
this pull request
Sep 16, 2026
… hono patch, smoke-dist signer guard Rolls up everything on main since v0.12.278: the Desktop visual refresh (#367) with three corrected numbers, chain switches that restart the proxy Desktop owns (#371) and the deletion of the write-only AgentStatus.restartRequired (#379), the Desktop staged runtime's axios 0.27.2 relock (#376), the root overrides audit that patched hono and dropped two no-op pins (#380), the single-copy Solana signer guard in smoke-dist (#375), and the brand-numbers resync plus hardened sync script (#359, #374, #383, #388). dist/ is unchanged from v0.12.278 — no src/ commit landed in between. CLAWROUTER_PACKAGE_VERSION moves with package.json (runtime-version test); the Desktop runtime relock follows once npm serves 0.12.279.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
brand-numbers.jsonin this repo was behind the published artifact, so everybr:marker here rendered a stale number.The markers worked correctly — they rendered the input they had.
--checkis offline by design so PR CI stays deterministic, which means it validates against this repo's own snapshot; only--refreshupdates that snapshot.Opened automatically by
brand/fanout-brand-numbers.mjs. Produced by--refresh, no hand-edited digits.Summary by CodeRabbit
Documentation
Updates