undici's HTTP/1 writer calls socket.setTypeOfService before each write,
outside any fetch promise. On macOS the syscall fails with EINVAL once the
peer has reset the socket (VPN, Wi-Fi switch, proxy), so a network change
became an uncaught main-process exception and a modal error dialog. Treat
the TOS syscall as best effort, as Node already does on Windows; the write
then fails through undici's normal ECONNRESET path. Argument validation
errors still throw.
The test resets a real peer connection and calls setTypeOfService on the
reset socket, reproducing the native EINVAL on macOS.
Fixes#39579
Co-authored-by: Jinwoo-H <jinwoo0825@gmail.com>
* Move environment store operations off the main thread
* Preserve CLI startup speed with the serialized environment owner
* Handle absent paired host labels in the producer regression fixture
* Preserve publication ownership and copy selected environment results
* Correct publication and WSL readiness regression fixtures
* Include environment store worker in deployed server artifacts
* Check fresh listing publication across an intervening store update
* Await store-backed results in new recovery coverage
* Retire failed page publications and retain CLI worker support entries
* Unpack environment store support modules for the installed CLI
* Align async store callers with their return contracts
* Avoid hardening work for absent environment store files
* Keep permission repair bounded to one hardening attempt
* Align store test fixtures and await pairing replacement
* Use the semantic store operation for external pairing fixtures
* Provide the live sender frame in the timed subscription fixture
* Share pending server lookups and settle retired phone requests
* Keep the relay error type import
* Keep status ownership and transport imports acyclic
* Await replacement pairing in status retirement cases
* Keep asynchronous server rows bound to their admitted pairing
* Keep inventory snapshots and queued delivery at one publication boundary
* Await saved-host and graph test setup through publication completion
* Finish async fixture types and remove foreground timing probe
* Await renderer surface transitions in process identity coverage
* Await nested graph publication fixtures through their callers
* Await restored pane graph publication before hook assertions
* Include imported store worker and sidebar files in web typecheck
* Prepare saved host storage in source-based WSL test rigs
* Await saved server lookups in the source retirement diagnostic
* Preserve newer WSL status across async saved-host reads
* Fence stopped probes when a newer WSL Ready arrives
* Keep saved WSL host selection covered when admission is off
* Check WSL probe ownership after async admission
* Preserve WSL stop authority without cancelling Ready persistence
* Prune removed WSL E2E real-time wait from flaky-test baseline
* Limit WSL callback invalidation to confirmed stops
* Retire pending WSL notices on every confirmed stop
* Close the WSL picker dialog explicitly between scenarios
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* Keep quit teardown within the source line budget
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <alpha-eng@stably.ai>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* feat(plugins): check host API calls against released Orca at validation
orca plugin validate and pnpm validate:plugin now read the literal host
method names a plugin's worker, panel and editor code calls, and report
methods this Orca does not have, proposed methods, wrong-surface calls,
and methods newer than engines.orca (unless guarded by orca.host.has).
Deprecated methods warn with a stable 'deprecated host method <name>'
prefix. Adds the Host API minor to first-Orca-release table.
* fix(plugins): avoid host-call validation false positives
Guarded proposed and wrong-surface calls warn instead of failing, and an orca.api.minor comparison counts as a floor guard. Only host.call/has receivers count, comments are stripped, files are stat-capped and read through their real path inside the plugin, root-relative script sources resolve, and each file is read once.
* fix(plugins): keep has-guarded host calls as errors before orca.host.has existed
* fix(plugins): fail only certain host-call problems and bound the scan
Floor and wrong-surface findings are warnings, since guards and per-surface reachability are not visible to a text scan; unknown and proposed methods without a literal has guard stay errors. Read attempts, references per file and queued files are capped, has?.() counts as a guard, and HTML script and comment scanning is linear.
* fix(plugins): treat any orca.host.has call as feature detection for unknown methods
* build(cli): ship the host-call validation module with the packaged CLI
* refactor(backend): extract live core startup modules
* refactor(backend): import orcad profile startup directly
* refactor(backend): address review — keep smoke load check covering activation, drop thin wrappers and import-graph test
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <alpha-eng@stably.ai>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test(computer): run the Linux bridge against an unreachable accessibility bus
* fix(computer): report an unreachable AT-SPI bus instead of aborting the Linux bridge
* test(computer): read the bridge response past the registry banner
* test(computer): keep the healthy-bus check off the desktop's X display
* perf(layout): skip unused normalization reports in pane commands (#42615)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Clarify cleanup pinning and ignored-file protection (#42616)
* test: remove 55 low-value suites and assertion driver (#42605)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* fix(skills): skip Claude sync scratch folders during skill discovery (#42610)
Claude Code parks replaced skill copies in `.trash` and in-progress syncs
in `.staging` under its skills roots. Discovery walked into both, so each
synced skill showed up as duplicates. Prune those directory names in the
native file walk and in the generated WSL `find` command.
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
* test: remove 78 low-value suites and trim redundant cases (#42621)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
* test: remove 53 low-value suites and trim redundant cases
---------
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Co-authored-by: BingZ <zzb@gxsmjx.com>
Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
Ports the edge halves of two release-branch changes onto main, which production
edge deploys come from (prod edge = ba3f991):
- Ingress mode (#41986): signed ingress header (INGRESS_SECRETS) and token mode
for a cloud load balancer (INGRESS_TOKENS secret, INGRESS_ORIGINS,
INGRESS_SOURCE_CIDRS). All or nothing: a partial or malformed setup turns the
mode off and logs relay_edge_ingress_config_invalid; it never throws. Requests
from the configured egress ranges that fail the trust rule get 403. Admin calls
are matched first. Adds cloud/apps/relay-ingress (stateless proxy) and the
relay-contract ingress-header module.
- POST /__admin/verify (#42538, edge half): the director's check for a phone
resume token or invite that exists only on the edge. Hash only, read-only: an
object that never held the host (or no longer holds it here) answers not_here
before anything is written; otherwise the token's jti is its only write.
Replay and jti_full are 409. Adds hash-input variants to RelayCredentialStore
(shared with the edge; existing methods delegate, behaviour unchanged).
Kept from main: drain, single-use admin tokens (jti), signing-key rotation,
JWKS-outage tolerance, keepalive auto-response, health probe. The place label
keeps main's '<continent>/<colo>' and, only behind a verified ingress, appends
'/<country>/<ingress name>'.
No user effect until the ingress vars/secret are set or the director calls verify.
* feat(mobile): ship Android as dev.orca.app and check updates by install source
Android becomes dev.orca.app, the package already live on Google Play; iOS keeps
com.stably.orca.mobile. The move screens and the "Orca (old)" label stay keyed to the old package,
so they never show in the new app.
The app asks Android who installed it. A Play install gets its updates from Play, so it runs no
GitHub check, hides "Check for updates" and points the update wall at Google Play. Any other
install checks GitHub for android-v releases; the old package keeps mobile-android-v.
* ci(mobile): release dev.orca.app to Play and publish Google's signed APK
An android-v tag (or a manual run) builds the AAB with the upload key and sends it to Play's
internal track. It then downloads the universal APK Google signed for that versionCode, fails unless
its V3.0 signer is Google's app signing key, and publishes it as the android-v GitHub pre-release.
Play and GitHub installs are the same signed app. A manual run with publish_github_release off only
validates the bundle with Play.
The orca.dev APK bump job is gone: the site builds its link from mobile-android-v, so it stays on
the last old-app APK, which sends people to the new app.
* Remove finished-agent retention and keep sleeping status with panes
* Fix legacy pane projection and sleeping-agent regression fixtures
* Cover sleeping display-only status in parked terminal coverage
* Keep pane conversation identity only across continuous agent observations
* Remove duplicate import and keep sleep fixtures type checked
* Preserve conversation boundaries across replays and inherited clocks
* Cover conversation map stability across a large status batch
* Bound conversation capacity work to changed pane owners
* Pass capacity classifiers their layout input directly
* Finalize conversation provenance once per status batch
* Keep paired snapshot tests focused on observable outcomes
* Type the conversation provenance test fixtures explicitly
* Consolidate agent session imports after main merge
* Preserve provider replacement evidence when resetting conversation continuity
* Separate retention deletion from sleeping agent display
* Restore migration row bucket comparison
* Skip unusable pane identities before title ownership lookups
* Refresh conversation titles when their owning pane changes
* Update completion test sound mock after module move
* Update imports for main module moves
* Remove an unreachable native chat owner comparison
The E2E agent guide linked the terminal layout parity runner and the
workspace layout checker at their old config/scripts locations, so the
link was broken and the inspection command failed with MODULE_NOT_FOUND.
Point both at their current locations and update the checker's own
usage comment to match.
Fixes#42426
Co-authored-by: Neil <neil@stably.ai>