Sync swagger: flatten consumption trace filter to repeated span filters

[prateek]

Syncs the configv1 swagger spec and regenerates clients/models/CLI (make update-swagger, wholesale regen committed as CI requires).

What this brings

• Flattened consumption trace filter: the partition filter condition on v1/config/ConsumptionConfig now carries a repeated trace_span_filters field directly — a list of the new top-level ConsumptionSpanFilter message (8 fields each: service, operation, parent_service, parent_operation, duration, error, tags, is_root_span). The old singular trace_filter field and its ConsumptionTraceFilter wrapper are gone. Matching happens at the span level: a span matches the condition only if it satisfies every span filter in the list (conjunctive); express alternatives with an IN string filter or with separate conditions. The field is preview, gated by the enable-consumption-trace-api feature flag.
• Rider — trace-metrics group-by keys: PARENT_SERVICE, PARENT_OPERATION, ROOT_SERVICE, ROOT_OPERATION group-by key types on v1/config/TraceMetricsRules.
• Rider — BREAKING sku_group removal: the deprecated sku_group field is removed from v1/config/ConsumptionBudget thresholds in favor of resource_group (which shipped in v1.28.0). Flagged as breaking in the CHANGELOG for the release team's versioning call.

Scope

The configv1 restructure only: delete Configv1ConsumptionTraceFilter and its nested span-filter model, add top-level Configv1ConsumptionSpanFilter, and rename PartitionFilterCondition.TraceFilter to TraceSpanFilters []*Configv1ConsumptionSpanFilter, plus the CHANGELOG reword. The wholesale make update-swagger also regenerated unrelated configunstable master drift (a new command-center-groups entity, SyntheticTest additions); that was reverted to keep this PR scoped to the trace filter — configunstable, statev1, and stateunstable are unchanged. Phase 2's pre-merge wholesale re-sync from master will pick that drift up in its own right.

Source

Specs synced from monorepo PR #87961 (the consumption trace restructure) at ca42bd7b. The worktree swagger source matches that branch tip — PR 3 commits touch no swagger, re-verified before this resync.

🤖 Generated with Claude Code

[prateek]

Review loop — iteration 1 (9 lenses; this PR's findings and fixes).

Fixed (7f02c05, CHANGELOG only):

• The trace_filter "Changed" entry now carries the never-operative parenthetical (the old shape was always gated by enable-consumption-trace-api, enabled for no tenant, so no existing manifest is affected) — preempts both the release-versioning question and the customer shape-diff question.
• Added the client-skew sentence: manifests containing the new trace_filter shape require this release or newer; older chronoctl versions reject them at decode and omit the filter when reading entities. (Distsys lens verified both skew directions fail loud — no silent-loss path.)

CI green (single "build" check is the repo's complete expected set).

🤖 Generated with Claude Code

[prateek]

Review loop — iteration 2. Fixed (8dc8ec0): two precision rewordings from the product lens — old clients "render the filter as an empty trace_filter object when reading entities" (not "omit": lenient unmarshal keeps the old-shaped key), and the never-operative claim is now scoped to customer tenants over the old shape's lifetime (the flag will be enabled on rc-uat test tenants at gate G1.5, so the present-tense global claim had an expiry date).

Iteration 3 incoming: PR #87961's final head changed the span_filters description from any-of to all-of semantics — a spec re-sync will pick up the new wording.

🤖 Generated with Claude Code

[prateek]

Review loop — iteration 3 (OR→AND contract-flip wave). Fixed (efd2d18): spec re-synced from PR #87961's squashed head — diff was description-only (the new all-of span_filters wording reaching spec.json, the regenerated model comment, and the scaffold YAML comment), with zero master-side riders. CHANGELOG entry reworded to the AND contract ("satisfies every span filter in the list; match alternatives with an IN string filter or with separate conditions").

🤖 Generated with Claude Code

[prateek]

Review loop — iteration 4. One finding here, fixed body-only: the PR description still carried the pre-flip OR wording ("satisfies all criteria of one span filter") — now matches the CHANGELOG's conjunctive sentence, and the swagger-source line reflects that PR #87961's current head 91a4918 is byte-identical to the synced spec. No code changes; head stays efd2d18.

🤖 Generated with Claude Code

[prateek]

Review loop — converged at iteration 6. All nine lenses clean (the single cosmetic finding — a duplicated sentence in the chronoctl PR body from an earlier edit — was fixed and verified in-round). Final state: monorepo #87970 @ 94c02c3b1ab with all 50 checks green and MERGEABLE on base #87961 @ fe94ba98da7; chronoctl #113 @ efd2d18, provider #220 @ ace2c08, scenarios #1184 @ 4fc0efd all green (scenarios live shard expected-red per its documented signatures). Loop totals across 6 iterations: 2 transient blockers, ~20 risks, ~25 nits found and fixed; 5 PR-1 base moves absorbed (2 with contract changes: OR→AND semantics, internal twin retype). Drafts now await PR #87961 (gate G1): wholesale external re-sync from master, then merges per the documented ordering.

🤖 Generated with Claude Code