Repository navigation
chore(brand): sync sync-brand-numbers.mjs from blockrun - #128
Merged
Merged
Conversation
Vendored copy update. blockrun/ci.yml's brand-script-sync fails on any drift from brand/sync-brand-numbers.mjs, so this must land before BlockRunAI/blockrun#469. Fixes in this build: markers inside fenced blocks can opt in with @LiVe and any that silently drift are now reported; fence offsets are recomputed per marker (a badge expands 2 chars to ~150 and shifted every later fence test); an unterminated fence now runs to EOF instead of un-fencing the tail; and the walk is filtered through git ls-files, which the header always claimed but never did.
VickyXAI
added a commit
that referenced
this pull request
Sep 15, 2026
…nothing in scripts/ moves money by being run - publish.yml refuses a package.json version BELOW npm latest (npm publish does not compare semver — a typo'd 0.5.1 would have become `latest` and downgraded every npx user), and the tag/release step is gated on the tag being ABSENT rather than on `pkg != npm`: a job that went red after the npm publish could never be repaired by a re-run, because the re-run found npm == pkg and skipped the step green. - brand-sync.yml: the direct push always fails on a protected main and GITHUB_TOKEN cannot open PRs here, and `|| echo` swallowed that too — the run went green having landed nothing, and a stale count sat in the README for 26 days behind a green badge. A drift the job cannot land is now a red run, from one fixed force-pushed branch. - verify:prices exits 2 when it could not look (too many `?` rows, an unreadable catalogue) instead of 0 — the day the gateway renames a header field, every row prints `?` and the release gate must not go green. The account rail's public pricing sheet is swept as a third catalogue (its other routes cannot be quoted without a key that would be charged, and the header says so). A probe row the CLIENT refuses (seedance-2.5@1080p) is marked as expecting an unpaid 4xx, now that blockrun PR #353 has deployed and the gateway refuses it too. - The live Polymarket e2e scripts require --confirm (or POLYMARKET_E2E_CONFIRM=1) before signing anything; every script installs the redacted exit handler so a thrown RPC error cannot print the wallet address the header promises to hide; the read-only preflight reports an outage as an error instead of `positions: []`. - smoke-speech prints the charge it computes from the estimator instead of a typed figure that understated it. - sync-brand-numbers.mjs documents why this copy is ahead of the source, so the next "copy the source over the consumer" remediation does not erase the render guard again (#84, #128). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Vendored copy of
brand/sync-brand-numbers.mjsfrom BlockRunAI/blockrun.blockrun's
ci.ymlrunsbrand-script-sync, which compares every consumer's copy against the canonical one and fails on drift. This PR must land before BlockRunAI/blockrun#469, which carries the canonical change and is red until the consumers update.Four fixes in this build:
--check, so a number in an ASCII diagram went stale under a green build. They can now opt in with@live, and any fenced marker whose value actually disagrees with the artifact is reported (non-fatal).Only git-tracked files are rewrittenwas in the header but nothing implemented it. Now filtered throughgit ls-files, falling back to the full walk outside a git checkout.No change to this repo's numbers — script only. Opened by a propagation run, not hand-edited.