# Provider Field Contract Discovery

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "provider-field-contract-discovery-2026-08-12",
  "problems": [
    {
      "problemId": "unsupported-optional-handoff-field-fails-scenario",
      "summary": "Evidence inferred get_token_time without an exhaustive visible field contract, and one unsupported optional handoff field rejected the whole query-latency scenario.",
      "status": "optimized_verified",
      "issueKeys": ["APID-29296"],
      "sourceRefs": ["https://tidb.atlassian.net/browse/APID-29296#problem:unsupported-handoff-field"],
      "signalTextIncludesAny": ["get_token_time", "op_batch_parameter_invalid", "unsupported optional handoff field"],
      "observedThrough": "2026-08-12",
      "effectiveAt": "2026-08-12T11:13:00+08:00",
      "verifiedAt": "2026-08-12T11:40:00+08:00",
      "attemptedAction": "Give Wetech Evidence one small on-demand exhaustive handoff-field reference, use it as the Provider Executor contract, and omit plus report unsupported optional names while continuing the remaining valid plan.",
      "evidenceUrl": "https://github.com/tidbcloud/aisupport/tree/main/auto-oncall-services/docs/opts/2026-08-12-provider-field-contract-discovery.md"
    }
  ]
}
-->

- Owner: Wetech Evidence Agent and Provider Executor
- Source: `APID-29296` replay `c530fc32-0448-474a-b21b-79f1b019c9ac`
- Status: optimized_verified

The runtime does not own or duplicate the provider field vocabulary. Evidence
reads the small exhaustive provider reference only when planning Slow Query
handoff fields. Unsupported optional names become an explicit acquisition gap;
valid fields and queries continue.

Staging replay `d8c9f1ba-e9ae-42b5-b338-e190ccbd27d9` on image
`e4c58c9db9bd2c52a2bfc4242d13005837a7815e` completed without
`op_batch_parameter_invalid`, `get_token_time`, or unsupported handoff fields.
Query-latency materialized valid Slow Query handoffs through three rounds.

The existing Jira internal comment `23399342` was updated in place after human
review. Readback confirmed `public=false` and the expected body; no duplicate
comment or issue transition was created.

Next action: monitor later Wetech replays for unsupported optional field gaps.