# apac-test OP and Public Cohort

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "apac-test-op-public-cohort-2026-08-12",
  "problems": [
    {
      "problemId": "apac-test-op-account-not-admitted",
      "summary": "The apac-test Account Alias was outside both the supported OP provider mapping and the customer-reply cohort, so it could not run Wetech-backed diagnostics or enter the Public Gate cohort.",
      "status": "optimized_unverified",
      "issueKeys": [],
      "sourceRefs": [],
      "signalTextIncludesAny": [
        "account alias apac-test",
        "op_unsupported",
        "customer_cohort_not_enabled"
      ],
      "observedThrough": "2026-08-12",
      "effectiveAt": "2026-08-12T16:01:38+08:00",
      "verifiedAt": null,
      "attemptedAction": "Map exact case-insensitive apac-test OP tickets to the isolated Wetech evidence provider and add apac-test to the guarded customer-reply Account Alias cohort while preserving all scenario, completion, validator, and Jira publication gates.",
      "evidenceUrl": "https://github.com/tidbcloud/aisupport/pull/824"
    }
  ]
}
-->

- Optimization ID: `apac-test-op-public-cohort-2026-08-12`
- Owner: auto-oncall-services OP routing and customer publication cohort
- Source reference: user-requested Account Alias allowlist change on 2026-08-12
- Implementation status: merged and deployed to staging
- Effective status: `optimized_unverified`

## Bounded problem

Exact OP tickets with `Account Alias = apac-test` had no automatic evidence
provider and were outside the customer-reply Account Alias cohort. This record
owns only that alias-to-Wetech provider admission and Public Gate cohort entry.
It does not bypass Auto Coverage scenario/resolution gates, evidence completion,
hard-risk checks, the independent validator, idempotency, or Jira write safety.

## Candidate change

- Map exact case-insensitive `apac-test` to the existing isolated Wetech OP
  provider route.
- Treat its explicit customer-supplied cluster alias as Wetech routing context.
- Add `apac-test` to the staging and disabled-prod customer-reply cohort
  templates; keep the prod customer-reply feature disabled.
- Keep unsupported OP accounts behind `op_unsupported`.

## Verification evidence

PR `https://github.com/tidbcloud/aisupport/pull/824` merged after its Auto
Oncall CI passed. Local validation also passed `npm run typecheck`, all 762
tests, and staging/prod `kubectl kustomize` renders. Staging registration PR
`https://github.com/tidbcloud/app-delivery/pull/77007` and image PR
`https://github.com/tidbcloud/app-delivery/pull/77008` merged.

Staging image `7c7717a88f8bc24fc94db9bbba58a38790ca2ace` reached one Ready Pod
with zero restarts. The Pod read back
`AUTO_ONCALL_CUSTOMER_REPLY_ACCOUNT_ALIASES=Wetech,apac-test`, customer
replies enabled, and active polling. An in-Pod deterministic smoke using exact
`Account Alias = APAC-TEST` returned `evidenceProvider=wetech`,
`resolutionMode=evidence_assisted`, `missingKeys=[]`, Auto Coverage `enabled`,
and Customer Reply Gate `allowed/final_answer`. No Jira write was requested.

Startup logs showed successful poll completion and idle workers. DB readback
showed no queued, running, or retryable jobs. This proves the deployed routing
and cohort configuration, but not the quality or actual publication result of
a real `apac-test` ticket.

## Unresolved gaps

- No real `apac-test` Jira case has exercised provider execution or the stored
  Customer Reply Gate after this change.
- No Jira customer-visible write or readback is claimed.
- The prod source template includes the cohort entry, but prod customer replies
  remain disabled and no prod rollout was performed.

## Next validation action

On the next eligible real `apac-test` ticket, verify the stored Auto Coverage
and Customer Reply Gate decisions, successful Wetech provider execution when
required, and the exact Jira delivery outcome before promoting this problem to
`optimized_verified`.