# Internal Only Section Label

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "internal-only-section-label-2026-08-13",
  "problems": [
    {
      "problemId": "internal-message-label-implies-engineer-handoff",
      "summary": "The Jira section label used the support term handoff even when the message was only private supplemental context and required no ownership transfer.",
      "status": "optimized_verified",
      "applicability": "Paired Jira internal comments and generated internal-comment artifacts for replay, live analysis, and continuation.",
      "issueKeys": ["ST-2891"],
      "sourceRefs": [
        "https://tidb.atlassian.net/browse/ST-2891#problem:internal-message-label-implies-engineer-handoff"
      ],
      "signalTextIncludesAny": [
        "internal handoff label implies ownership transfer",
        "internal only content has no engineer handoff"
      ],
      "observedThrough": "2026-08-13",
      "effectiveAt": "2026-08-13T06:28:00Z",
      "verifiedAt": "2026-08-13T06:32:11Z",
      "attemptedAction": "Keep the internalHandoffMarkdown wire field unchanged, but rename the visible Jira section from Internal Handoff to Internal Only and document that the label does not imply ownership transfer.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/ST-2891"
    }
  ]
}
-->

- Optimization ID: `internal-only-section-label-2026-08-13`
- Owner: paired Jira response presentation
- Source reference: `ST-2891`
- Implementation status: merged and deployed to staging
- Effective status: `optimized_verified`

## Bounded problem

`handoff` has a specific daily Support meaning: another engineer must take over.
The paired internal message exists for every result and often contains only
private supplemental context, so the visible `【内部交接】` label incorrectly
implied an ownership transfer for ordinary `internal_only` answers such as
ST-2891.

## Implemented change

- Keep the canonical `internalHandoffMarkdown` field unchanged for wire and
  persisted-payload compatibility.
- Render the visible Jira/internal-comment section as `【Internal Only】`.
- Preserve explicit owner or escalation instructions inside the message only
  when a real handoff is part of the result.

## Verification status

Source PR `tidbcloud/aisupport#869` passed CI and merged as
`ac292ff7503384cbc5f15887121637450258a0ae`. Deployment workflow
`31673552493` built that image, and app-delivery PR
`tidbcloud/app-delivery#77189` updated the staging tag. The live Deployment
reported the exact image with one Ready Pod and zero restarts; `/healthz` and
`/readyz` both returned HTTP 200.

ST-2891 `mode=read` replay run `9d2a78e9-c483-4873-bf96-eac3b2389c99`
remained `decision=internal_only`. The response retained
`internalHandoffMarkdown`, emitted no `internalOnlyMarkdown`, and reported Jira,
database, evaluation, and Feishu writes as `not_requested`. Rendering that
fresh response with the production replay-comment builder produced
`【建议对客回复】` followed by `【Internal Only】` and no `【内部交接】` label.

## Next validation action

Keep the paired-comment label and unchanged-wire-field tests as preservation
checks. No write replay or Jira comment refresh is required for this
presentation-only change.