chore(brand): refresh the snapshot — the markers were rendering a stale catalog - #239
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: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe pull request updates automatic-routing savings claims from 87% to 88%. It also updates visible model counts in ChangesMetrics and documentation synchronization
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
VickyXAI
pushed a commit
that referenced
this pull request
Aug 8, 2026
…xt surfaces The brand fan-out PR (#239) updated every br:-marked occurrence of savings.autoVsBaselinePct but left package.json's "description" and skills/clawrouter/SKILL.md's frontmatter on 87%, because neither is marker-wrapped. src/router/brand-numbers.test.ts pins exactly those two, so main went red the moment that PR merged. Same shape as the seed-oss regression in v0.12.241: the fan-out maintains markers, and anything quoting a brand number OUTSIDE a marker is invisible to it. The guard test is what catches the gap — it did its job here. Both surfaces now read 88%. 716 tests pass, brand-numbers --check clean, prettier clean. No version bump: package.json's description ships in the npm metadata, but 0.12.243 is already published and this is a marketing string, not behaviour. It rides along with the next release.
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
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