fix(seer): Resolve UUID run_id in OrganizationSeerAgentUpdateEndpoint

[trevor-e]

What

After #117265 and #117780, the Seer Explorer frontend started sending sentry_run_id (a UUID) instead of the numeric seer_run_state_id for run identification. The chat endpoint's GET (poll) and POST (continue) paths were updated to resolve either form via resolve_seer_run(). The update endpoint (/seer/explorer-update/{run_id}/) was missed, so Seer's Pydantic model rejects UUID run IDs with:

{"detail":[{"type":"int_parsing","loc":["body","run_id"],"msg":"Input should be a valid integer, unable to parse string as an integer","input":"cac2b2c1-4fd7-4003-acc2-e0f1ca0a5640"}]}

Fix

Apply resolve_seer_run() to OrganizationSeerAgentUpdateEndpoint.post(), translating UUIDs (or numeric IDs) to seer_run_state_id before forwarding to Seer's /v1/automation/explorer/update. Mirrors the fix already applied to the chat endpoint.

• run_id type hint widened to str (the URL pattern already captured it as [^/]+)
• resolved.seer_run_state_id (int) used in the Seer request body
• Added test_explorer_update_with_uuid_run_id covering the UUID path end-to-end
• Updated existing run_id assertion from "123" → 123 (now correctly an int after resolution)

Reported by Sofia Rest. Refs #117265, #117780.

---

View Session in Sentry

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 165140d. Configure here.}