@yanlinglabs/winter-provider-catalog 0.0.17 → 0.0.22

package/NOTICE

@@ -1,59 +1,41 @@
-NOTICE — third-party material in @yanlinglabs/winter-provider-catalog
-====================================================================
-
-NO THIRD-PARTY SOURCE CODE. As of this file's writing, this package contains no third-party source
-code, and no file in it was copied from any upstream project.
-
-Two upstream files ARE copied into this repository — but into `third_party/`, not here:
-
-  third_party/omniroute-provider-source/LICENSE   <- OmniRoute's root LICENSE (MIT), verbatim
-  third_party/omniroute-provider-source/NOTICE    <- OmniRoute's THIRD_PARTY_NOTICES.md, verbatim
-
-Both are registered with their upstream path, git blob id, sha256 and byte count in
-`third_party/omniroute-provider-source/extraction-manifest.json`, under `copiedFiles`, with
-`modifications: "none"`.
-
-Why the file exists anyway
---------------------------
-
-WS-13 §5 permits a narrow, deliberate exception: a *pure helper* may be copied from the OmniRoute
-provider corpus with clean per-file provenance. WS-13 §13's acceptance list then requires "notices
-cover copied files". This NOTICE is that register. It is empty of code entries on purpose, and an
-empty register is a stronger statement than a missing one: it says the exception has not been used,
-rather than leaving a reader to guess.
-
-If a future lane copies such a file, it appends an entry here naming the file, the upstream project,
-the exact commit, the upstream path, and the licence — and the copy is not merged without it.
-
-What IS derived from upstream, and how
---------------------------------------
-
-Catalog DATA (provider ids, endpoint templates, protocol families, auth kinds, model rows) is
-extracted from the pinned upstream tree into `generated/upstream-layer.json` and merged into
-`generated/catalog.json`. That is inert data, not code. Nothing in this package or anywhere in
-Winter imports, evaluates, or executes an upstream module: the extractor
-(`src/extract/literal-extractor.ts`) hands file TEXT to the TypeScript parser and walks object and
-array literals, rejecting every executable value into `generated/rejections.json`. WS-13 §13 states
-the rule directly — "no executable upstream URL builders", and "a catalog entry alone never causes
-code download or execution". Adapter behaviour is Winter-authored per protocol family (WS-13 §5),
-proven by the behavioural corpus.
-
-The extraction materialized 309 upstream files into a scratch checkout outside this repository and
-deleted it before the run finished. The two files listed above are the only ones that survived.
-
-The pinned source
------------------
-
-  repository  https://github.com/diegosouzapw/OmniRoute
-  tag         v3.8.50
-  tag object  6f5d4e00e817bc01b2ac16fdd66db3840c296416   (the ANNOTATED TAG, not a commit)
-  commit      5458026c216f77a3da68ea49152dc33470cfe2cb   (the tag, peeled)
-  licence     MIT, Copyright (c) 2026 diegosouzapw
-
-The MIT licence covers the source it was applied to. It does NOT grant permission to use a
-provider's consumer subscription, to copy user credentials from another product, to reach private or
-reverse-engineered endpoints, or any trademark right in provider names or logos. The provider logo
-tree is deliberately not imported by this work (report §12), and per-file intake review remains
-mandatory even under an MIT root — the audited upstream head carries retirement migrations for
-GPL-derived and provenance-hold integrations, which at this pinned tag have not yet landed
-(see PROVENANCE.md).
+NOTICE
+======
+
+Third-party attributions for the Winter agent SDK.
+
+This file records material that Winter DERIVED FROM third-party artifacts. Winter copies no source
+code from any of them; what it takes is protocol facts — endpoint URLs, form-field names, client
+identifiers and scope strings — which it needs in order to speak to a vendor's service at all. Each
+entry names the exact commit the values were read at, so the derivation is re-checkable.
+
+
+-------------------------------------------------------------------------------
+xai-org/grok-build
+-------------------------------------------------------------------------------
+
+    Repository:  https://github.com/xai-org/grok-build
+    Commit:      72a61251fcffb464bcc687aeb5a998e5a98ec0c9
+    License:     Apache License, Version 2.0
+                 https://www.apache.org/licenses/LICENSE-2.0
+    Copyright:   Copyright 2023-2026 SpaceXAI
+
+Winter's `xai-oauth` provider derives the following constants and request shapes from this
+repository's authentication module, in order to perform its own OAuth 2.0 device authorization
+grant (RFC 8628) against xAI's public, secret-less OAuth client:
+
+  - the public OAuth client identifier
+  - the OAuth issuer, device-authorization endpoint and token endpoint
+  - the requested scope set
+  - the name of the form field the flow carries a client identity in
+  - the shape (field names) of the device-authorization and token requests
+
+No source code from this repository is copied into Winter, and no part of Winter is a derivative
+work of it. The derivation is recorded, with per-value line citations, in:
+
+    packages/conformance/compat/xai/grok-build/derived-shapes-p6b-xai.md
+
+Winter identifies ITSELF in that flow. It sends its own `User-Agent` (`winter-agent-sdk/<version>`)
+and its own name in the flow's identity field, and it does not send xAI's product-identity or
+telemetry headers. Winter is not affiliated with or endorsed by SpaceXAI, and "Grok" and "Grok Build"
+are the marks of their owner; they appear here and in the capture solely to identify the artifact
+these values were derived from.

