Repository navigation
docs: migration count 178 -> 181 in README, AGENTS.md and llm.txt - #14559
Merged
Merged
Conversation
…mirrors) The Docs Gates job was red on the release tip: three migrations landed (179, 180, 181) without the count claims being touched. check:docs-counts is green again; the 66 llm.txt mirrors regenerated with sync-llm-mirrors.
Owner
Author
|
CI: every red is the base tip's (this PR changes six numeric claims in README.md, AGENTS.md, llm.txt and regenerates the llm.txt mirrors). The 15 failing unit test files are the same set reproduced on the pure tip |
diegosouzapw
pushed a commit
that referenced
this pull request
Sep 22, 2026
…ry (#14544) Merged — closes #11725. Thank you, @RaviTharuma. Correlating the credential CLIProxyAPI actually selected with the usage row is the kind of plumbing that only pays off later, when someone is trying to work out *which* account burned the quota. Storing the opaque `auth_index` on all three paths (success, streaming, error) with a backfill when the first write missed the header, and resolving the human-readable label at **read** time from the sanitized account-health projection, is the right split: the column never holds an email, a path, a token or a raw management payload, and a missing or unrecognized header stays unattributed instead of failing the request. Validation before merge: boarded onto the release tip with the other seven PRs of your batch, then reconciled twice as the branch moved under it. - **First move:** #14559 (another session) corrected the docs migration count 178 → 181, colliding with this PR on 69 files — `README.md`, `AGENTS.md`, `llm.txt` and 66 i18n `llm.txt` mirrors, 270 hunks. All 270 were proven mechanically to be pure numeral collisions (base 178 / ours 182 / theirs 181, byte-identical otherwise), and the resolution keeps the tip's exact line shape with 182. I checked separately that no mirror lost its translated prose: 270 removed lines and 270 added lines, each pair identical but for the numeral. - **Second move:** #14069 landed and both sides had *added* a new top-level `_rebaseline_*` key to `config/quality/file-size-baseline.json` — an add/add, so both were kept and #14069's entry is intact. The 182 is verified, not carried over: the tip has 181 migration files and this PR adds `185_usage_history_cpa_auth_index.sql`. `check:migration-numbering` reports `182 migrations, 0 duplicates` and `check:docs-counts-sync` passes its STRICT migration-count assertion across all four claim sites. `cpa-trace-auth-index` + `cpa-auth-index-usage` + `db/migration-185-cpa-auth-index` + `chatcore-failure-usage` 12 pass / 0 fail. `check:file-size` OK — note your `chatCore.ts` ceiling is now 6402, measured after the commit; that file had been sitting at exactly 6400 with zero headroom since #14213. `typecheck:core` reports exactly one error, and it is **not yours**: `src/lib/services/cliproxyAccountHealth.ts` TS2322 on `host: options.host ?? externalHost`. That expression is byte-identical on the pure tip at line 146 — this PR only shifts it to 157 by adding `labelForCliproxyAuthIndex` above — and it touches neither the `host: string` type nor `externalHost`. Inherited base defect, tracked separately. Two things your PR did that I want to name, since both were on my checklist and neither needed a bounce: you bumped the migration count in `AGENTS.md`/`llm.txt` yourself (those are agent-instruction surfaces, so I confirmed the change was purely the numeral before merging), and in doing so you drained the 178 → 181 docs drift the previous batch had deferred. A leftover for someone else: `docs/i18n/fr/README.md` and `docs/i18n/phi/README.md` still say 178 — #14559 updated the `llm.txt` mirrors but missed the README ones. Pre-existing on the tip, outside this diff.
5 tasks done
diegosouzapw
added a commit
that referenced
this pull request
Sep 24, 2026
…irement, extracted failure projection - docs: migration count 182 -> 183 in README, AGENTS.md and llm.txt (+ the 66 llm.txt mirrors), same shape as #14559; migration 185 landed with #14544. - #14468 retired suno: APIKEY_PROVIDERS 242 -> 241 and the translate-path golden loses the suno entry (regenerated; that is the only diff). - #14527 moved the retained provider-failure projection into chatCore/providerFailureRetention.ts; the public-error guard now follows the call and still requires sanitizeErrorMessage() at the projection. Refs #14496
BenjaminAronsson
added a commit
to BenjaminAronsson/OmniRoute
that referenced
this pull request
Oct 3, 2026
Rebase onto release/v3.8.51 surfaced three problems. Migration 185 collided with 185_usage_history_cpa_auth_index from diegosouzapw#14544, which the migration runner rejects outright. Renumbered to 186; no retroactive isSchemaAlreadyApplied guard is needed because this migration has never shipped under the old number. The SSO branch claimed any RS256 JWT bearer even with SSO switched off, so a client sending its own unrelated JWT — extractBearer already notes VS Code Copilot does this — would hard-401 instead of degrading to anonymous under REQUIRE_API_KEY=false. It is now gated on isEntraSsoEnabled(), which answers false if the settings read throws so an unreadable config falls through to the pre-SSO path rather than 500-ing auth. The new test is RED against the previous commit. The migration count landed off by one: diegosouzapw#14559 had already moved the docs to 181 and the base to 182, and the rebase merged both edits cleanly into a number that no longer matched the 183 files on disk.
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.
Summary
Docs Gates(check:docs-counts) is red on the release tip: README.md, AGENTS.md and llm.txt still say 178 migrations whilesrc/lib/db/migrations/has 181 (three landed since without the claims being touched). This bumps the six claims and regenerates the 66docs/i18n/<locale>/llm.txtmirrors withscripts/i18n/sync-llm-mirrors.mjs.Touches
AGENTS.md(agent-instruction surface) — one numeric claim only, no rule text; merge explicitly approved by the operator in chat on 2026-09-22.Validation
npm run check:docs-countsnpm run check:docs-sync(pre-commit)