# Time labels can show UTC clock values with UTC+08:00 labels.

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "final-time-presentation-2026-09-07",
  "problems": [
    {
      "problemId": "time-offset-label-inconsistent",
      "summary": "Time labels can show UTC clock values with UTC+08:00 labels.",
      "status": "optimized_unverified",
      "applicability": "Final Response presentation prompt",
      "issueKeys": [
        "APID-29470"
      ],
      "sourceRefs": [
        "https://tidb.atlassian.net/browse/APID-29470#problem:time-offset-label-inconsistent"
      ],
      "signalTextIncludesAny": [
        "UTC+08:00"
      ],
      "observedThrough": "2026-09-07",
      "effectiveAt": "2026-09-07T15:29:20Z",
      "verifiedAt": null,
      "attemptedAction": "The one timezone presentation instruction is deployed in AOS 65232e57. Operator requested a simple canary and publication of the existing read result instead of another full replay; no new Final Response was generated.",
      "evidenceUrl": "https://github.com/tidbcloud/aisupport/actions/runs/34137649995"
    }
  ]
}
-->

Owner: Final Response presentation prompt. Source: explicit operator request after isolated run `5aa523af-28ca-4bec-bf8e-6ae4270cc033`.

Add one timezone presentation instruction; preserve the Router-owned instant and avoid double offsets or invented conversions. This cannot recover an incorrect Router time without an unambiguous source.

Implementation prepared; no new live verification or Jira publication. Validation: 1,167 full unit tests and six isolated-runner checks passed; the subsequently added stale-recovery test passed with the worker suite. Skill metadata validation and diff checks passed. Next validation: publish the Skill and deploy the merged image/configuration, then verify the same case. A prompt-only time instruction is not proof of correcting an already-invalid Router timestamp.


## Deployed, without a new Final Response evaluation

Release 34137649995 attempt 2 and app-delivery PRs #79458/#79459 deployed AOS `65232e57`; the new Ready service was checked after its Pod was created at 2026-09-07T15:29:02Z. The operator explicitly requested no new full replay. The bounded TopSQL canary does not execute or verify Final Response. Publishing the existing frozen run `5aa523af-28ca-4bec-bf8e-6ae4270cc033` preserves its original time-label mismatch; its content must not be rewritten or attributed to this new prompt. Keep this presentation change unverified until a future authorized case-specific evaluation produces a correctly labeled new answer.

The original frozen answer was subsequently published successfully to internal Jira comment `23815249` through `publish-read`; this is publication of the earlier answer, not validation of the new presentation prompt.