package/PROVENANCE.md

@@ -7,8 +7,8 @@ The committed catalog is the merge of two layers, performed by `scripts/provider
 
 | Layer | Source | Owner | Present |
 | --- | --- | --- | --- |
-| upstream | `generated/upstream-layer.json`, extracted from the pinned OmniRoute tree by `scripts/provider-source-sync.ts` | the extractor | **yes** — 106 providers, 540 models |
-| overlay | `overlay/providers.json` + `overlay/models.json`, hand-authored and reviewed | Winter | yes — 64 providers, 65 models |
+| upstream | `generated/upstream-layer.json`, extracted from the pinned OmniRoute tree by `scripts/provider-source-sync.ts` | the extractor | **yes** — 106 providers, 539 models |
+| overlay | `overlay/providers.json` + `overlay/models.json`, hand-authored and reviewed | Winter | yes — 64 providers, 117 models |
 
 **The overlay always wins.** WS-13 §7: live discovery and upstream extraction never silently
 overwrite `official-doc`/`live-probe` overlay entries, so a conflicting upstream row is dropped in
@@ -113,11 +113,11 @@ and wants to refresh this document by name — not a second gate.
 
 <!-- BEGIN GENERATED: admission-tier census (bun run scripts/provenance-tiers.ts) -->
 
-Generated from `generated/catalog.json` (`v3.8.50+winter.1`, 166 provider rows). Do not edit by hand.
+Generated from `generated/catalog.json` (`v3.8.50+winter.1`, 171 provider rows). Do not edit by hand.
 
 | Tier | Rows | What it means |
 | --- | ---: | --- |
-| **fetched-document** | 39 | a vendor page this repository retrieved and read, on a recorded date |
+| **fetched-document** | 44 | a vendor page this repository retrieved and read, on a recorded date |
 | **pinned-upstream** | 101 | the vendor's own site as the pinned upstream product catalog records it, plus that id's own pinned entry — a real, dated reference, but NOT a page read here |
 | **spec-ruling** | 4 | a ruling in an approved spec (or a user ruling recorded in one) admits the PATH; the row's own details are carried from a reviewed ledger entry — `anthropic`, `azure-ai`, `console`, `oci` |
 | **local** | 12 | a local installation on the operator's own machine — there is no third party to be admitted by — `docker-model-runner`, `lemonade`, `llama-cpp`, `llamafile`, `lm-studio`, `mlx-gemma`, `mlx-qwen`, `ollama-local`, `oobabooga`, `triton`, `vllm`, `xinference` |
@@ -315,7 +315,7 @@ unfalsifiable against its own source.
 
 ## What was excluded, and why
 
-`generated/rejections.json` carries all **722** rows. The counts below are generated from the ledger
+`generated/rejections.json` carries all **723** rows. The counts below are generated from the ledger
 and pinned by `catalog-integrity.test.ts` → *"PROVENANCE.md's exclusion table matches the ledger,
 row for row"*, because a hand-typed count is the line that goes stale first and nobody notices.
 
@@ -342,7 +342,7 @@ row for row"*, because a hand-typed count is the line that goes stale first and
 | `category-system` | 1 | `auto` is routing policy, which this layer bans |
 | `duplicate-id` | 1 | upstream's second `gpt-4o` |
 | `no-registry-entry` | 1 | `azure-openai` — catalogued upstream, with no backend entry |
-| **`out-of-scope`** | 1 | **`gemini-3.1-flash-tts-preview`** — a TEXT-TO-SPEECH model. WS-13 §4 is a MUST: `tts` rows never feed the worker-model picker, and `scope` is per PROVIDER, so a `gemini` row cannot declare itself `tts` while its provider is `llm`. Excluded through the allowlist's reviewed `modelOverrides`, never a name heuristic — a heuristic would silently drop a future model whose id happened to match |
+| **`out-of-scope`** | 2 | **`gemini-3.1-flash-tts-preview`** is a TEXT-TO-SPEECH model: WS-13 §4 is a MUST, so `tts` rows never feed the worker-model picker. **`deepseek-v4-flash`** is a retired legacy id that DeepSeek temporarily routes to canonical `deepseek-flash`; it is excluded from the stale upstream layer so the catalog has one canonical row with the legacy id as its alias. Both are reviewed `modelOverrides`, never name heuristics |
 
 **`unrepresentable-protocol` is the interesting one.** Upstream's `vertex` entry lists eleven
 `claude-*` models with `targetFormat: "claude"` — Claude models served over Vertex's endpoint in the
@@ -423,7 +423,7 @@ reviewed allowlist change" a property of the pipeline instead of a promise.
 ## Pricing
 
 `overlay/models.json` carries list prices for the cohort rows below, each with the vendor's own
-pricing page as `sourceRef` and the observation instant. The set is pinned by name in
+official pricing or model page as `sourceRef` and the observation instant. The set is pinned by name in
 `src/extract/catalog-integrity.test.ts`, so a row gaining or losing a price is a deliberate edit:
 
 | Model | Input | Output | Cache read | Cache write | Source |
@@ -436,10 +436,24 @@ pricing page as `sourceRef` and the observation instant. The set is pinned by na
 | `google/gemini-3.5-flash-lite` | 0.30 | 2.50 | 0.03 | — | ai.google.dev/gemini-api/docs/pricing |
 | `google/gemini-3.8-flash` | 0.75 | 3.75 | 0.075 | — | ai.google.dev/gemini-api/docs/pricing |
 | `openai/gpt-4.1` | 2.00 | 8.00 | 0.50 | — | developers.openai.com/api/docs/pricing |
+| `openai/gpt-4.1-mini` | 0.40 | 1.60 | 0.10 | — | developers.openai.com/api/docs/models/gpt-4.1-mini |
+| `openai/gpt-4.1-nano` | 0.10 | 0.40 | 0.025 | — | developers.openai.com/api/docs/models/gpt-4.1-nano |
+| `openai/gpt-4o` | 2.50 | 10.00 | 1.25 | — | developers.openai.com/api/docs/models/gpt-4o |
+| `openai/gpt-4o-2024-11-20` | 2.50 | 10.00 | 1.25 | — | developers.openai.com/api/docs/models/gpt-4o |
+| `openai/gpt-4o-mini` | 0.15 | 0.60 | 0.075 | — | developers.openai.com/api/docs/models/gpt-4o-mini |
+| `openai/gpt-5.4` | 2.50 | 15.00 | 0.25 | — | developers.openai.com/api/docs/models/gpt-5.4 |
+| `openai/gpt-5.4-mini` | 0.75 | 4.50 | 0.075 | — | developers.openai.com/api/docs/models/gpt-5.4-mini |
+| `openai/gpt-5.4-nano` | 0.20 | 1.25 | 0.02 | — | developers.openai.com/api/docs/models/gpt-5.4-nano |
+| `openai/gpt-5.4-pro` | 30.00 | 180.00 | — | — | developers.openai.com/api/docs/models/gpt-5.4-pro |
+| `openai/gpt-5.5` | 5.00 | 30.00 | 0.50 | — | developers.openai.com/api/docs/models/gpt-5.5 |
+| `openai/gpt-5.5-pro` | 30.00 | 180.00 | — | — | developers.openai.com/api/docs/models/gpt-5.5-pro |
+| `openai/gpt-5.6` | 4.00 | 20.00 | 0.40 | — | developers.openai.com/api/docs/models/gpt-5.6-sol |
 | `openai/gpt-5.6-luna` | 0.20 | 1.20 | 0.02 | — | developers.openai.com/api/docs/pricing |
 | `openai/gpt-5.6-sol` | 4.00 | 20.00 | 0.40 | — | developers.openai.com/api/docs/pricing |
 | `openai/gpt-5.6-terra` | 2.00 | 12.00 | 0.20 | — | developers.openai.com/api/docs/pricing |
 | `openai/gpt-6-astra` | 10.00 | 50.00 | 1.00 | 12.50 | developers.openai.com/api/docs/pricing |
+| `openai/o3` | 2.00 | 8.00 | 0.50 | — | developers.openai.com/api/docs/models/o3 |
+| `openai/o3-mini` | 1.10 | 4.40 | 0.55 | — | developers.openai.com/api/docs/models/o3-mini |
 | `openai/o4-mini` | 1.10 | 4.40 | 0.275 | — | developers.openai.com/api/docs/pricing |
 | `xai/grok-4.6` | 2.00 | 6.00 | 0.50 | — | docs.x.ai/docs/models |
 
@@ -596,3 +610,34 @@ document (`scanForSecrets`), and the extractor runs the **same** scan over the r
 a debug dump no output-side scan would ever see. Field names carrying credential or identity
 material (`oauth`, `anonymousApiKey`, `headers`, `extraHeaders`, `defaultHeaders`) are rejected on
 sight, whatever their shape. WS-13 §6 is categorical: descriptors never contain secrets.
+
+## Copied-files register (WS-13 §13)
+
+Moved here from this package's own `NOTICE` (P7a fix wave r3 (I3)), which now ships the root
+`NOTICE`'s Apache-2.0 `xai-org/grok-build` attribution byte-for-byte instead — `generated/
+catalog.json` cites that same repository, at the identical pinned commit, as the `sourceRef` for
+several xAI model-catalogue rows (`crates/codegen/xai-grok-models/default_models.json`), so this
+package is a genuine carrier of that derivation alongside `@yanlinglabs/winter-provider-runtime` and
+`@yanlinglabs/winter-provider-conformance`. This register is unrelated to that attribution; it is the
+WS-13 §13 acceptance requirement that "notices cover copied files", for the OmniRoute corpus.
+
+NO THIRD-PARTY SOURCE CODE. As of this section's writing, this package contains no third-party
+source code, and no file in it was copied from any upstream project.
+
+Two upstream files ARE copied into this repository — but into `third_party/`, not here:
+
+  third_party/omniroute-provider-source/LICENSE   <- OmniRoute's root LICENSE (MIT), verbatim
+  third_party/omniroute-provider-source/NOTICE    <- OmniRoute's THIRD_PARTY_NOTICES.md, verbatim
+
+Both are registered with their upstream path, git blob id, sha256 and byte count in
+`third_party/omniroute-provider-source/extraction-manifest.json`, under `copiedFiles`, with
+`modifications: "none"`.
+
+WS-13 §5 permits a narrow, deliberate exception: a *pure helper* may be copied from the OmniRoute
+provider corpus with clean per-file provenance. WS-13 §13's acceptance list then requires "notices
+cover copied files". This register is that register. It is empty of code entries on purpose, and an
+empty register is a stronger statement than a missing one: it says the exception has not been used,
+rather than leaving a reader to guess.
+
+If a future lane copies such a file, it appends an entry here naming the file, the upstream project,
+the exact commit, the upstream path, and the licence — and the copy is not merged without it.

package/README.md

@@ -43,4 +43,10 @@ a patch.
 
 MIT — see [`LICENSE`](./LICENSE), which ships in the published tarball.
 
-Third-party attribution for the upstream catalog data this package derives from is in [`NOTICE`](./NOTICE), which ships in the tarball beside this file.
+This package's generated catalog data cites the Apache-2.0 licensed `xai-org/grok-build` as the
+source for several xAI model-catalogue rows; that attribution is in [`NOTICE`](./NOTICE) — identical
+to the [root `NOTICE`](../../NOTICE) — which ships in the tarball beside this file.
+
+The separate OmniRoute-corpus extraction this package's catalog **data** is built from (no code
+copied, two licence/notice files registered verbatim under `third_party/`) is documented in
+[`PROVENANCE.md`](./PROVENANCE.md), which also ships in the tarball.

package/dist/extract/merge.d.ts

@@ -1,4 +1,4 @@
-import type { AdmissionTier, ModelFamilyDescriptor, ProviderProtocol, WinterCatalog, WinterModelDescriptor, WinterProviderDescriptor } from "../types.js";
+import type { AdmissionTier, CapabilityEvidence, ModelFamilyDescriptor, ModelPricing, ProviderProtocol, WinterCatalog, WinterModelDescriptor, WinterProviderDescriptor } from "../types.js";
 import type { ExclusionClass, LiteralValue, Rejection } from "./literal-extractor.js";
 export interface AllowlistProviderRow {
     upstreamId: string;
@@ -184,7 +184,15 @@ export declare function buildUpstreamLayer(input: BuildUpstreamLayerInput): Upst
 /** Total, stable rejection ordering: a ledger diff between two upstream bumps must show CHANGES, not churn. */
 export declare function compareRejections(a: LedgerRejection, b: LedgerRejection): number;
 /** The overlay files a re-sync must NEVER write. Exported so the sync script's own guard and its test read the same list. */
-export declare const OVERLAY_FILES: readonly ["overlay/providers.json", "overlay/models.json", "overlay/families.json"];
+export declare const OVERLAY_FILES: readonly ["overlay/providers.json", "overlay/models.json", "overlay/families.json", "overlay/pricing.json"];
+/** Exact provider/model price evidence. A price is not a model override: it must never erase fields extracted for the same row. */
+export type ModelPricingPatches = Record<string, CapabilityEvidence<ModelPricing>>;
+/**
+ * Applies the reviewed price-only overlay after a whole-row merge. The explicit unknown-key refusal
+ * makes a stale price row fail closed instead of becoming orphaned documentation after an upstream
+ * model rename.
+ */
+export declare function applyPricingPatches<T extends UnstampedModelDescriptor>(models: readonly T[], pricingPatches: Readonly<ModelPricingPatches>): T[];
 /**
  * The overlay-wins merge, mirroring `scripts/provider-catalog.ts`.
  *
@@ -210,4 +218,4 @@ export declare function mergeLayers(upstream: {
 }, overlay: {
     providers: WinterProviderDescriptor[];
     models: UnstampedModelDescriptor[];
-}, pin: WinterCatalog["upstream"], families?: readonly ModelFamilyDescriptor[]): WinterCatalog;
+}, pin: WinterCatalog["upstream"], families?: readonly ModelFamilyDescriptor[], pricingPatches?: Readonly<ModelPricingPatches>): WinterCatalog;

package/dist/index.d.ts

@@ -2,6 +2,7 @@ export type { CapabilityEvidence, CatalogValidationResult, EvidenceConfidence, E
 export { CATALOG_VOCABULARIES, scanForSecrets, validateCatalog } from "./validate.js";
 export { CLAUDE_FAMILY_ID, CLAUDE_RESERVED_SLOT_NAMES, CURRENCY_RE, FAMILY_ID_RE, OTHER_FAMILY_ID, SLOT_NAME_RE, canonicalModelIdOf, familyIdOf, familyOfModelKey, isSlotServableRow, modelFamilyOf, resolveSlotName, rowsForCanonicalId, stampFamilyFields, } from "./families.js";
 export type { SlotNameResolution } from "./families.js";
+export { CATALOG_TAG_RENAMES } from "./tag-renames.js";
 import type { WinterCatalog } from "./types.js";
 /**
  * The catalog compiled into this build.