1. [P1] Treat remap failures as resume failures — if replaceSubagentRunAfterSteer
   returns false, do NOT clear abortedLastRun, increment failed count.

2. [P2] Count scan-level exceptions as retryable failures — set result.failed > 0
   in the outer catch block so scheduleOrphanRecovery retry logic triggers.

3. [P2] Persist resumed-session dedupe across recovery retries — accept
   resumedSessionKeys as a parameter; scheduleOrphanRecovery lifts the Set to
   its own scope and passes it through retries.

4. [Greptile] Use typed config accessors instead of raw structural cast for TLS
   check in lifecycle.ts.

5. [Greptile] Forward gateway.reload.deferralTimeoutMs to deferGatewayRestartUntilIdle
   in scheduleGatewaySigusr1Restart so user-configured value is not silently ignored.

6. [Greptile] Same as #4 — already addressed by the typed config fix.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
(cherry picked from commit 98f6ec5)

1. [P1] Treat remap failures as resume failures — if replaceSubagentRunAfterSteer
   returns false, do NOT clear abortedLastRun, increment failed count.

2. [P2] Count scan-level exceptions as retryable failures — set result.failed > 0
   in the outer catch block so scheduleOrphanRecovery retry logic triggers.

3. [P2] Persist resumed-session dedupe across recovery retries — accept
   resumedSessionKeys as a parameter; scheduleOrphanRecovery lifts the Set to
   its own scope and passes it through retries.

4. [Greptile] Use typed config accessors instead of raw structural cast for TLS
   check in lifecycle.ts.

5. [Greptile] Forward gateway.reload.deferralTimeoutMs to deferGatewayRestartUntilIdle
   in scheduleGatewaySigusr1Restart so user-configured value is not silently ignored.

6. [Greptile] Same as #4 — already addressed by the typed config fix.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
(cherry picked from commit 98f6ec5)

…hes #2517-class regressions (#2519)

Extends app.smoke.test.ts (#2495/#2496) with a browser-mode smoke suite
that mounts <remoteclaw-app> into a desktop viewport (1280x720 via
page.viewport() from vitest/browser), waits for layout (updateComplete
+ double rAF), and asserts getBoundingClientRect dimensions on
.sidebar / .topbar-status / .nav-section / section.chat — catching the
#2517 regression class where production class renders but structural
wrappers are missing, so the sidebar lands in the wrong grid cell and
nav content escapes the visible area.

Scope:
- ui/src/ui/app.computed-style.test.ts — 4 tests, ~2.1s runtime, uses
  mountApp helper + explicit ../styles.css import (matches
  navigation.browser.test.ts pattern)
- .github/workflows/ci.yml — new test-ui-smoke job, installs Chromium
  via "pnpm --dir ui exec playwright install --with-deps chromium",
  runs pnpm test:ui:smoke; wired into CI aggregator needs
- package.json — root test:ui:smoke script runs the two smoke suites
- CLAUDE.md — new "Browser-mode smoke tests" subsection under
  § Testing documenting the lane and its scope discipline

AC #4 verified empirically: removing the .shell-nav / .sidebar-shell /
.sidebar-nav wrapper hierarchy makes the sidebar-fits-viewport test
fail ("expected 52 to be greater than 300") and the nav-section header
position test fail ("expected 90.31 to be less than or equal to 53.31").

The test-ui-smoke CI lane is scoped to the two sync-regression suites
only — the broader pnpm test:ui has unrelated pre-existing failures
(cron.test.ts / sessions.test.ts / etc.) that are out of scope.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…hes #2517-class regressions (#2519) (#2532)

Extends app.smoke.test.ts (#2495/#2496) with a browser-mode smoke suite
that mounts <remoteclaw-app> into a desktop viewport (1280x720 via
page.viewport() from vitest/browser), waits for layout (updateComplete
+ double rAF), and asserts getBoundingClientRect dimensions on
.sidebar / .topbar-status / .nav-section / section.chat — catching the
#2517 regression class where production class renders but structural
wrappers are missing, so the sidebar lands in the wrong grid cell and
nav content escapes the visible area.

Scope:
- ui/src/ui/app.computed-style.test.ts — 4 tests, ~2.1s runtime, uses
  mountApp helper + explicit ../styles.css import (matches
  navigation.browser.test.ts pattern)
- .github/workflows/ci.yml — new test-ui-smoke job, installs Chromium
  via "pnpm --dir ui exec playwright install --with-deps chromium",
  runs pnpm test:ui:smoke; wired into CI aggregator needs
- package.json — root test:ui:smoke script runs the two smoke suites
- CLAUDE.md — new "Browser-mode smoke tests" subsection under
  § Testing documenting the lane and its scope discipline

AC #4 verified empirically: removing the .shell-nav / .sidebar-shell /
.sidebar-nav wrapper hierarchy makes the sidebar-fits-viewport test
fail ("expected 52 to be greater than 300") and the nav-section header
position test fail ("expected 90.31 to be less than or equal to 53.31").

The test-ui-smoke CI lane is scoped to the two sync-regression suites
only — the broader pnpm test:ui has unrelated pre-existing failures
(cron.test.ts / sessions.test.ts / etc.) that are out of scope.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>