@yanlinglabs/winter-provider-catalog 0.0.3 → 0.0.5

package/dist/index.js

@@ -15936,6 +15936,110 @@ var catalog_default = {
       canonicalModelId: "hcx-007",
       modelFamily: "other"
     },
+    {
+      key: "codex-oauth/gpt-5.6-luna",
+      providerId: "codex-oauth",
+      upstreamId: "gpt-5.6-luna",
+      displayName: "GPT-5.6 Luna (Codex)",
+      aliases: [],
+      endpoints: [
+        "responses"
+      ],
+      contextWindow: {
+        value: 272000,
+        source: "upstream-static",
+        sourceRef: "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        confidence: "declared",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      inputModalities: {
+        value: [
+          "text",
+          "image"
+        ],
+        source: "upstream-static",
+        sourceRef: "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        confidence: "declared",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      outputModalities: {
+        value: [
+          "text"
+        ],
+        source: "winter-default",
+        sourceRef: "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        confidence: "unknown",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      toolCalling: {
+        value: "native",
+        source: "upstream-static",
+        confidence: "inferred",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      nativeTools: {
+        value: true,
+        source: "upstream-static",
+        confidence: "inferred",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      reasoning: {
+        supported: {
+          value: true,
+          source: "upstream-static",
+          confidence: "inferred",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        efforts: [
+          "low",
+          "medium",
+          "high"
+        ],
+        defaultEffort: "medium",
+        continuation: "opaque-provider-state",
+        readableState: {
+          value: "summary",
+          source: "official-doc",
+          sourceRef: "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        summaryRequest: {
+          value: {
+            field: "reasoning.summary",
+            values: [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          source: "official-doc",
+          sourceRef: 'continuity report §5.1 — the Responses surface\'s summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: "summary"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.',
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        completionEvent: {
+          value: "response.completed",
+          source: "upstream-static",
+          sourceRef: "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        continuationDomain: {
+          value: [
+            "codex-oauth/gpt-5.6-luna"
+          ],
+          source: "official-doc",
+          sourceRef: 'continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma\'s shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: "OpenAI-compatible" is never the capability test.',
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        }
+      },
+      unsupportedParameters: [],
+      status: "candidate",
+      canonicalModelId: "gpt-5.6-luna",
+      modelFamily: "gpt"
+    },
     {
       key: "codex-oauth/gpt-5.6-sol",
       providerId: "codex-oauth",
@@ -16040,6 +16144,110 @@ var catalog_default = {
       canonicalModelId: "gpt-5.6-sol",
       modelFamily: "gpt"
     },
+    {
+      key: "codex-oauth/gpt-5.6-terra",
+      providerId: "codex-oauth",
+      upstreamId: "gpt-5.6-terra",
+      displayName: "GPT-5.6 Terra (Codex)",
+      aliases: [],
+      endpoints: [
+        "responses"
+      ],
+      contextWindow: {
+        value: 272000,
+        source: "upstream-static",
+        sourceRef: "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        confidence: "declared",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      inputModalities: {
+        value: [
+          "text",
+          "image"
+        ],
+        source: "upstream-static",
+        sourceRef: "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        confidence: "declared",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      outputModalities: {
+        value: [
+          "text"
+        ],
+        source: "winter-default",
+        sourceRef: "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        confidence: "unknown",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      toolCalling: {
+        value: "native",
+        source: "upstream-static",
+        confidence: "inferred",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      nativeTools: {
+        value: true,
+        source: "upstream-static",
+        confidence: "inferred",
+        observedAt: "2026-09-11T00:00:00Z"
+      },
+      reasoning: {
+        supported: {
+          value: true,
+          source: "upstream-static",
+          confidence: "inferred",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        efforts: [
+          "low",
+          "medium",
+          "high"
+        ],
+        defaultEffort: "medium",
+        continuation: "opaque-provider-state",
+        readableState: {
+          value: "summary",
+          source: "official-doc",
+          sourceRef: "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        summaryRequest: {
+          value: {
+            field: "reasoning.summary",
+            values: [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          source: "official-doc",
+          sourceRef: 'continuity report §5.1 — the Responses surface\'s summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: "summary"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.',
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        completionEvent: {
+          value: "response.completed",
+          source: "upstream-static",
+          sourceRef: "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        },
+        continuationDomain: {
+          value: [
+            "codex-oauth/gpt-5.6-terra"
+          ],
+          source: "official-doc",
+          sourceRef: 'continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma\'s shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: "OpenAI-compatible" is never the capability test.',
+          confidence: "declared",
+          observedAt: "2026-09-11T00:00:00Z"
+        }
+      },
+      unsupportedParameters: [],
+      status: "candidate",
+      canonicalModelId: "gpt-5.6-terra",
+      modelFamily: "gpt"
+    },
     {
       key: "codex-oauth/gpt-6-astra",
       providerId: "codex-oauth",

package/generated/catalog.json

@@ -15229,6 +15229,110 @@
       "canonicalModelId": "hcx-007",
       "modelFamily": "other"
     },
+    {
+      "key": "codex-oauth/gpt-5.6-luna",
+      "providerId": "codex-oauth",
+      "upstreamId": "gpt-5.6-luna",
+      "displayName": "GPT-5.6 Luna (Codex)",
+      "aliases": [],
+      "endpoints": [
+        "responses"
+      ],
+      "contextWindow": {
+        "value": 272000,
+        "source": "upstream-static",
+        "sourceRef": "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "inputModalities": {
+        "value": [
+          "text",
+          "image"
+        ],
+        "source": "upstream-static",
+        "sourceRef": "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "outputModalities": {
+        "value": [
+          "text"
+        ],
+        "source": "winter-default",
+        "sourceRef": "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        "confidence": "unknown",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "toolCalling": {
+        "value": "native",
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "nativeTools": {
+        "value": true,
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "reasoning": {
+        "supported": {
+          "value": true,
+          "source": "upstream-static",
+          "confidence": "inferred",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "efforts": [
+          "low",
+          "medium",
+          "high"
+        ],
+        "defaultEffort": "medium",
+        "continuation": "opaque-provider-state",
+        "readableState": {
+          "value": "summary",
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "summaryRequest": {
+          "value": {
+            "field": "reasoning.summary",
+            "values": [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface's summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: \"summary\"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "completionEvent": {
+          "value": "response.completed",
+          "source": "upstream-static",
+          "sourceRef": "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "continuationDomain": {
+          "value": [
+            "codex-oauth/gpt-5.6-luna"
+          ],
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma's shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: \"OpenAI-compatible\" is never the capability test.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        }
+      },
+      "unsupportedParameters": [],
+      "status": "candidate",
+      "canonicalModelId": "gpt-5.6-luna",
+      "modelFamily": "gpt"
+    },
     {
       "key": "codex-oauth/gpt-5.6-sol",
       "providerId": "codex-oauth",
@@ -15333,6 +15437,110 @@
       "canonicalModelId": "gpt-5.6-sol",
       "modelFamily": "gpt"
     },
+    {
+      "key": "codex-oauth/gpt-5.6-terra",
+      "providerId": "codex-oauth",
+      "upstreamId": "gpt-5.6-terra",
+      "displayName": "GPT-5.6 Terra (Codex)",
+      "aliases": [],
+      "endpoints": [
+        "responses"
+      ],
+      "contextWindow": {
+        "value": 272000,
+        "source": "upstream-static",
+        "sourceRef": "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "inputModalities": {
+        "value": [
+          "text",
+          "image"
+        ],
+        "source": "upstream-static",
+        "sourceRef": "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "outputModalities": {
+        "value": [
+          "text"
+        ],
+        "source": "winter-default",
+        "sourceRef": "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        "confidence": "unknown",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "toolCalling": {
+        "value": "native",
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "nativeTools": {
+        "value": true,
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "reasoning": {
+        "supported": {
+          "value": true,
+          "source": "upstream-static",
+          "confidence": "inferred",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "efforts": [
+          "low",
+          "medium",
+          "high"
+        ],
+        "defaultEffort": "medium",
+        "continuation": "opaque-provider-state",
+        "readableState": {
+          "value": "summary",
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "summaryRequest": {
+          "value": {
+            "field": "reasoning.summary",
+            "values": [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface's summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: \"summary\"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "completionEvent": {
+          "value": "response.completed",
+          "source": "upstream-static",
+          "sourceRef": "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "continuationDomain": {
+          "value": [
+            "codex-oauth/gpt-5.6-terra"
+          ],
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma's shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: \"OpenAI-compatible\" is never the capability test.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        }
+      },
+      "unsupportedParameters": [],
+      "status": "candidate",
+      "canonicalModelId": "gpt-5.6-terra",
+      "modelFamily": "gpt"
+    },
     {
       "key": "codex-oauth/gpt-6-astra",
       "providerId": "codex-oauth",

package/overlay/models.json

@@ -952,6 +952,212 @@
       "unsupportedParameters": [],
       "status": "candidate"
     },
+    {
+      "key": "codex-oauth/gpt-5.6-terra",
+      "providerId": "codex-oauth",
+      "upstreamId": "gpt-5.6-terra",
+      "displayName": "GPT-5.6 Terra (Codex)",
+      "aliases": [],
+      "$comment": "Winter-owned (D11), authored 2026-09-11 (SDK 0.0.4, Winter 8b). WHY THE ROW EXISTS: the `gpt` family's `terra` SLOT names `canonicalModelId: \"gpt-5.6-terra\"` and `overlay/families.json`'s gpt row leads `vendorProviders` with `codex-oauth` (a configured subscription's marginal cost is zero, WS-13c §4 step 3-i), so on a Codex-only install that slot resolved to `codex-oauth/gpt-5.6-terra` — a key the catalog did not carry, which is a typed `unknown-model` refusal rather than a fallback. EVIDENCE THAT THE CODEX BACKEND SERVES IT: Norma's shipped Codex adapter declares `gpt-5.6-sol`, `gpt-5.6-terra` and `gpt-5.6-luna` as the ONLY user-selectable Codex models (packages/core/src/providers/codex-config.ts, `CODEX_MODELS`, each with `contextWindow: 272_000` and `supportsVision: true`; `CODEX_MODELS_VERIFIED = \"2026-07-31\"` records the date that static set was last checked against the live `/models` catalogue), and Norma's engine leg serves them today — the sibling `codex-oauth/gpt-5.6-sol` row already in this file cites exactly the same source. EVERY OTHER FIELD IS COPIED VERBATIM from that sibling: same backend, same adapter, same Responses dialect, same efforts. The ONE exception is `continuationDomain`, which names THIS key alone — §2.5's narrowness rule (two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads), so this row shares no domain with `openai/gpt-5.6-terra` despite the shared HTTP shape. Like every codex-oauth row it is deliberately UNPRICED — a subscription backend has no per-token list price (`pricingBasis: subscription` on the provider), so `maxBudgetUsd` is inert for it by design; the metered per-token rates belong to the separate `openai/gpt-5.6-terra` row. `status: candidate` — only the live gate promotes.",
+      "endpoints": [
+        "responses"
+      ],
+      "contextWindow": {
+        "value": 272000,
+        "source": "upstream-static",
+        "sourceRef": "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "inputModalities": {
+        "value": [
+          "text",
+          "image"
+        ],
+        "source": "upstream-static",
+        "sourceRef": "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "outputModalities": {
+        "value": [
+          "text"
+        ],
+        "source": "winter-default",
+        "sourceRef": "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        "confidence": "unknown",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "toolCalling": {
+        "value": "native",
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "nativeTools": {
+        "value": true,
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "reasoning": {
+        "supported": {
+          "value": true,
+          "source": "upstream-static",
+          "confidence": "inferred",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "efforts": [
+          "low",
+          "medium",
+          "high"
+        ],
+        "defaultEffort": "medium",
+        "continuation": "opaque-provider-state",
+        "readableState": {
+          "value": "summary",
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "summaryRequest": {
+          "value": {
+            "field": "reasoning.summary",
+            "values": [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface's summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: \"summary\"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "completionEvent": {
+          "value": "response.completed",
+          "source": "upstream-static",
+          "sourceRef": "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "continuationDomain": {
+          "value": [
+            "codex-oauth/gpt-5.6-terra"
+          ],
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma's shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: \"OpenAI-compatible\" is never the capability test.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        }
+      },
+      "unsupportedParameters": [],
+      "status": "candidate"
+    },
+    {
+      "key": "codex-oauth/gpt-5.6-luna",
+      "providerId": "codex-oauth",
+      "upstreamId": "gpt-5.6-luna",
+      "displayName": "GPT-5.6 Luna (Codex)",
+      "aliases": [],
+      "$comment": "Winter-owned (D11), authored 2026-09-11 (SDK 0.0.4, Winter 8b). WHY THE ROW EXISTS: the `gpt` family's `luna` SLOT names `canonicalModelId: \"gpt-5.6-luna\"` and `overlay/families.json`'s gpt row leads `vendorProviders` with `codex-oauth` (a configured subscription's marginal cost is zero, WS-13c §4 step 3-i), so on a Codex-only install that slot resolved to `codex-oauth/gpt-5.6-luna` — a key the catalog did not carry, which is a typed `unknown-model` refusal rather than a fallback. EVIDENCE THAT THE CODEX BACKEND SERVES IT: Norma's shipped Codex adapter declares `gpt-5.6-sol`, `gpt-5.6-terra` and `gpt-5.6-luna` as the ONLY user-selectable Codex models (packages/core/src/providers/codex-config.ts, `CODEX_MODELS`, each with `contextWindow: 272_000` and `supportsVision: true`; `CODEX_MODELS_VERIFIED = \"2026-07-31\"` records the date that static set was last checked against the live `/models` catalogue), and Norma's engine leg serves them today — the sibling `codex-oauth/gpt-5.6-sol` row already in this file cites exactly the same source. EVERY OTHER FIELD IS COPIED VERBATIM from that sibling: same backend, same adapter, same Responses dialect, same efforts. The ONE exception is `continuationDomain`, which names THIS key alone — §2.5's narrowness rule (two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads), so this row shares no domain with `openai/gpt-5.6-luna` despite the shared HTTP shape. Like every codex-oauth row it is deliberately UNPRICED — a subscription backend has no per-token list price (`pricingBasis: subscription` on the provider), so `maxBudgetUsd` is inert for it by design; the metered per-token rates belong to the separate `openai/gpt-5.6-luna` row. `status: candidate` — only the live gate promotes.",
+      "endpoints": [
+        "responses"
+      ],
+      "contextWindow": {
+        "value": 272000,
+        "source": "upstream-static",
+        "sourceRef": "Norma packages/core/src/providers/codex-config.ts — CODEX_MODELS, a dated static set with its own drift guard",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "inputModalities": {
+        "value": [
+          "text",
+          "image"
+        ],
+        "source": "upstream-static",
+        "sourceRef": "Norma codex-config.ts CODEX_MODELS supportsVision: true",
+        "confidence": "declared",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "outputModalities": {
+        "value": [
+          "text"
+        ],
+        "source": "winter-default",
+        "sourceRef": "WINTER DEFAULT: upstream declares no output modality for ANY model, so `text` is Winter's inference for a chat registry, NOT an upstream statement. Stamped `source: winter-default` — the `EvidenceSource` member added for exactly this — so a reader filtering evidence BY SOURCE does not get a Winter guess wearing an upstream label. See PROVENANCE.md.",
+        "confidence": "unknown",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "toolCalling": {
+        "value": "native",
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "nativeTools": {
+        "value": true,
+        "source": "upstream-static",
+        "confidence": "inferred",
+        "observedAt": "2026-09-11T00:00:00Z"
+      },
+      "reasoning": {
+        "supported": {
+          "value": true,
+          "source": "upstream-static",
+          "confidence": "inferred",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "efforts": [
+          "low",
+          "medium",
+          "high"
+        ],
+        "defaultEffort": "medium",
+        "continuation": "opaque-provider-state",
+        "readableState": {
+          "value": "summary",
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface returns a readable summary, never the raw chain",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "summaryRequest": {
+          "value": {
+            "field": "reasoning.summary",
+            "values": [
+              "auto",
+              "concise",
+              "detailed"
+            ]
+          },
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1 — the Responses surface's summary control and its current values `auto`/`concise`/`detailed`; the deprecated `generate_summary` alias is deliberately not listed. Same evidence as `openai/o4-mini` — the same field on the same wire shape — which is exactly why the DOMAIN still is not shared (§2.5). A `readableState: \"summary\"` claim with no way to REQUEST the summary is a capability nobody can use, so the two travel together.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "completionEvent": {
+          "value": "response.completed",
+          "source": "upstream-static",
+          "sourceRef": "Norma packages/core/src/providers/responses-sse.ts — encrypted_content is preserved VERBATIM off the completion event",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        },
+        "continuationDomain": {
+          "value": [
+            "codex-oauth/gpt-5.6-luna"
+          ],
+          "source": "official-doc",
+          "sourceRef": "continuity report §5.1/§5.3 for own-state acceptance — the Responses surface replays its own completed `reasoning.encrypted_content` items to the same model, which is what Norma's shipped Codex adapter does verbatim off `response.completed` — and §2.5 for the narrowness: two endpoints can both use `/v1/responses` while issuing UNRELATED encrypted payloads, so this backend shares NO domain with `openai/*` despite the shared HTTP shape. WS-13 §8.2: \"OpenAI-compatible\" is never the capability test.",
+          "confidence": "declared",
+          "observedAt": "2026-09-11T00:00:00Z"
+        }
+      },
+      "unsupportedParameters": [],
+      "status": "candidate"
+    },
     {
       "key": "deepseek-anthropic/deepseek-reasoner",
       "providerId": "deepseek-anthropic",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yanlinglabs/winter-provider-catalog",
-  "version": "0.0.3",
+  "version": "0.0.5",
   "license": "MIT",
   "type": "module",
   "engines": {