Repository navigation
chore: refresh the generated catalog and limits tables - #151
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
chore/generated-refresh
branch
from
November 4, 2026 12:27
0f22c3e to
938762b
Compare
…nges The nightly regenerated `src/catalog-data.ts` for a vendor move — `DeepSeek V4 Pro (New)` renamed to `DeepSeek V4 Pro`, and one new free model, `crouton-alpha-free` — and the branch was opened with the generated file only, so six tests failed on it: the documents that COUNT the catalog, and the one place the count is written down on purpose. - Zen: **81 → 82** active models, `(absent)` SDK bucket **24 → 25**, free tiers **9 → 10**; - `README.md` and `README.zh-CN.md`: the routing table's `(absent)` row and both prose totals (and the measurement date, which moves with them); - `docs/protocol-routing-and-merge.md`: every `N of 81` row; - `docs/redirect-planes.md`: the served/listed cell, the `0 of 81` sentence and the plane-by-plane `(none)` cell; - `test/catalog.test.ts`: the two deliberate constants. They stay literal on purpose — a silent drop is a model nobody can pick, so a change has to be seen. `pnpm run catalog:shim` reports the shim current and `pnpm run limits:shim` reports the allowance table up to date, so the generated files and the vendor agree; the suite is 1332 green.
viztor
added a commit
that referenced
this pull request
Nov 4, 2026
Phase **P1a** of `docs/improvement-plan.md`, restacked onto 1.8.1. Most of what shipped broken in 1.4.1 is on `main` now (#133, #135), so this is what is left: - **Purge refusal.** The purge row shows the `message` of a refusal whose `error` is the remote protocol's serialized `RemoteError`. `main` reads only a string `message` or `error`, so that refusal was reported without its reason. - **The endpoint copy (D19).** The schema description, the `config-values` doc, the card's hint and Automatic label, both READMEs and `docs/redirect-planes.md` name the per-protocol inference family for `modern`, with `auto` as its alias. A test asserts that `auto` resolves exactly as `modern` does. - **`isZenProvider("opencode-google")` regression tests.** The predicate, its agreement with `catalogPlaneForRoute`, and the usage service's Zen fallback on that route. The fix itself is on `main`. - **Warning colour.** Both rows use the bare `var(--dsw-alias-state-warn-label)` — no token fallback, because the fallback is what hid the original bug — and `host-tokens.test.ts` checks every token the card files name against the host's primitives vocabulary. - **Catalog refusal tests.** Three cases `main` lacks: the Zen-plane 404 fill, the non-JSON 200 answer, and the `retry-after` passthrough. - **Debug rule (D24).** Naming `debugFile` writes the file; `debug` governs the console only. Dropped because `main` now does it: the wrapper fix (#135), the `isZenProvider` code change, the `enrichModelsResponse` passthrough, the spinner keyframes, the `parsePurgeResult` switch, P1a's `endpointModern` label, and P1a's debug gate. Restacked by rebasing the branch's net change onto 1.8.1 rather than merging `main` into it: the branch's own history is two merges of `main`, and replaying them would have carried the pre-refresh catalog back over #151.
viztor
added a commit
that referenced
this pull request
Nov 4, 2026
Phase **P1a** of `docs/improvement-plan.md`, restacked onto 1.8.1. Most of what shipped broken in 1.4.1 is on `main` now (#133, #135), so this is what is left: - **Purge refusal.** The purge row shows the `message` of a refusal whose `error` is the remote protocol's serialized `RemoteError`. `main` reads only a string `message` or `error`, so that refusal was reported without its reason. - **The endpoint copy (D19).** The schema description, the `config-values` doc, the card's hint and Automatic label, both READMEs and `docs/redirect-planes.md` name the per-protocol inference family for `modern`, with `auto` as its alias. A test asserts that `auto` resolves exactly as `modern` does. - **`isZenProvider("opencode-google")` regression tests.** The predicate, its agreement with `catalogPlaneForRoute`, and the usage service's Zen fallback on that route. The fix itself is on `main`. - **Warning colour.** Both rows use the bare `var(--dsw-alias-state-warn-label)` — no token fallback, because the fallback is what hid the original bug — and `host-tokens.test.ts` checks every token the card files name against the host's primitives vocabulary. - **Catalog refusal tests.** Three cases `main` lacks: the Zen-plane 404 fill, the non-JSON 200 answer, and the `retry-after` passthrough. - **Debug rule (D24).** Naming `debugFile` writes the file; `debug` governs the console only. Dropped because `main` now does it: the wrapper fix (#135), the `isZenProvider` code change, the `enrichModelsResponse` passthrough, the spinner keyframes, the `parsePurgeResult` switch, P1a's `endpointModern` label, and P1a's debug gate. Restacked by rebasing the branch's net change onto 1.8.1 rather than merging `main` into it: the branch's own history is two merges of `main`, and replaying them would have carried the pre-refresh catalog back over #151.
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.
The nightly freshness check found the vendor sources moved. Regenerated by CI - review the diff and merge.