Improve table column and tag interactions

[ejsmith]

Summary

• remove redundant checkboxes from the column picker and make each row the add/remove target
• add optional Project columns to event and stack tables
• add optional compact Tags columns to event and global stack tables that show two tags plus a remaining count, with the hidden tags available in a theme-aligned hover surface
• use one neutral, bordered, clickable tag treatment across event and stack tables/details; clicking filters and the redundant per-tag filter icons are removed
• keep filter/copy guidance on individual tag tooltips while the overflow tooltip displays only the hidden tags
• align semantic log-level badges with the same compact tag shape, reduce their width, and use restrained 15% color-tinted backgrounds with 1px outlines in dark theme
• decode JSON-encoded exception extended data before rendering Additional Data so fields are not split into character rows
• include project names and tags in event and stack summary responses using cached bulk project lookups
• allow Project and Tags column state to be persisted in event, stack, and stream saved views

Verification

• npm run validate
• focused shared tag-list and log-level Vitest coverage (8 tests passed)
• focused exception Additional Data coverage for encoded, structured, and malformed extended data
• local synthetic COMException Playwright coverage confirms ErrorCode and ObjectName render as structured rows
• local Playwright dogfood coverage for event and stack Tags picker/table flows, the tags-only overflow tooltip, and matching event/stack tag presentation in light and dark themes
• saved-view Playwright coverage, including save/rename/reset/delete and switching views
• focused saved-view API coverage, including stack Tags persistence (6 tests passed)
• focused stack summary API coverage confirms tags are returned
• npm run build
• dotnet test -- --filter-class Exceptionless.Tests.Api.Endpoints.EventEndpointTests (103 passed)
• OpenApiSnapshotTests and SummaryDataTests (16 passed)

Breaking changes

None. The response additions are backward compatible, and the new columns are hidden by default.

[ejsmith]

/preview

[github-actions]

Preview deployed

• App: https://dev-app.exceptionless.io
• Collector: https://dev-collector.exceptionless.io
• Commit: b6f47d54f275
• Version: 8.6.3-preview.issue.column-picker-options.0.39
• Workflow run: view logs

[ejsmith]

/preview

[ejsmith]

/preview

[ejsmith]

/preview

[ejsmith]

/preview

[ejsmith]

/preview

[ejsmith]

/preview

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
Exceptionless.Core	73%	65%	9499	➖
Exceptionless.AppHost	38%	40%	139	❌
Exceptionless.Insulation	23%	23%	205	❌
Exceptionless.Web	84%	67%	6933	✔
Summary	76% (22526 / 29459)	65% (10357 / 15858)	16776	✔

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b6f47d54f2

ℹ️ 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]

Pass stack defaults into saved-view comparison

For any stack saved view created before these columns existed, columns lacks project and tags. The table now merges these false defaults into its current visibility, but the useSavedViews call above is not given defaultColumnVisibility, so columnsEqual sees two extra keys and reports the view as modified immediately; Reset only reapplies the legacy object and therefore cannot clear that state. Pass the same defaults to useSavedViews and cover legacy saved records missing the new keys.

AGENTS.md reference: AGENTS.md:L72-L75

Useful? React with 👍 / 👎.