The scheduled E2E suite has been red for 3+ weeks with ~19 deterministic
failures across 9/10 shards. All are test-side issues (stale assertions,
CI-timing races, over-strict perf thresholds, and fixture gaps); no product
regressions were found. Two small app changes are test-support only:
a stable data-testid on the GitHub item detail surface, and honoring
prefers-reduced-motion in the sidebar reveal scroll (also an a11y win).
Fixes:
- github-cli-stall / pr-comments / onboarding: update stale assertions to
current UI (inline GitHub detail, removed 'Open' badge #7338, error-state
recovery #6473, Host-selector Add Project UI).
- source-control / workspace-space-git-status: poll worktrees.list past the
5s detection-scan cache; match git-reported store paths (not realpath'd).
- terminal-column-desync / combined-diff: poll to convergence instead of a
fixed wait; ignore virtualizer remeasurement in the scroll-jump metric.
- terminal-tui-wheel-reports/-drain: space notches past the burst window;
reduce dense CDP stream + test.slow to fit the 120s budget.
- settings-display-name-ime: commit the IME composition (persist-on-commit
since #6238). onboarding: broaden step predicate for auto-skipped steps.
- terminal-shortcuts: guard the split before Cmd/Ctrl+W and confirm the
'Stop and Close' dialog. tab-close: drain late startup terminals.
- artificial-opencode: tolerate a single scheduler spike in the drift gate.
- worktree: resolve create base to the local HEAD branch; assert URL-resolve
reuse via the lookup count.
Co-authored-by: Orca <help@stably.ai>
* chore(lint): upgrade oxlint to 1.71 and enable 7 new rules
Upgrade oxlint 1.67.0 -> 1.71.0 (1.72 was blocked by the repo's 3-day
minimum-release-age supply-chain guard; nothing here needs it). The
bump is a no-op on the existing config.
Enable 3 error rules (backlog autofixed to zero in this commit) and
4 warn rules (surface signal without gating CI):
error (autofixed, behavior-preserving):
- unicorn/prefer-node-protocol (~1531 sites: bare builtin -> node:)
- typescript/no-import-type-side-effects (~36: all-inline-type -> import type)
- unicorn/no-array-reverse (19: copy-then-reverse -> toReversed)
warn (real signal, current fires are test-only/correct):
- unicorn/no-array-fill-with-reference-type (aliasing footgun guard)
- typescript/no-unsafe-function-type (bans bare Function type)
- unicorn/prefer-array-flat-map (map().flat() -> flatMap())
- unicorn/prefer-regexp-test (.match() in bool ctx -> .test())
mobile/.oxlintrc.json extends root, so it inherits all 7; the autofix
ran from root and covered mobile/ too.
Verification (all green): oxlint 0 errors (root+mobile+aux configs),
oxfmt clean, typecheck (node+cli+web), vitest 22795 passed / 0 failed,
builds (electron-vite + web + cli) succeed. node: rewrites confirmed to
skip embedded SSH/CLI string payloads (AST-only); all toReversed sites
verified to operate on fresh copies or write-once locals.
* chore(lint): bump mobile oxlint to 1.71 so inherited rules parse
mobile/ is a standalone pnpm project pinning its own oxlint@1.67, which
lacks unicorn/no-array-fill-with-reference-type (needs >=1.70). Since
mobile/.oxlintrc.json extends the root config, mobile CI's 'cd mobile &&
oxlint' failed to parse the new rule. Bump mobile to match root (1.71).
Verified in mobile/: oxlint 0 errors, oxfmt --check clean, tsc --noEmit
pass, vitest 978 passed / 0 failed.
Co-authored-by: Orca <help@stably.ai>
---------
Co-authored-by: Orca <help@stably.ai>