* refactor(renderer): group browser and terminal modules by owner
* refactor: consolidate floating workspace type imports
* test: mark worktree card introduction seen in completed profiles
* refactor(renderer): place upstream terminal sleep owners with tab lifecycle
* ci(windows): require a trusted signature on every shipped Windows binary
The release gate checked only the binaries it had sent for signing plus a
fixed list. A Windows binary that skipped signing or arrived after staging
could ship unsigned, and Smart App Control machines refuse to load it; that
is how unsigned dev-channel builds lost their terminals on a test machine.
Release cuts now also check every .exe/.dll/.node in the shipped installer
payload (minus the non-Windows server-template binaries) for a valid
SignPath or Microsoft signature and fail with the offender list. Dev-channel
builds run the same check in advisory mode and never fail.
* ci(windows): match signers by CN and harden the payload signature gate
- Match our signer on its exact CN and Microsoft vendors on CN+O instead of
the full subject, so a certificate renewal that moves address fields
cannot block a cut; quoted, escaped and repeated attributes cannot spoof it.
- Say how to allow a vendor when the gate fails: release staging skips any
validly signed file, so a new vendor must be added to VENDOR_IDENTITIES.
- Reset LASTEXITCODE after the check so the fail-open path really warns,
and put the script's stderr into the evidence verdict when it cannot run.
- Force UTF-8 PowerShell output and time the signature read out after
10 minutes (reported as could-not-run).
- The pass message counts only the checked binaries and no longer claims
they are all SignPath-signed.
dev-fresh-profile spawned a bare `pnpm` with shell:false, which fails with
ENOENT on Windows where only pnpm.cmd/pnpm.exe exist. Use
resolvePnpmCliInvocation() like the other dev scripts so the child pnpm is
the one that launched the script.
Fixes#43413
Co-authored-by: Neeidaan <228572363+Neeidaan@users.noreply.github.com>
* fix(wsl): stop launching wsl.exe when WSL is not installed
Windows 11's inbox wsl.exe opens the installer on every invocation. Remember a missing WSLService and LxssManager for this process so distro, status, and running probes do not retry.
* fix(wsl): only treat a missing service as no WSL, and refuse every wsl.exe spawn once known absent
sc.exe exits 1060 only when the service is not registered. Access denied, a
timeout or a signal kill now stay unknown instead of hiding a real install
until restart.
Once absence is confirmed, process-host refuses any wsl.exe spawn with ENOENT,
so per-distro background work (stale saved distros, hooks, git, watchers)
cannot reopen the installer either.
* fix(wsl): reuse an unknown WSL service answer for 60 s
Denied or timed-out sc.exe queries were not cached, so every running-list
read spawned another sc.exe pair even inside the wsl.exe failure backoff
(ten reads: twenty sc.exe). Unknown now holds for 60 s; confirmed absence
stays a session latch. Covers each service name alone reporting present.
* fix(wsl): never query WSL services synchronously
Sync distro and home reads now use the cached service verdict. Without one,
they return what is cached and start the async query rather than spawning
wsl.exe, so a sync read on startup can't open the installer either. The main
process starts the query at launch. List the new module in the web tsconfig.
* fix(wsl): keep sync WSL readers answering before the service verdict
Before the async sc.exe verdict, sync readers returned empty, so a default-WSL
Claude launch could pick host credentials and a daemon session could freeze
an undefined distro and skip the stopped-distro hold. They now check, once per
process and without spawning, for LxssManager.dll or wslservice.exe: present
keeps the previous sync wsl.exe path, absent returns empty. An expired unknown
verdict keeps being served while it re-checks.
* fix(wsl): read WSL service registration from the registry before sc.exe
The file-path hint missed Store MSIX and custom-INSTALLDIR layouts. Sync
readers now check HKLM\SYSTEM\CurrentControlSet\Services\{WSLService,
LxssManager} through the bundled in-process registry addon: a key proves the
service is registered (no sc.exe at all), while a missing key or unloadable
addon leaves the verdict to sc.exe's 1060, and sync readers spawn nothing
until then. Drops the sync-fs baseline entry. The stale-unknown re-check is now
an explicit peekWslInstallationAndRefreshIfDue.
* test(wsl): keep the sc.exe service-query suite independent of the host registry
On a Windows host with WSL installed, the real WSLService key answered before
the mocked sc.exe and failed 9 of the suite's tests. Mock the registry reader
as having no WSL keys. Also fix a stale function name in a comment.
---------
Co-authored-by: Neil <neil@stably.ai>
* fix(ui): widen divider grab areas to 16px on the side away from scrollbars
* fix(ui): keep the diff tree separator on its original pixels
* fix(ui): leave sub-pixel divider crossings to the parent divider
* fix(ui): type the split handle overhang style without a cast
* fix(ui): ignore synthetic events in the divider native-drag guard
* feat(ui): widen tab and terminal split gaps to a real 16px instead of overlays
* test(ui): cover the 16px terminal divider box
* fix(ui): paint wide split gaps with the editor surface
* fix(ui): route gap file drops to the nearer pane, keep the seam under the pointer, and continue tab strips across split gaps
* fix(ui): layer the tab band border over the strip fill
* fix(ui): drop the gap drop relay; follow container moves and commit at release
* test(ui): drop the terminal divider size test that restates its formula
* ci: drop the e2e route to a spec deleted in #43014
The feature.terminal-pane-geometry route still named
issue-12656-terminal-link-tooltip, which #43014 removed, so any PR touching
terminal.css or pane-divider.ts failed 'changed e2e specs' on a missing file.
* refactor(ipc): group handlers and PTY support by owner
* chore(test): prune retired IPC timeout baseline
* fix(types): include worktree path settings in web project
#43014 removed plugin-syntax-smoke and plugin-theme-smoke but kept their
source routes, so any PR touching those sources (for example the
protected copy keys) failed 'changed e2e specs' on a missing spec file.
Frames only got the colour tokens and --orca-radius, so a plugin panel could
not match a user's chosen app font. Add --font-sans and --font-mono to the
panel design token allowlist; the existing theme sync already refreshes frames
in place when the root style changes, so a font change now restyles them too.
Native chat visuals already listed both tokens and now get them from the
shared allowlist.
Fixes#42575
Co-authored-by: Claude <noreply@anthropic.com>
* refactor(main): organize agent session and tab lifecycle owners
* fix(ci): carry moved backend test and mobile routing metadata
* test: retire copy assertions in headless notification test
* feat(mobile): add chat text size, font and line spacing settings
Pinching in a chat now saves the size for every chat instead of resetting when you leave.
* fix(mobile): measure the screen on the first chat text read, not at import
* feat(mobile): add a stepped slider control
* feat(mobile): terminal font, size, line spacing and weight settings
Terminal settings get a Font section with a live preview: a font picker
(system fonts plus JetBrains Mono, Fira Code and Geist Mono shipped as
variable woff2), a point-size slider replacing the old percentage presets,
line spacing and weight. Pinch now snaps to whole points. Tablets start at
15 pt, Normal spacing and Regular weight.
The size keeps its storage key as points over 13; the font, spacing and
weight live in a new negotiated page storage key. Both terminal hosts read
them at start and on a new set-font-style message; a style change keeps
the grid and lets the cell-box refit resize the PTY.
Spawn the status helper directly instead of through LaunchServices, and have it re-exec itself as its own responsible process so TCC still checks the helper's grant. A timeout now stops the probe by PID, so a late LaunchServices launch can no longer leave a suspended helper behind. Startup kills suspended probes left by older builds.
Co-authored-by: Mikel Vallejo <58292517+VallejoM@users.noreply.github.com>