@tormentalabs/claude-code-wire-compat 0.4.0 → 0.6.0

package/src/model-queries.ts

@@ -0,0 +1,273 @@
+// SPDX-License-Identifier: GPL-3.0-or-later
+
+import type { ClaudeCodeProtocolProfile } from "./contracts.js";
+import { supportsStructuredOutputs as portedStructuredOutputs } from "./model-capabilities.js";
+import { modelFamilyOf, normalizeModelId } from "./model-identity.js";
+import { CLAUDE_CODE_2_1_195_PROFILE } from "./profiles/claude-code-2.1.195.js";
+
+/*
+ * Read-only model queries.
+ *
+ * DESIGN DECISION (Phase 1.1). Two surfaces, deliberately separate:
+ *
+ *   1. `modelCapability(model, capability, profile)` -- the GENERIC query. The
+ *      catalogue is the source of truth: it normalizes the id, looks the entry
+ *      up in `profile.supportedModels` and asks whether the verbatim upstream
+ *      capability string is present. It invents nothing, maps nothing, and
+ *      therefore answers for capability strings this package does not model as
+ *      a `ClaudeCodeCapabilities` field (`fast_mode`, `lean_prompt`,
+ *      `fable_5_mitigations`, `mid_conv_system`, ...) as readily as for the
+ *      six that it does.
+ *
+ *   2. The NAMED family/version predicates below -- `isOpus47Model` and
+ *      friends. A family is not a catalogue capability; it is an identity
+ *      question. They are therefore written over `normalizeModelId` and
+ *      `modelFamilyOf`, NOT over a new family regex and NOT over the
+ *      catalogue. Consequence, and it is intended: an id normalizing to
+ *      `claude-opus-4-7` answers `isOpus47Model` true whether or not the
+ *      active profile catalogues it.
+ *
+ * Do not fold (2) into (1). Asking `modelCapability(model, "adaptive_thinking")`
+ * and asking `isAdaptiveThinkingModel(model)` are different questions with
+ * different answers for ids the active profile does not catalogue, and both
+ * questions have callers.
+ *
+ * INVALID INPUT. Every predicate here returns `false` for a non-string or an
+ * empty id rather than throwing. This departs from `resolveModel`
+ * (`ClaudeCodeWireError("INVALID_INPUT")`) on purpose: these are predicates,
+ * their upstream counterparts are total functions returning `false` on a
+ * falsy model, and a predicate that throws cannot be used in the boolean
+ * position its callers put it in.
+ *
+ * RUNTIME NEUTRALITY. No builtins, no clock, no randomness, no I/O.
+ */
+
+/** Lowercased + dotted-to-dashed id, or `null` for input no predicate can answer for. */
+function normalizedOrNull(model: string): string | null {
+  if (typeof model !== "string" || model.length === 0) {
+    return null;
+  }
+  return normalizeModelId(model);
+}
+
+/**
+ * Explicit 1M markers a caller can spell into the model id.
+ *
+ * `\[1m\]` is deliberately absent: it marks a request-time context selection,
+ * not an always-1M id, and the upstream marker check does not accept it.
+ */
+const ONE_MILLION_MARKER_RE = /(^|[-_ ])1m($|[-_ ])|context[-_]?1m/iu;
+
+/** As `ONE_MILLION_MARKER_RE`, plus the bracketed request-time marker. */
+const ONE_MILLION_ELIGIBLE_MARKER_RE =
+  /(^|[-_ ])1m($|[-_ ])|context[-_]?1m|\[1m\]/iu;
+
+/**
+ * Vendor tokens the upstream web-search gate accepts. Transcribed as a token
+ * list rather than a regex so it stays a data question, not a pattern-matching
+ * one.
+ */
+const WEB_SEARCH_VENDOR_TOKENS: readonly string[] = Object.freeze([
+  "claude",
+  "sonnet",
+  "opus",
+  "haiku",
+  "gpt",
+  "gemini",
+]);
+
+/**
+ * Whether the active profile's catalogue records `capability` for `model`.
+ *
+ * `capability` is a verbatim upstream capability string. Ids the profile does
+ * not catalogue answer `false` for every capability: the catalogue is the only
+ * evidence this query consults, and absence of evidence is reported as
+ * absence. Callers wanting the derived nine-boolean view -- which falls back
+ * to the ported predicates for uncatalogued ids -- want `resolveModel`.
+ */
+export function modelCapability(
+  model: string,
+  capability: string,
+  profile: ClaudeCodeProtocolProfile = CLAUDE_CODE_2_1_195_PROFILE,
+): boolean {
+  const id = normalizedOrNull(model);
+  if (
+    id === null ||
+    typeof capability !== "string" ||
+    capability.length === 0
+  ) {
+    return false;
+  }
+  const entry = profile.supportedModels[id];
+  if (entry === undefined) {
+    return false;
+  }
+  return entry.capabilities.includes(capability);
+}
+
+/** Whether `model` normalizes to `claude-opus-4-6`. */
+export function isOpus46Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-opus-4-6";
+}
+
+/** Whether `model` normalizes to `claude-opus-4-7`. */
+export function isOpus47Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-opus-4-7";
+}
+
+/** Whether `model` normalizes to `claude-opus-4-8`. */
+export function isOpus48Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-opus-4-8";
+}
+
+/** Whether `model` normalizes to `claude-opus-5`. */
+export function isOpus5Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-opus-5";
+}
+
+/** Whether `model` normalizes to `claude-opus-5-5`. */
+export function isOpus55Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-opus-5-5";
+}
+
+/** Whether `model` normalizes to `claude-sonnet-4-6`. */
+export function isSonnet46Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-sonnet-4-6";
+}
+
+/** Whether `model` normalizes to `claude-sonnet-5`. */
+export function isSonnet5Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-sonnet-5";
+}
+
+/** Whether `model` normalizes to `claude-fable-5`. */
+export function isFable5Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-fable-5";
+}
+
+/** Whether `model` normalizes to `claude-fable-5-1`. */
+export function isFable51Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-fable-5-1";
+}
+
+/** Whether `model` normalizes to `claude-mythos-5`. */
+export function isMythos5Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-mythos-5";
+}
+
+/** Whether `model` normalizes to `claude-mythos-5-1`. */
+export function isMythos51Model(model: string): boolean {
+  return normalizedOrNull(model) === "claude-mythos-5-1";
+}
+
+/**
+ * Whether `model` belongs to the haiku family.
+ *
+ * Reuses `modelFamilyOf`, the package's one family classifier, so a new haiku
+ * id is classified in exactly one place.
+ */
+export function isHaikuModel(model: string): boolean {
+  const id = normalizedOrNull(model);
+  return id !== null && modelFamilyOf(id) === "haiku";
+}
+
+/**
+ * Whether `model` is a Claude 3 generation id.
+ *
+ * The `claude-3-` substring test is the same one the ported capability
+ * predicates open with (`model-capabilities.ts`), applied to the normalized
+ * id, so a Claude 3 id spelled with a dotted version (`claude-3.5-sonnet`)
+ * classifies with its hyphenated spelling.
+ */
+export function isClaude3Model(model: string): boolean {
+  return normalizedOrNull(model)?.includes("claude-3-") ?? false;
+}
+
+/**
+ * Whether `model` may receive the 1M-context beta.
+ *
+ * Three sources, in order: an explicit 1M marker in the id, the active
+ * profile's `context.supports1mBeta`, and -- for ids the profile does not
+ * catalogue -- the ported family set (`claude-sonnet-4*`, Opus 4.6/4.7/4.8).
+ */
+export function isEligibleFor1MContext(
+  model: string,
+  profile: ClaudeCodeProtocolProfile = CLAUDE_CODE_2_1_195_PROFILE,
+): boolean {
+  const id = normalizedOrNull(model);
+  if (id === null) {
+    return false;
+  }
+  if (ONE_MILLION_ELIGIBLE_MARKER_RE.test(model)) {
+    return true;
+  }
+  const entry = profile.supportedModels[id];
+  if (entry !== undefined) {
+    return entry.context?.supports1mBeta === true;
+  }
+  return (
+    id.startsWith("claude-sonnet-4") ||
+    id === "claude-opus-4-6" ||
+    id === "claude-opus-4-7" ||
+    id === "claude-opus-4-8"
+  );
+}
+
+/**
+ * Whether `model` names 1M context explicitly and therefore always uses it.
+ *
+ * Marker-only by design. The catalogue's `context.native1m` is a DIFFERENT
+ * question -- the model's native window -- and consulting it here would make
+ * every natively-1M id answer true, which is not what a static "always send
+ * 1M" gate means. Use `modelContextWindow`-shaped catalogue reads for that.
+ */
+export function hasOneMillionContext(model: string): boolean {
+  return normalizedOrNull(model) !== null && ONE_MILLION_MARKER_RE.test(model);
+}
+
+/**
+ * Whether `model` supports the structured-outputs beta.
+ *
+ * Delegates to the predicate ported from the genuine client (`j4e`), which is
+ * narrower and better evidenced than a family-shaped heuristic.
+ */
+export function supportsStructuredOutputs(model: string): boolean {
+  const id = normalizedOrNull(model);
+  return id !== null && portedStructuredOutputs(id);
+}
+
+/** Whether `model` supports the web-search tool. */
+export function supportsWebSearch(model: string): boolean {
+  const id = normalizedOrNull(model);
+  return (
+    id !== null && WEB_SEARCH_VENDOR_TOKENS.some((token) => id.includes(token))
+  );
+}
+
+/**
+ * Whether `model` uses adaptive thinking (`{type: "adaptive"}`) instead of a
+ * manual `budget_tokens`.
+ *
+ * The union of the named per-model predicates, not a catalogue read: this
+ * gates the shape of the emitted `thinking` block, and an uncatalogued id must
+ * not inherit adaptive thinking from the permissive capability fallback. The
+ * union covers every id any pinned profile's catalogue marks
+ * `adaptive_thinking` (the 2.1.280 catalogue is the widest). Ask
+ * `modelCapability(model, "adaptive_thinking", profile)` for a specific
+ * profile's answer.
+ */
+export function isAdaptiveThinkingModel(model: string): boolean {
+  return (
+    isOpus46Model(model) ||
+    isOpus47Model(model) ||
+    isOpus48Model(model) ||
+    isOpus5Model(model) ||
+    isOpus55Model(model) ||
+    isSonnet46Model(model) ||
+    isSonnet5Model(model) ||
+    isFable5Model(model) ||
+    isFable51Model(model) ||
+    isMythos5Model(model) ||
+    isMythos51Model(model)
+  );
+}

