Skip to content

fix(codearts): OT session/trace headers after sign (hub #723 / tip 28527f4) - #463

Merged
caigee-cmd merged 1 commit into
mainfrom
feat/codearts-ot-session-headers
Nov 3, 2026
Merged

caigee-cmd merged 1 commit into
mainfrom
feat/codearts-ot-session-headers

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

Align CodeArts chat with WorkBuddy tip 28527f4 / v1.10.1 (hub issue/PR context #723):

  • After SDK-HMAC-SHA256 signing, set account-stable x-ot-session-id and user-session-id (sha256(codearts-ot-session:+userID) hex[:32], same seed as hub)
  • Set per-request x-ot-trace-id (fresh 32 hex)
  • These headers are applied after signRequest, so they are not listed in SignedHeaders

No cloak bumps, other providers, catalog, frontend, merge, release, or SGP3 deploy.

Test plan

  • go test ./internal/providers/codearts/ -run 'OTSession|ApplyOT|ChatOT'
  • Full go test ./internal/providers/codearts/
  • Assert tip seed hash matches hub for user-1
  • SignedHeaders omit the three tip headers; session ids stable across two chats; trace differs

Refs: workbuddy2api-hub #723 / tip 28527f4 / v1.10.1

Align CodeArts chat with WorkBuddy tip 28527f4 / v1.10.1: after
SDK-HMAC signing, set account-stable x-ot-session-id and
user-session-id plus a per-request x-ot-trace-id, kept out of
SignedHeaders so Huawei stops treating every call as a new session.
@caigee-cmd
caigee-cmd merged commit a78a0f8 into main Nov 3, 2026
6 checks passed
@caigee-cmd
caigee-cmd deleted the feat/codearts-ot-session-headers branch November 3, 2026 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant