Improve premium search enforcement and Svelte upgrade guidance

[Copilot]

What changed

• Improved the Svelte event and stack search experience so free-plan users see upgrade guidance for the effective filter, including saved views.
• Made premium-field detection resource-specific so free stack fields such as critical, first, and last are not incorrectly labeled premium.
• Kept premium search enforcement at the API boundary for event search, event count, and stack search requests.

Why

The Svelte UI previously used the event field rules for both event and stack routes and only inspected the raw URL filter. This produced false upgrade prompts for valid free stack searches and missed premium filters supplied by saved views. Direct API requests could also bypass UI guidance and receive silently filtered results.

Behavior

• Premium search filters on non-premium organizations return 426 Upgrade Required.
• The Svelte UI shows upgrade guidance for premium event and stack filters.
• Free event and stack filters continue to work without an upgrade prompt.
• No public API shape, WebSocket message, configuration key, or legacy Angular behavior changed.

Verification

• npm run validate
• npm run test:unit — 310 passed
• npm run build
• Three targeted controller regressions — passed
• Local Svelte dogfood against Aspire:
  • stack critical:true — no upgrade prompt
  • stack title:timeout — upgrade prompt shown
  • event reference:ABC123 — no upgrade prompt
  • event tags:important — upgrade prompt shown

Breaking changes

None.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ niemyjski
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b0727eace1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve free stack filters in stack-mode event searches

For free organizations using the Svelte Stacks page with a stack-only free filter such as first_occurrence, last_occurrence, or critical, this new block returns 426 before the stack-mode path can apply EnforceEventStackFilter(). The page still requests organizations/{organizationId}/events with mode: 'stack_frequent' (stack/+page.svelte lines 598 and 669), so this method validates those stack filters with PersistentEventQueryValidator, whose free event fields do not include the stack-only fields that EventStackFilter later supports. That makes the new “free stack fields” UI guidance disagree with the API and breaks those stack searches for free plans.

Useful? React with 👍 / 👎.

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
Exceptionless.AppHost	39%	41%	136	❌
Exceptionless.Core	72%	64%	8644	➖
Exceptionless.Insulation	24%	23%	205	❌
Exceptionless.Web	79%	67%	5241	✔
Summary	72% (17206 / 23740)	64% (8787 / 13686)	14226	➖