package/src/models.ts

@@ -38,7 +38,7 @@ export function resolveModel(
     id,
     wireId,
     // The catalogue supplies the family here, and -- since T1.1.2 -- also
-    // supplies the six catalogue-backed capabilities. Both now honour THIS
+    // supplies the catalogue-backed capabilities. Both now honour THIS
     // profile: `deriveCapabilities` takes the active profile, so a request
     // built against a non-pinned profile derives from that profile's
     // catalogue rather than from 2.1.195's. Ids with no catalogue entry fall

package/src/profiles/beta-registry-2.1.280.ts

@@ -0,0 +1,309 @@
+// SPDX-License-Identifier: GPL-3.0-or-later
+
+interface BetaRegistryEntry {
+  readonly featureKey: string;
+  readonly header: string;
+}
+
+/*
+ * `deepFreeze` is duplicated from `src/beta-registry.ts` rather than imported,
+ * for the same reason the 2.1.233 registry duplicates it: a shared helper
+ * module would make every registry import-coupled for four lines of code, and
+ * keeping each registry a leaf keeps a version bump from rippling.
+ */
+function deepFreeze<T>(value: T): T {
+  if (value !== null && typeof value === "object") {
+    for (const key of Reflect.ownKeys(value)) {
+      deepFreeze(Reflect.get(value, key));
+    }
+    Object.freeze(value);
+  }
+  return value;
+}
+
+/**
+ * Genuine-client beta registry as of 2.1.280, upstream factory chain at byte
+ * offset 6277485 and ordered array `oy` immediately after it.
+ *
+ * KEY ORDER IS LOAD-BEARING, and for 2.1.280 it is load-bearing in a way it was
+ * not before: upstream's array is NOT append-only. `thinking_resumption` is
+ * inserted at position 17, and `per_turn_timing`, `mid_conv_tool_change` and
+ * `inline_tools` are inserted at 29-31, ahead of four entries that already
+ * existed. A diff that assumes new identifiers only ever land at the end will
+ * mis-align fifteen entries: 2.1.233 positions 17-27 shift by one and 28-31
+ * shift by four. See
+ * `docs/protocol/versions/claude-code-2.1.280-analysis.md` section 4.2.
+ *
+ * The upstream array carries 42 slots with two explicit `null`s (indices 34 and
+ * 37, `kAt` at byte 6279405 and `hZt` at byte 6279537) which `.filter(e => e
+ * !== null)` removes, leaving the forty entries below. Both slots are null IN
+ * THIS BUILD, which is all the bytes establish: upstream treats registry
+ * members as nullable per build -- `Dg` carries `...BR ? [BR] : []` and `hRr`
+ * guards on `kAt === null` -- so a compile-time feature gate fits the evidence
+ * as well as a removal does, and this file claims neither. `kAt` still has two
+ * consumers at byte 14167580: `hRr`, short-circuited by that null check, and
+ * `yRr`, which reads `kAt.name` with no null guard and so is either unreachable
+ * or a throw path. Neither says WHICH beta the slot held; see the note above
+ * `AUTO_MODE_CLASSIFIER`. Neither null slot is transcribed here; a null is not
+ * an entry.
+ *
+ * Two further registry members are deliberately absent:
+ * `mid_conv_cache_promotion_latch` and `mid_conv_cache_promotion_ok_latch`
+ * (`x-cc-internal-mid-conv-cache-promotion` and its `-ok` sibling). Upstream
+ * declares them through the same factory but excludes them from the ordered
+ * array, and their "header" values are internal `x-cc-*` names, not beta
+ * identifiers. Transcribing them would corrupt the registry.
+ *
+ * Every one of the nine entries new since 2.1.233 was confirmed against its own
+ * `N(alias, header)` declaration in the carved dump rather than against the
+ * analysis document alone, so no new header rests on a single reading:
+ * `rrt` 6278299, `w$` 6278910, `j_` 6278959, `W_` 6279023, and `qk`, `Aoe`,
+ * `cD`, `V1`, `lD` in the window at 6279405.
+ *
+ * `oauth_auth` is the one entry whose header is NOT a string literal upstream:
+ * the declaration reads `swe=N("oauth_auth",Ru)`. `Ru` is an imported binding,
+ * re-exported as `OAUTH_BETA_HEADER` at byte 25341943, and the only beta-shaped
+ * `oauth-*` literal in the bundle is `"oauth-2025-04-20"` at byte 4418398.
+ * Resolved by that binding, not by name similarity.
+ */
+export const BETA_REGISTRY_2_1_280 = deepFreeze({
+  CLAUDE_CODE: { featureKey: "claude_code", header: "claude-code-20250219" },
+  OAUTH_AUTH: { featureKey: "oauth_auth", header: "oauth-2025-04-20" },
+  INTERLEAVED_THINKING: {
+    featureKey: "interleaved_thinking",
+    header: "interleaved-thinking-2025-05-14",
+  },
+  LONG_CONTEXT: { featureKey: "long_context", header: "context-1m-2025-08-07" },
+  CONTEXT_MANAGEMENT: {
+    featureKey: "context_management",
+    header: "context-management-2025-06-27",
+  },
+  STRUCTURED_OUTPUTS: {
+    featureKey: "structured_outputs",
+    header: "structured-outputs-2025-12-15",
+  },
+  WEB_SEARCH: { featureKey: "web_search", header: "web-search-2025-03-05" },
+  ADVANCED_TOOL_USE: {
+    featureKey: "tool_search",
+    header: "advanced-tool-use-2025-11-20",
+  },
+  TOOL_SEARCH: {
+    featureKey: "tool_search",
+    header: "tool-search-tool-2025-10-19",
+  },
+  EFFORT: { featureKey: "effort", header: "effort-2025-11-24" },
+  TASK_BUDGETS: {
+    featureKey: "task_budgets",
+    header: "task-budgets-2026-03-13",
+  },
+  PROMPT_CACHING_SCOPE: {
+    featureKey: "prompt_caching_scope",
+    header: "prompt-caching-scope-2026-01-05",
+  },
+  PROMPT_CACHING_EVICT: {
+    featureKey: "prompt_caching_evict",
+    header: "prompt-caching-evict-2026-05-12",
+  },
+  EXTENDED_CACHE_TTL: {
+    featureKey: "extended_cache_ttl",
+    header: "extended-cache-ttl-2025-04-11",
+  },
+  SPEED: { featureKey: "speed", header: "fast-mode-2026-02-01" },
+  REDACT_THINKING: {
+    featureKey: "redact_thinking",
+    header: "redact-thinking-2026-02-12",
+  },
+  // New at 2.1.280, and inserted HERE rather than appended. Every entry below
+  // this point sat one slot lower in 2.1.233.
+  THINKING_RESUMPTION: {
+    featureKey: "thinking_resumption",
+    header: "thinking-resumption-2026-07-17",
+  },
+  THINKING_TOKEN_COUNT: {
+    featureKey: "thinking_token_count",
+    header: "thinking-token-count-2026-05-13",
+  },
+  AFK_MODE: { featureKey: "afk_mode", header: "afk-mode-2026-01-31" },
+  ADVISOR_TOOL: {
+    featureKey: "advisor_tool",
+    header: "advisor-tool-2026-03-01",
+  },
+  CACHE_DIAGNOSIS: {
+    featureKey: "cache_diagnosis",
+    header: "cache-diagnosis-2026-04-07",
+  },
+  CONTEXT_HINT: {
+    featureKey: "context_hint",
+    header: "context-hint-2026-04-09",
+  },
+  MCP_SERVERS: { featureKey: "mcp_servers", header: "mcp-servers-2025-12-04" },
+  FILES_API: { featureKey: "files_api", header: "files-api-2025-04-14" },
+  ENVIRONMENTS: {
+    featureKey: "environments",
+    header: "environments-2025-11-01",
+  },
+  CCR_BYOC: { featureKey: "ccr_byoc", header: "ccr-byoc-2025-07-29" },
+  MID_CONVERSATION_SYSTEM: {
+    featureKey: "mid_conversation_system",
+    header: "mid-conversation-system-2026-04-07",
+  },
+  PER_MESSAGE_EFFORT: {
+    featureKey: "per_message_effort",
+    header: "per-turn-control-2026-07-01",
+  },
+  // New at 2.1.280. Also inserted rather than appended: the four entries below
+  // `INLINE_TOOLS` all predate this release.
+  PER_TURN_TIMING: {
+    featureKey: "per_turn_timing",
+    header: "timing-2026-09-09",
+  },
+  MID_CONV_TOOL_CHANGE: {
+    featureKey: "mid_conv_tool_change",
+    header: "mid-conversation-tool-changes-2026-07-01",
+  },
+  INLINE_TOOLS: {
+    featureKey: "inline_tools",
+    header: "inline-tools-2026-09-15",
+  },
+  SERVER_SIDE_FALLBACK: {
+    featureKey: "server_side_fallback",
+    header: "server-side-fallback-2026-06-01",
+  },
+  SERVER_SIDE_FALLBACK_CATEGORY: {
+    featureKey: "server_side_fallback_category",
+    header: "server-side-fallback-2026-07-01",
+  },
+  FALLBACK_CREDIT: {
+    featureKey: "fallback_credit",
+    header: "fallback-credit-2026-06-01",
+  },
+  /*
+   * NARRATION_SUMMARIES IS DELIBERATELY ABSENT, exactly as in the 2.1.233
+   * registry, and re-adding it would reintroduce a header the genuine client no
+   * longer sends. Do not "fix" it.
+   *
+   * This position -- between `FALLBACK_CREDIT` and `AUTO_MODE_CLASSIFIER` -- is
+   * where the 2.1.233 registry records the removal, and it is also where array
+   * index 34 (`kAt`, null) falls. That correspondence is suggestive and NOT
+   * EVIDENCED: the `summarize-connector-text-2026-03-13` header string appears
+   * nowhere in the 2.1.280 bundle, so nothing ties it to `kAt` rather than to
+   * `hZt`, and `kAt`'s surviving consumer at byte 14167580 reports rejections
+   * under an "Auto mode classifier" label, which points the other way. The
+   * analysis document asserts only that two slots are null and this file
+   * asserts no more. See section 4.2 of
+   * `docs/protocol/versions/claude-code-2.1.280-analysis.md`.
+   */
+  AUTO_MODE_CLASSIFIER: {
+    featureKey: "auto_mode_classifier",
+    header: "auto-mode-classifier-2026-07-16",
+  },
+  // New at 2.1.280.
+  DANGEROUS_TOOL_USE: {
+    featureKey: "dangerous_tool_use",
+    header: "dangerous-tool-use-2026-09-03",
+  },
+  /*
+   * The SECOND null slot (`hZt`, upstream index 37) belongs here. As with the
+   * first, what it once held -- if anything -- is unknown: no header string in
+   * any analysed release is tied to it by evidence. It is recorded rather than
+   * silently closed up, because a future build may reuse the slot.
+   */
+  // New at 2.1.280.
+  THINKING_DISPLAY_UPDATES: {
+    featureKey: "thinking_display_updates",
+    header: "thinking-display-updates-2026-08-18",
+  },
+  MESSAGE_THREADS: {
+    featureKey: "message_threads",
+    header: "message-threads-2026-08-12",
+  },
+  MID_CONVERSATION_SYSTEM_CLEAR_AT: {
+    featureKey: "mid_conversation_system_clear_at",
+    header: "mid-conversation-system-clear-at-2026-08-21",
+  },
+  /*
+   * LAST in the array, though upstream DECLARES it alongside
+   * `thinking_display_updates` and `message_threads`. Declaration order and
+   * array order differ here and the array is what this transcription follows.
+   */
+  THINKING_BINDING_CONTROLS: {
+    featureKey: "thinking_binding_controls",
+    header: "thinking-binding-controls-2026-08-01",
+  },
+} satisfies Record<string, BetaRegistryEntry>);
+
+/*
+ * Third-party filtering as of 2.1.280, upstream `Dg` at byte 7029997, consumed
+ * by `DDn(e) { if (iwe()) return e; return e.filter(n => Dg.has(n)) }` in the
+ * same run -- that is, the set is applied only when the request is NOT
+ * first-party, which is how it was identified: by call site, not by resemblance
+ * to the 2.1.233 set.
+ *
+ * Upstream writes one member as a conditional spread, `...BR ? [BR] : []`. That
+ * is why the extractor reported this set `unresolved` ("a member is neither a
+ * string literal nor a single property read"). `BR` is unconditionally defined
+ * at byte 6278332 in this build, so the spread always contributes and the set
+ * has fourteen members.
+ *
+ * Delta against the 2.1.233 set: `dangerous_tool_use`, `thinking_token_count`
+ * and `thinking_binding_controls` were ADDED; nothing was removed. Order below
+ * follows upstream's literal.
+ */
+export const THIRD_PARTY_ALLOWED_BETAS_2_1_280: ReadonlySet<string> =
+  Object.freeze(
+    new Set([
+      BETA_REGISTRY_2_1_280.CLAUDE_CODE.header,
+      BETA_REGISTRY_2_1_280.INTERLEAVED_THINKING.header,
+      BETA_REGISTRY_2_1_280.LONG_CONTEXT.header,
+      BETA_REGISTRY_2_1_280.CONTEXT_MANAGEMENT.header,
+      BETA_REGISTRY_2_1_280.STRUCTURED_OUTPUTS.header,
+      BETA_REGISTRY_2_1_280.WEB_SEARCH.header,
+      BETA_REGISTRY_2_1_280.EFFORT.header,
+      BETA_REGISTRY_2_1_280.TOOL_SEARCH.header,
+      BETA_REGISTRY_2_1_280.AFK_MODE.header,
+      BETA_REGISTRY_2_1_280.DANGEROUS_TOOL_USE.header,
+      BETA_REGISTRY_2_1_280.FALLBACK_CREDIT.header,
+      BETA_REGISTRY_2_1_280.MID_CONVERSATION_SYSTEM.header,
+      BETA_REGISTRY_2_1_280.THINKING_TOKEN_COUNT.header,
+      BETA_REGISTRY_2_1_280.THINKING_BINDING_CONTROLS.header,
+    ]),
+  );
+
+/*
+ * Provider filtering as of 2.1.280, upstream `qbr` at byte 6280270.
+ *
+ * Identified by behaviour rather than by shape: `Y5` at byte 7029210 reads
+ * `if (sc(e) === "bedrock") return n.filter(r => !qbr.has(r))`, and the
+ * complementary `lco` at the same site keeps exactly this set as bedrock
+ * extra-body parameters. Byte-identical to the 2.1.233 set.
+ *
+ * A DIFFERENT `qbr` exists at byte 13922760 in another module -- a set of grep
+ * flags. Minified names are module-scoped; this entry is the one the beta
+ * pipeline consumes.
+ *
+ * Static reference data with no call site in `src/`, exactly like its 2.1.233
+ * counterpart. See `test/governance/provider-scope.test.ts`.
+ */
+export const BEDROCK_UNSUPPORTED_BETAS_2_1_280: ReadonlySet<string> =
+  Object.freeze(
+    new Set([
+      BETA_REGISTRY_2_1_280.INTERLEAVED_THINKING.header,
+      BETA_REGISTRY_2_1_280.LONG_CONTEXT.header,
+      BETA_REGISTRY_2_1_280.TOOL_SEARCH.header,
+    ]),
+  );
+
+/*
+ * Count-tokens selection as of 2.1.280, upstream `iNn` at byte 6280282,
+ * consumed as `betas: y.filter(he => iNn.has(he))` inside
+ * `beta.messages.countTokens` at bytes 12304007, 12304164 and 12305087.
+ * Byte-identical to the 2.1.233 set.
+ */
+export const COUNT_TOKENS_BETAS_2_1_280: ReadonlySet<string> = Object.freeze(
+  new Set([
+    BETA_REGISTRY_2_1_280.CLAUDE_CODE.header,
+    BETA_REGISTRY_2_1_280.INTERLEAVED_THINKING.header,
+    BETA_REGISTRY_2_1_280.CONTEXT_MANAGEMENT.header,
+    BETA_REGISTRY_2_1_280.OAUTH_AUTH.header,
+  ]),
+);