chore(event formatter): add new event formatter to mcp

[shayna-ch]

to be merged after endpoint pr

Switches the MCP issue/event and autofix output to consume Sentry's shared-formatter output when it's available:

• getEventForIssue and getAutofixState now request ?llmFormat=markdown.
• BaseEventSchema and AutofixRunStateSchema gain an optional formatted: {format, content} field.
• formatIssueOutput uses event.formatted.content for error / default / generic / csp events (re-adding the replay note so output still matches formatEventOutput), falling back to formatEventOutput otherwise.
• analyze-issue-with-seer uses autofixState.formatted.content at each terminal/progress output point, falling back to getOutputForAutofixRun.

No behavioral change on merge. behind the issues.standardized-markdown-for-llm option. Rollout will happen gradually via feature flag.

[shayna-ch]

bugbot run

[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 e7f534f. Configure here.}

[cursor]

Seer status omitted with formatted content

Medium Severity

When autofixState.formatted.content is present, formatSeerSummary returns early and skips the existing status handling for in-progress, failed, and awaiting_user_input runs. analyze_issue_with_seer still appends that status after using formatted content, so get_issue_details can hide that Seer failed or needs input once the shared formatter rolls out.

 

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