Skip to content

chore(brand): refresh the snapshot — the markers were rendering a stale catalog - #51

Closed
VickyXAI wants to merge 1 commit into
mainfrom
chore/refresh-brand-numbers
Closed

chore(brand): refresh the snapshot — the markers were rendering a stale catalog#51
VickyXAI wants to merge 1 commit into
mainfrom
chore/refresh-brand-numbers

Conversation

@VickyXAI

Copy link
Copy Markdown
Contributor

brand-numbers.json in this repo was behind the published artifact, so every br: marker here rendered a stale number.

The markers worked correctly — they rendered the input they had. --check is offline by design so PR CI stays deterministic, which means it validates against this repo's own snapshot; only --refresh updates that snapshot.

Opened automatically by brand/fanout-brand-numbers.mjs. Produced by --refresh, no hand-edited digits.

…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.
@VickyXAI
VickyXAI force-pushed the chore/refresh-brand-numbers branch from bf33041 to 67e911f Compare August 31, 2026 06:02
VickyXAI pushed a commit that referenced this pull request Sep 5, 2026
`--check` was green because it only validates the keys a marker actually
renders, and those five were current. The rest of the snapshot had drifted:
withFallback 48 → 34, withFallbackAllEntries 89 → 73, aliases 229 → 259, plus
three mcp context keys the artifact now carries. No rendered number changes, so
this is not a docs fix — it stops the next marker added for one of those keys
from rendering a stale value on day one.

Produced by `scripts/sync-brand-numbers.mjs --refresh`, no hand-edited digits.

Supersedes #51, which proposed the same refresh against a 26 Aug main. Its five
rendered numbers have since landed independently, so the branch had nothing left
to deliver and conflicted with the API-key documentation merged in #59/#60.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMLNFbR6Jg2HBFpRUGBjyh
@VickyXAI

VickyXAI commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by b7e54a6 on main.

The five rendered numbers this branch carried (chatVisible 76, models.free 7, autoVsBaselinePct 84) have already landed on main independently — brand-numbers.json here is byte-identical to main's, so there was nothing left to merge. The branch also predates the API-key docs from #59/#60, which is where the conflict came from.

Ran --refresh against current main instead: the rendered keys were already current, but withFallback, withFallbackAllEntries, aliases and the mcp context keys had drifted. That's committed in b7e54a6.

@VickyXAI VickyXAI closed this Sep 5, 2026
@VickyXAI
VickyXAI deleted the chore/refresh-brand-numbers branch September 5, 2026 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant