# Wetech Cluster Alias Routing Without Name Enumeration

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "wetech-cluster-alias-routing-2026-07-23",
  "problems": [
    {
      "problemId": "wetech-explicit-alias-reported-as-missing-context",
      "summary": "Replay classification can report missing cluster context after the customer explicitly supplies a Wetech cluster alias.",
      "status": "optimized_verified",
      "issueKeys": ["APID-29226"],
      "sourceRefs": ["https://tidb.atlassian.net/browse/APID-29226#problem:ai_gap:wetech-alias-routing"],
      "signalTextIncludesAny": ["缺少 cluster_or_tenant_context", "missing cluster context", "explicit wetech alias ignored"],
      "observedThrough": "2026-07-23",
      "effectiveAt": "2026-07-23T15:59:00+08:00",
      "verifiedAt": "2026-07-23T16:05:32+08:00",
      "attemptedAction": "Use the same semantic scenario classifier for production manual replay and recognize explicit Wetech cluster references without enumerating known alias names.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/APID-29226?focusedCommentId=23269769"
    }
  ]
}
-->

- Optimization ID: `wetech-cluster-alias-routing-2026-07-23`
- Owner: auto-oncall-services
- Source reference: `APID-29226`
- Bounded problem: replay classified the visible `btwallet` clarification as
  missing cluster context because its deterministic fallback enumerated only a
  few known Wetech alias shapes.
- Implementation status: merged in `tidbcloud/aisupport#473` and deployed to
  staging in image `636bbdf8399538bb60814532319f10c1f9b40430`.
- Effective status: `optimized_verified`.

## Verification evidence

- Pre-change replay `fee2eef3-3f94-4412-b089-f9e36d5a70ad` included the
  `btwallet` comment but persisted `missingKeys=["cluster_or_tenant_context"]`.
- The manual replay path now invokes the same injected scenario classifier as
  the normal worker and passes only replay-safe visible comments.
- The deterministic fallback recognizes an explicit Wetech alias
  semantically, including the short confirmation `是btwallet`, without a list
  of known cluster names.
- Full repository regression passed on 2026-07-23: 410 tests, 0 failures.
- Post-deployment write replay `1398d45f-8abf-453c-add1-f088e6b15eab`
  classified the case as `cluster_runtime_issue`, recorded both
  `account_alias` and `cluster_alias`, and left `missingKeys` empty.
- The replay wording correction in `tidbcloud/aisupport#474` made the historical
  replay include the customer's `是btwallet` clarification without adding any
  cluster-name enumeration.

## Unresolved gaps

- None for this bounded alias-routing problem. Root-cause diagnosis for the
  restart remains a separate human follow-up.

## Next validation action

Watch later Wetech tickets for a regression where a newly supplied explicit
cluster alias is again reported as missing context.