feat(llm-detector): Add config for LLM Detected issues

[roggenkemper]

pr adds a new config for the ai detected issue category which allows more control over what we show on the issue details page

fixes https://linear.app/getsentry/issue/ID-1084/add-new-issue-type-config-for-new-issue-category

[cursor]

Bug: AI Issues Misclassified as Performance

The eventOccurrenceTypeToIssueCategory function incorrectly categorizes AI detected issues (occurrence type 3501) as IssueCategory.PERFORMANCE instead of IssueCategory.AI_DETECTED. Since 3501 is >= 1000, it matches the performance condition. This prevents aiDetectedConfig from ever being applied, causing AI detected issues to use performance configuration instead.

static/app/utils/issueTypeConfig/index.tsx#L124-L129

sentry/static/app/utils/issueTypeConfig/index.tsx

Lines 124 to 129 in ae3104f

	hasTitle &&
	!!getErrorHelpResource({title: params.title!, project})
	);
	}
	const eventOccurrenceTypeToIssueCategory = (eventOccurrenceType: number) => {

 

---

[linear]

ID-1084 Add new Issue Type Config for new Issue Category

[cvxluo]

should we generally be consistent with AI detected vs LLM detected?

[roggenkemper]

In my opinion - AI Detected is what we are calling the issue category,LLM detected so far is what we are calling the type. so for now if we can stay consistent with that, i think we are fine (changing these later isn't too difficult)