fix(web): resolve Vite sourcemap and supports warnings

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}

[juliusmarminge]

What Changed

• Corrected Tailwind supports variants in the composer surfaces so Vite no longer reports invalid selector warnings.
• Simplified pull request detail actions to keep their labels visible and avoid responsive header overflow.
• Removed the composer-driven page-scroll controller and its tests.

Why

The web build emitted sourcemap and CSS supports warnings, while the pull request action header contained unnecessary responsive complexity. This change removes the warning sources and simplifies the affected UI and scroll handling.

UI Changes

The pull request detail header now uses consistently labeled action buttons and badges. No before/after screenshots are included.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Class-string and Vite CSS sourcemap wiring only; no auth, data, or API changes, with intended visual behavior unchanged.

Overview
This PR quiets web build warnings by fixing Tailwind not-supports-[...] syntax on chat composer glass fallbacks and aligning CSS sourcemap settings with the existing build flag.

In ComposerBanner and ComposerSurface, the backdrop-filter fallback variants now wrap the or condition in an extra pair of parentheses (e.g. not-supports-[((backdrop-filter:blur(1px))_or_(...))]), so Vite/Tailwind stop treating the selector as invalid while keeping the same “no backdrop blur → solid surface” behavior.

vite.config.ts sets css.devSourcemap to match build.sourcemap (buildSourcemap !== false), because @tailwindcss/vite only emits CSS sourcemaps when dev sourcemaps are on—otherwise rolldown reports SOURCEMAP_BROKEN on sourcemapped builds.

^{Reviewed by Cursor Bugbot for commit b583147. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Tailwind not-supports syntax in chat components and enable Vite CSS sourcemaps

• Groups the full backdrop-filter OR webkit-backdrop-filter condition inside the negated supports query across chat UI components in ComposerBanner.tsx and ComposerSurface.tsx
• Adds a CSS sourcemap setting in vite.config.ts that enables dev CSS sourcemaps whenever buildSourcemap is not explicitly false
• Behavioral Change: fallback background styling for chat surfaces is now generated from a grouped negated support condition; browsers without supported backdrop-filter implementations get the fallback

^{Macroscope summarized b583147.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.2 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.3 KiB	+496 B (+8.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.5 KiB	+5.7 KiB (+11.6%)	66.4 KiB	✅
Codex	Live turn messages	16	8	−8 (−50.0%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+1.9 KiB (+16.9%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+515 B (+8.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.3 KiB	+5.7 KiB (+11.4%)	66.4 KiB	✅
Claude	Live turn messages	16	8	−8 (−50.0%)	21	✅

Baseline: 83d769f · PR result: b583147 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at b583147

Macroscope's review found this PR approvable — This is a narrow maintenance fix that corrects existing CSS feature-query syntax and enables development CSS sourcemaps to match the established sourcemap setting. It adds no new capability, does not change production bundle sourcemap behavior or product defaults, and does not suppress static-analysis diagnostics.

^{You can add or adjust custom eligibility rules. Learn more.}