chore(brand): refresh the snapshot — the markers were rendering a stale catalog - #2
Merged
Merged
Conversation
…le catalog brand-numbers.json here was a catalog generation behind, so every br: marker in this repo rendered a number that has not been true for some time. The markers did their job — they rendered the input they were given. Nothing refreshes that input: sync-brand-numbers.mjs reads the local snapshot and only re-fetches under --refresh, and --check is offline on purpose so PR CI stays deterministic. Its header defers freshness to a fan-out job that was never built, so every consumer validated markers against its own stale copy and reported green. Produced by --refresh, not by hand.
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 a catalog generation behind, so everybr:marker here rendered a stale number.The markers worked correctly — they rendered the input they had. Nothing refreshes that input.
sync-brand-numbers.mjsreads the local snapshot and only re-fetches under--refresh;--checkis offline by design so PR CI stays deterministic. The script header defers freshness to a fan-out job that was never built, so all 15 consumers have been validating markers against their own stale copies and reporting green.Measured across the org on 2026-08-05: 14 of 15 consumers stale, most at 66/86/8, ClawRouter at 65/85/7. Truth is 71 chat / 92 total / 6 free. Only ClawRouter-Hermes was current.
Produced by
node scripts/sync-brand-numbers.mjs --refresh— no hand-edited digits.The mirror (BlockRunAI/awesome-blockrun#34) is refreshed first, since it is what every other repo falls back to. The fan-out job itself follows in BlockRunAI/blockrun.