chore(widget): Sonnet 5.5 replaces Sonnet 5 (staging)

[manager]

What

The Ask UX Core widget now asks the subscription relay for Claude Sonnet 5.5 (claude-sonnet-5-5) instead of Sonnet 5. One constant in src/lib/widget/llmClient.ts; nothing else reads the model name.

The relay answers claude-sonnet-5-5 over its CLI transport: a probe on the production consumer token returned 200 on the first track on 2026-09-28. Until this ships, the target keeps asking for Sonnet 5, which still works.

Same commit as #248, cherry-picked onto dev: main and dev have separate histories since the squash release in #246, so the main-based branch conflicts with dev. The diff against dev is the same single line.

Authorized by Wolf on 2026-09-28 for staging.

🤖 Generated with Claude Code

[github-actions]

Claude finished @manager's task in 12s —— View job

---

Review of PR #249

• Read the diff against origin/dev
• Check for other references to the model name

Verdict: looks good, no issues found.

The change is one line in src/lib/widget/llmClient.ts: CLAUDE_MODEL goes from claude-sonnet-5 to claude-sonnet-5-5. A grep across src, mcp and scripts finds that constant as the only reference to a claude-sonnet* ID. That matches the PR description, so no other file needs to change.

Notes

• The scope is minimal. The PR touches no UX Core data, styling, or dependencies, and has no SSR or security implications.
• The dev cherry-pick matches the diff of chore(widget): Sonnet 5.5 replaces Sonnet 5 #248, and the description explains why it was needed.
• I couldn't run the relay probe from here, so I haven't independently checked the description's claim that claude-sonnet-5-5 returns 200 over the CLI transport. That was recorded in the PR as done on 2026-09-28.
• Per CLAUDE.md, merging to dev (staging) needs Wolf's direct go. The PR says he authorized it for staging on 2026-09-28. I have not merged anything.
• If staging shows the relay rejecting the new ID, reverting this line restores Sonnet 5, which the description says still works.