fix(web): keep the Workspace rail clear of the OS status and nav bars

[btli]

Related issue

Closes #3585

Summary

On a tablet or unfolded foldable (Pixel 10 Pro Fold), the right Workspace rail rendered underneath the OS status bar — its Files / Agents / Shells / Tasks tab icons sat in the occluded band and could not be tapped — and its bottom edge ran under the gesture-nav bar.

The rail is md:m-2 (8px on every edge) and, being hidden md:flex, only exists at ≥768px. Every native-shell inset rule lives inside @media (width < 48rem) (index.css:522→731), so none of them can reach it; it is also absent from the shared panel selector lists on both the CSS side and the Android-injected side. Its top edge therefore landed at y = 16px, inside a 24–48dp status bar.

• Add the safe-area margins outside the width gate, scoped to :is([data-ios-native], [data-android-native]), so both native shells get it and browser/Electron are untouched.
• Mirror the identical declaration into the Android injected sheet (ensureInsetStyles) so shells pointed at a server running an older web build get the fix from an APK update. Same property, same value, so the two stylesheets are idempotent and cannot double-count.
• Separate, independently droppable commit: the execution-logs panel docks as a full-height rail at md+ but was missing from both selector lists, so it had no safe-area padding at any width. Debug-mode only, which is why it went unnoticed.

Uses --omnigent-safe-*, not --omnigent-inset-* — the latter folds in the native bottom-bar footprint and would double-count against the bottom edge.

BEFORE                          AFTER
┌──── status bar ────┐          ┌──── status bar ────┐
│ ▣ ▣ ▣ ▣  ← dead    │          ├────────────────────┤
├────────────────────┤          │ ▣ ▣ ▣ ▣  ← tappable│
│  workspace rail    │          │  workspace rail    │

ELI5: the rail is a floating card pinned 8px from the screen edges. On phones a separate set of rules pushes UI clear of the status bar, but those rules switch off at tablet width — exactly where this card starts existing. So it kept its 8px and slid under the clock and battery icons.

Test Plan

• npx vitest run src/index.css.test.ts — 16 passed.
• The regression test pins the property that actually matters: the rule must apply at md+. It asserts the rule has no enclosing at-rule of any kind, that every rule setting the rail's margins is top-level and uses --omnigent-safe-* rather than the inset vars, and that exactly one such rule exists.
• Mutation-checked throughout — an early version of this test passed while the fix was inert, so each hardening was accepted only after the corresponding mutation went red. The suite now fails for: wrapping the rule in @media (width < 48rem), @media (max-width: 767px) or @supports; appending a later @media (min-width: 48rem) block that zeroes the margins; a second top-level rule reintroducing the inset vars; shorthand margin and logical margin-block* overrides; and the same selector written single-quoted, unquoted or with extra spacing.
• pre-commit run --files <changed files> — passed. npm run lint — no new findings.
• Reviewed by three independent engines (gpt-5.6-sol, Grok 4.5, Gemini 3.1 Pro) over six rounds; all three report clean on the final state.

Note the uniqueness assertion will deliberately fail if someone later adds a second margin rule for the rail. That is intended: this rule was silently inert on every tablet until now, so a future change to it should require a human to look rather than pass quietly.

Demo

Recorded on an Android emulator at 800×1280 @ 160dpi (an 800dp-wide viewport, i.e. the md+ tablet/unfolded-foldable layout) with the tall display-cutout overlay enabled, connected to a local server.

Before (main APK)	After (this PR's APK)

Before: the Workspace rail's Files / Agents / Shells tab icons render inside the status bar, sharing the row with the clock and battery; tapping them does nothing (the taps land on the system bar), while content lower in the rail still responds. After: the rail's card starts below the status bar and clear of the gesture-nav area, and the same taps switch tabs normally. Full-resolution MP4s alongside the GIFs on the asset branch.

The floating server pill visible near the top of the "after" capture still overlaps web chrome — that is the separate defect fixed by #3589 and is untouched by this PR.

Type of change

• Bug fix
• Feature
• UI / frontend change
• Refactor / chore
• Docs
• Test / CI
• Breaking change

Test coverage

• Unit tests added / updated
• Integration tests added / updated
• E2E tests added / updated
• Manual verification completed
• Existing tests cover this change
• Not applicable

Coverage notes

The CSS contract is covered by the mutation-checked regression test above, and the rendered result is now verified on an emulator at md+ width (see Demo), including the tap behaviour before and after. Not yet verified on physical foldable hardware. The inset values themselves are unchanged and already exercised on phones — this change only adds a new consumer of them.

Deliberately out of scope, and worth a follow-up: the same @media (width < 48rem) gate means that at iPad widths the chat header, conversation content, terminal view and composer are also uncovered, because iOS has no injected-sheet backstop the way Android does. This PR fixes the rail on both shells but does not make iPad correct in general.

Changelog

The workspace rail on Android tablets and foldables no longer slides under the status bar, so its tab icons stay tappable

[btli]

Withdrawing — this isn't the right fix for the rail inset issue; a different approach is coming.

[btli]

Reopening after discussion — this approach is correct after all.

[btli]

Pushed 2 commits:

• The workspace rail pads content clear of the OS bars on all four edges instead of shrinking with top/bottom margins, so its background and divider stay flush; lateral insets fold into --omnigent-safe-left/right.
• Published insets include the display cutout, which systemBars() alone omits; the injected fallback sheet mirrors the same rules.
• Plus a test-helper dedup in the CSS contract tests.

Verification: web suite green on this branch (4,715); Android green except one pre-existing failure (configuration change updates system bar icon polarity) — this branch's base reads resources.configuration, which lags direct onConfigurationChanged calls under Robolectric. #3800 fixes that by passing the Configuration in, hence the rebase note below.

---

Recommended merge order — this PR is one of seven fixed and verified together; the fully integrated reference (all cross-PR conflicts resolved, 5,003 web tests + 273/273 Android tests green) is btli:test-android-ui-integration @ 3fa45ff3.

Android track (suggest landing first — security fixes, and the later two resolve against it):

1. fix(android): sign in to servers behind front-door auth proxies (Databricks Apps) #3800 — no dependencies
2. fix(web): keep the Workspace rail clear of the OS status and nav bars #3587 — rebase after fix(android): sign in to servers behind front-door auth proxies (Databricks Apps) #3800: it picks up applySystemBarContrast(Configuration), which fixes this branch's one pre-existing Robolectric failure; and since main now has flush rails (feat(web): make the rails flush boxes and move the canvas gradient #4020), the rebase should also drop the stale +16 from --workspace-panel-offset (see integration commit 8b687d7c)
3. fix(android): keep the server switcher centred over the chat column, clear of header controls #3589 — after fix(android): sign in to servers behind front-door auth proxies (Databricks Apps) #3800: both add constructor callbacks to OmnigentBridgeListener; union them (resolution in integration merge 3fa45ff3)

Web track (file-disjoint from the Android track; order within it matters):
4. #3985 — base swipe-actions feature
5. #4060 — folder context menu
6. #4057 — mobile ungroup drop zone
7. #4065 — hold: superseded by the unified row-gesture recognizer, which builds on #3985 and interacts with #4057/#4060; after 4–6 land, update it to the recognizer commits (69a8ada5, bf597b87, e388aacf, reachable on the integration branch)