# Merge high-risk human handoffs into report classification

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "high-risk-report-classification-2026-07-21",
  "problems": [
    {
      "problemId": "high-risk-handoffs-rendered-as-unclassified",
      "summary": "Known high-risk human handoffs are rendered as unclassified and omitted from the weekly report.",
      "status": "optimized_verified",
      "issueKeys": ["APID-29203", "ST-2822", "TCID-12935"],
      "sourceRefs": [],
      "signalTextIncludesAny": ["s1_priority", "cluster_availability_risk", "data_protection_risk", "plaintext_aws_credentials_exposed", "customer_secret_in_ticket", "exposed_aws_access_key", "exposed_aws_secret_access_key", "exposed_aws_credentials", "high risk", "高风险", "暂未归类"],
      "observedThrough": "2026-07-21",
      "effectiveAt": "2026-07-21T07:31:00Z",
      "verifiedAt": "2026-07-21T07:35:00Z",
      "attemptedAction": "Classify known incident, priority, and exposed-credential human handoffs as high risk and list them in the weekly report.",
      "evidenceUrl": "https://github.com/tidbcloud/aisupport/pull/421"
    }
  ]
}
-->

- Optimization ID: `high-risk-report-classification-2026-07-21`
- Title: Merge high-risk human handoffs into report classification
- Owner: auto-oncall-services
- Source type: weekly report audit
- Source reference: `APID-29203`, `ST-2822`, `TCID-12935`; staging weekly report
  `2026-07-13 00:00 ~ 2026-07-20 00:00`

## Bounded problem

The report already has a high-risk human-required category, but the live risk
flags `s1_priority`, `cluster_availability_risk`,
`plaintext_aws_credentials_exposed`, and `customer_secret_in_ticket` do not
enter it. The live `APID-29203` rerun also emits the concrete flags
`exposed_aws_access_key` and `exposed_aws_secret_access_key`. Those human handoffs appear as unclassified, and the weekly report
does not render the high-risk count or affected tickets at all.

## Status

- Implementation: complete across `tidbcloud/aisupport#413`, `#419`, and `#421`.
- Effective/deployment: staging image `81841ce30920d7388805c555d168f4fce23c5c51`.

## Problem validation

| Problem signal | Ticket keys | Status | Evidence |
| --- | --- | --- | --- |
| High-risk human handoffs render as unclassified and are absent from weekly core metrics | `APID-29203`, `ST-2822`, `TCID-12935` | `optimized_verified` | Base readback classifies all three as high risk. Feishu message `om_x100b6ac65d29b0a8c07296619bf1282` shows the two in-window cases `ST-2822` and `TCID-12935` in weekly core metrics on 2026-07-21. |

## Unresolved gaps and next action

- No unresolved gap for this classification problem. Continue routine
  monitoring for newly emitted risk-flag semantics.