* fix(wsl): keep background git and GitHub reads from booting a stopped distro
Git history, diff and status-follower reads, GitHub issue/work-item/check
polls, chat link existence checks, the composer's create-base prefetch,
the worktree-root fan-out and the Settings/Automations orca.yaml previews
now refuse or skip a stopped WSL distro instead of starting it (E9).
* fix(wsl): explicit opens may start a stopped distro; more polls gated (E9)
Folds the parallel G1-G6 work into this branch and splits background
reads from user acts:
- An explicit open runs as a user act for its distro and may boot it:
showing a diff tab or its Retry, showing Commits or its Refresh,
opening the checks panel or entering its tab, checks Refresh, a check
action, and linking or creating a PR. Main takes a wakeWslDistro flag
on git:diff, git:branchDiff, git:commitDiff, git:history and
gh:prChecks and runs those reads under runAsWslUserAct.
- Polls, timers, refreshes after Git actions, prefetches and fan-outs
stay background and are refused while the distro is stopped.
- Also gated: the hosted-review card poll for every provider, the GitLab
checks-panel poll (background flag), and the composer's open-time
orca.yaml check (Create re-checks in the foreground).
- Pollers keep the data they already show on a refusal: the issue on a
card, the checks list, an open diff and loaded submodule children, and
stop logging it.
* docs(wsl): note that a hosted-review poll's stopped-distro refusal is still logged (E9)
* fix(wsl): Settings re-asks orca.yaml once a stopped distro runs; drop link-check gating (E9)
- Link existence checks (shell:pathsExist / pathExists) are no longer
gated here: answering "missing" cached chat and terminal links as
absent and toasted "File not found" on markdown link clicks. The
pathsExist refusal lives in its own PR, which throws instead.
- Settings no longer sits on "checking" forever: a repo whose distro
refused the background check is re-asked on window focus, on
visibility, and after 10 s, until it answers. An unverifiable distro is
now marked (wsl-distro-unverifiable) and treated as unread too, instead
of being stored as "no orca.yaml".
- The sidebar issue poll and the Tasks list and count refuse with "Open a
terminal in it to start it", since their Retry is itself a background
read; the checks panel keeps "Retry", whose Refresh is a user act.
* fix(wsl): Tasks Refresh, interactive review refresh and manual PR lookups may start a stopped distro (E9)
- Tasks: a Refresh, Retry or search, or Tasks opened on a single repo,
passes wakeWslDistro through gh:listWorkItems and gh:countWorkItems
(IPC only; the RPC twins and web routes drop it). A multi-repo open
stays background. Their refusal says "Retry" again; only the sidebar
issue poll says "Open a terminal".
- hostedReview:forBranch wakes for an interactive request (the checks
panel's manual Refresh), so GitLab, Bitbucket, Azure DevOps and Gitea
reviews with nothing cached can load.
- gh:prForBranch, the renderer's fallback when refreshPRNow is missing,
is gated like the other card polls; a manual lookup wakes, matching
refreshPRNow's manual-only rule. The fallback call moves into its own
module, built from the refresh candidate.
* fix(wsl): only an explicit Refresh starts a stopped distro for review status (E9)
hostedReview:forBranch woke on admissionTier 'interactive', but the
visible-review scheduler sends 'interactive' for the selected card on a
timer, so that poll restarted a stopped distro every interval. The wake
is now an explicit wakeWslDistro flag (desktop IPC only). The card
refresh helper sets it, since every caller follows a user act (the
checks panel's manual Refresh, or a review created, linked or edited),
and the manual Refresh also wakes its pre-refresh git status.
admissionTier is back to priority only.
* fix(wsl): an explicit review Refresh never joins a refused poll (E9)
fetchHostedReviewForBranch let a forced card Refresh join an in-flight
forced scheduler poll, since the join only compared force. On a stopped
WSL distro that poll is refused, so the click got the refusal. The
in-flight entry now records the wake, and a waking request joins only a
waking flight; a poll may still join an explicit Refresh.
#14397 split `shared/types.ts` into 46 per-domain modules but kept the path as
a re-export barrel so the import sites did not have to change. This removes
the barrel: every consumer now imports from the module that actually declares
the type, and `src/shared/types.ts` is deleted.
Barrels hide where a type lives, make every consumer look like it depends on
the whole domain, and let an unrelated edit invalidate a module that ~2,000
files transitively import.
2,323 import declarations across 2,321 files. Rewritten mechanically: each
specifier was resolved to an absolute path via the TypeScript AST and
recomputed, rather than string-substituted, so alias forms (`@/../../shared/
types`) and per-specifier `type` modifiers survive.
Four cases the mechanical pass had to handle, each found by a gate rather than
by reading the diff:
- Modules inside `src/shared` import the barrel as `./types`, not
`shared/types`. A pre-filter on the latter string skipped 176 of them and
left imports dangling at a deleted file, which surfaced as confusing
`Property 'x' is optional in type 'Repo' but required in Pick<Repo, ...>`
errors rather than "module not found".
- The barrel RENAMED one type on the way through
(`WorkspaceSource as WorkspaceCreateTelemetrySource`), so the original name
in the owning module has to be re-aliased at each consumer.
- Three test files put `;(globalThis as ...)` on the line after the import.
TypeScript parses that `;` as the import statement's terminator, so
replacing through `statement.getEnd()` deletes it and breaks ASI. The
rewrite now stops at the module specifier.
- A file that already imported directly from a module got a SECOND import
from it, because the barrel re-exported those same names — which trips
`import/no-duplicates` under `--deny-warnings`. A post-pass merges
declarations sharing a specifier and type-only-ness; the `import type` plus
`import` pair from one module is left alone, since that form is allowed.
Splitting one barrel import into several genuinely adds lines, which pushed
`terminal-layout-pty-ownership.ts` to 301 counted lines: its 107-character
import must wrap, and neither local type collapses onto one line (101 and 116
characters). Rather than contort a type declaration to fit a line budget,
`collectLeafIds` and `pruneLeaves` move to `terminal-pane-layout-tree.ts` —
they are pure structural operations on the layout tree and independent of PTY
ownership. `visible-worktrees.ts` similarly loses its own mini-barrel
re-export of `isDefaultBranchWorkspace`, with the four real consumers
repointed at the declaring module. No `max-lines` bypass added.
Verified: cold `tsc --noEmit` green on node, cli, and web (buildinfo deleted
first — these projects are `composite: true` and reuse stale caches); the full
`pnpm lint` green, not just bare oxlint — the narrower local check is what let
the duplicate imports reach CI; max-lines ratchet OK at 344.
`src/preload/api-types.ts` was 3,752 raw lines (3,533 counted, 11.8x the
300-line budget) behind an `eslint-disable max-lines`. Almost all of it was a
single `PreloadApi` object type whose ~83 namespace properties were declared
inline, so any IPC surface change meant editing one 2,600-line type.
Give each namespace a named type in its own module under `src/preload/api/`
(`pty-api.ts`, `filesystem-api.ts`, `github-pull-request-api.ts`, ...) and
recompose `PreloadApi` from those names. `api-types.ts` keeps the `declare
global` Window augmentation and re-exports every moved name, so all 52 import
sites are untouched.
Two shapes needed care to stay type-identical rather than merely compatible:
- Three keys (`gh`, `git`, `ui`) are composed from two modules each. A plain
intersection is NOT identical to the original flat object literal, so those
use a `Merged<T>` mapped type; a negative control confirmed that dropping it
fails the parity assertion.
- Keys whose module groups several namespaces use indexed access
(`fs: FilesystemApi['fs']`) to preserve exact identity and source order.
`config/tsconfig.web.json` and `tsconfig.tc.web.json` enumerate files by path,
so they need `src/preload/api/**/*` alongside the existing `api-types.ts` seed
or the web projects fail TS6307.
Verified by exact type identity, not assignability: 41 assertions of the form
`Equals<Now.X, Before.X>` against a frozen pre-split snapshot, covering every
exported name, plus a per-key pass over all 83 `PreloadApi` keys. All three
projects typecheck clean with those assertions active.
Verification note: these tsconfigs are `composite: true`, and `tsc --noEmit`
will reuse a stale `.tsbuildinfo` and report clean for a state that genuinely
fails. Every result above was produced after deleting the buildinfo, including
a negative control confirming the gate still fails on deliberate drift.
Drops the `max-lines` bypass and its baseline entry (ratchet 346 -> 345).