feat: consume the published brand-numbers artifact - #3
Merged
Conversation
The model count here was hand-maintained and stale against the live catalog. It now regenerates from blockrun.ai/brand/numbers.json via markers, and CI fails offline against a committed snapshot when it disagrees. scripts/sync-brand-numbers.mjs is vendored byte-for-byte from BlockRunAI/blockrun:brand/ — a package would mean a dependency bump in every consuming repo, and several have no package manifest at all. blockrun CI diffs the copies, so this one cannot quietly fall behind.
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.
Wires this repo into the brand-numbers system from blockrun#288.
The model count was hand-maintained and stale against the live catalog. It now regenerates from
blockrun.ai/brand/numbers.jsonvia markers:The number stays literal in the source, so the README renders normally on GitHub — the comments are inert there.
CI
sync-brand-numbers.mjs --checkruns on every PR, offline by design: it compares against the committedbrand-numbers.jsonand never fetches, so a blockrun.ai deploy in progress cannot fail this repo. Pulling a newer artifact is a separate deliberate act (--refresh).Vendored script
scripts/sync-brand-numbers.mjsis byte-for-byte fromBlockRunAI/blockrun:brand/. A package would mean a dependency bump in every consuming repo, and several have no package manifest at all. blockrun CI diffs all copies, so this one cannot quietly fall behind.Left alone
Numbers that describe this repo rather than the gateway — its own tool count, its own curated allowlist, its own supported payment chains — are untouched. Same words, different subjects.