Repository navigation
Sync upstream v2 through 56d893c24 while preserving fork contracts - #96
Merged
Merged
Conversation
…-host gate The builder now fetches dependency tarballs and redirect hops with private network access only on the configured registry's origin, so a gate that followed a redirect anywhere could pass an archive the builder refuses. The gate reads dist.tarball, refuses one whose origin differs from EXECUTOR_NPM_REGISTRY, and downloads with manual redirects that must stay on that origin. Its scenarios prove an off-origin tarball URL, a same-origin URL redirecting away, and the existing same-origin pass.
Fork CI ran none of the new contracts that interact with the fork's private registry and operator OAuth. The security-e2e filter now selects the private-fetch egress scenarios and the held-scope and gmail.modify self-host scenarios, and a new step runs the apps SDK release gate's suite against a local registry.
The image runs executor-collector, so the trace sampling section no longer calls the span receiver Motel.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reconcile exactly 69 commits from upstream/v2 through
56d893c24d60e76bc532400c8cfaefc8f70fa41donto fork4f9fce5001e57532a5632af286af9a9d9f3ebf8a(#92 plus #95), with a real two-parent merge (ae24c3e210697543cb299218a3aaa82b485c83cc). Already incorporated upstream:9de0a387a564f625eb454e3ac0281c5822eb0da2. Never upstream/main.Rust collector packaging, safer runtime failure classification, batched discovery, workflow engine-call diagnostics/sleep handling, content-addressed build storage, operator OAuth held scopes, OpenAPI HuJSON/account-schema improvements and dependency egress enforcement. Fork SDK: 0.0.1-beta.141.shuv.1, CLI beta.59. Protocol command: 1–13 unchanged; live 14 recorded, no protocol-list change.
Implementation/PR only: do not merge or deploy automatically. Lead review, private SDK publication, retained-data/exact-image rollback rehearsal and deployment remain separate. Nothing published, deployed or read from production.
Qualification so far
bun install,bun run format,bun run check: PASS; 24 installed patches and exact dependency pins validated.bun run e2e:prepare: PASS. Named plan/fork-CI product selections passed, including final unified discovery (both statement scenarios), dotted search, cold 8,549-tool discovery, key/anti-widening, caller/person-only approval, sharedRuntime, organizations, publishing/pins, CLI/media, feedback, collector and error contracts. Per-command receipts will be appended below before handoff.go test ./..., actionlint and Compose config PASS.a_drain_killed_part_way_finishes_after_a_restart_and_leaves_a_consistent_storewaits for a retention step on every one of six restarts, including after prior steps already finished the drain. Failure recordssteps=0,maintenancePending=false,draining=false, used bytes 1,859,584, already below its 90% low-water bound. The crate is byte-identical to the frozen upstream target. No retry, deadline extension, skip or weakened assertion was applied; retained-data rollback is not claimed qualified by this test.sha256:a7bbe1ea0835839c1397c539ffa50bd3c2761d04946991a0a36ba08e67ac95ab, amd64. Packaged feedback, separate collectors and burst-memory return: 3 passed. Collector app-isolation and compression/streaming: 2 blocked/failing before behavior because app deployment cannot reach the host-gateway synthetic registry. A synthetic HTTP listener answers locally but times out from the same Node Docker image; no firewall/route/config workaround was made. These two behaviors are NOT qualified by the image run.b9b8a5062b05cabf0f587d5ee382d51b226833b9: https://github.com/shuv1337/executor/actions/runs/44081239025 . check 3m10s; security-e2e 6m45s; both Socket checks pass. No CI rerun needed.Unverified: production/private registry availability, live data/account-sharing impact, deployed Cloud, native arm64/macOS/Windows, complete old-image product/telemetry backward-read and rollback. No product/hosted data step is added; detailed impact below.
Fork CI is selected regression coverage, not upstream's full suites or deployment approval. It now explicitly builds/checks/smokes the pinned collector: upstream prepare skips that build in CI expecting an artifact job this fork does not have. Bun remains 1.4.4 and Playwright remains 1.64.1 with its patch.
Frozen upstream reconciliation — November 17, 2026 (PST)
Implementation/PR only. The lead owns review, merge, private SDK distribution, exact-image
rollback rehearsal and deployment. No production, registry, account or network configuration
was accessed or changed by this work.
Identities and boundaries
4f9fce5001e57532a5632af286af9a9d9f3ebf8a(Sync 219 upstream v2 commits through Executor beta.50 #92 plus Support private fork SDK publication without bumping the advertised version #95).9de0a387a564f625eb454e3ac0281c5822eb0da2.56d893c24d60e76bc532400c8cfaefc8f70fa41d, 69 reachable commits.This includes a contributed HuJSON branch merged by an export; “exports” is the task's
shorthand, not a claim that every commit has an Export subject.
from each commit's first-parent diff, including the merge commit, not export labels.
main. The reconciliation uses a real two-parent merge.apps@0.0.1-beta.141.shuv.1. Existing app pins are not rewritten.Support private fork SDK publication without bumping the advertised version #95's private publication tool and fail-closed guard survive; nothing was published.
Additional 28-commit inventory
1d5cd9fac88a106b9704c82fcc1584ac89cad024aa07b772670dd26616d31d8492e3387baac1f734e9a908c50758496da91d244c76894e1b1fda1da02e8c8b7ed736b6c95f8f87c6a90f78160752919a502b7c415293a93ac00d6f4323f0d52cceba64d1f66f9cf2f0d40629b1cbf32186eeb97e96bb91c1ece78469888ebffb3a51bf17afb2114fa2cdf023734e0b76d97757d9d960ed886cbc51bcbc7194ee658397d4634775526256d777251c8593687c392a15cca94353951efffd9761188921267e9091078c9ec62d7c788ed0480d534597c972e9fbc05defd45307d9fc1f8fc4a6b52d6c41056c9e29822b23c0e40e5ea0a29a6175b97e16855000fcb3d798764312ee40be1d7a0ec66f7f0a6b229fc9688956e2bdec9dd1254be126e608c597e83208e12cc0821a7703b23ea1ccd35d06686bec144fddb076608129f664362230c887aa4fac26ae688125ec5f300bb26fda00d81a4e3980b8c5b05110211292d8df5ef6ed52c4834a074ea87c511a630c076d42b4da0433ade160181f047f316e459358ec6161a7560a962e63fbb5ac1df109e54e5bbb55fa9d05f45f1ba7640a41120c3805ec9b5dcfd3aae52f04b09c19a11c22dcd272aff3100cca9584962cefa3ca455a23c775a8d3a2c555f6d14a019ef2ee9fdb8e0b9209ecfcf4416e915d7c4479a29c01f9d5fc6ec4343251fbab2a3469bcb22cacfd5e8c085b5ebe79d1da1d88d2daa20f473726d1a8553d28d9e35b749c6f5dfc56d893c24d60e76bc532400c8cfaefc8f70fa41dPlan gates changed, plainly
The 28 commits are not covered by the original plan's “no SDK source change” or “OAuth
usability refactor only” observations. They require a new immutable SDK version, held-scope
OAuth refusal/renewal evidence, multi-account schema closure checks, dependency-egress
checks and expanded storage/engine-call classification. Repeated sleeps and content-addressed
storage operations are not never-connected app RPC exchanges. No app write or workflow step
whose answer was lost is replayed. #93 is not diagnosed or fixed. The fork retains its 60-second scenario/hook limits rather than upstream's 120 seconds. No test retry,
skip or assertion allowance is added here to make these paths green.
Conflict ledger (all 23 unmerged paths)
apps/hosted/self-host/README.mdapps/hosted/self-host/compose.yamlapps/hosted/self-host/native/main.goapps/hosted/self-host/scripts/package-runtime.tsapps/hosted/server/src/contracts/mcp-connections.tsapps/hosted/server/src/implementation/access.tsapps/hosted/server/src/implementation/mcp-connections.tsapps/hosted/server/src/implementation/mcp.ts{app,access}, account/connection checks and listAccountsEach. Reconcile one upstream searchReads/PrefetchHost snapshot with the fork's batched kept-row facade; misses/refusals use that same snapshot, not another query cache.apps/hosted/server/src/implementation/resource-lifecycle.tsapps/hosted/server/src/implementation/tools.tsbun.locke2e/tests/mcp-connections.spec.tspackages/app-templates/src/implementation/executor-skill-digests.gen.tspackages/apps/package.jsonpackages/mcp/src/implementation/execute.tspackages/sdk/src/contracts/executor.tspackages/sdk/src/implementation/declarations.tspackages/sdk/src/implementation/listings.tspackages/sdk/src/implementation/tool-search-store.tspackages/sdk/src/implementation/tool-search.tspackages/sdk/src/implementation/tools.tspackages/sdk/src/implementation/worker-dependencies.tspackages/sdk/src/implementation/workerd-entry.tsNon-conflicting preservation and fixture reconciliation
#88 resolver, #89 OpenAPI shared closures, #90 awaited feedback receipt/privacy, #91 shared
notifications/cancellation, root-owner multi-org admission, organization-only publishing,
short names, apps call, Playwright patch/Bun 1.4.4, migration mapping and #95 were reviewed
beyond conflict markers. The pending personal-account scenario remains retained and skipped;
neither hosted target is unskipped. No #68/#80/#93 feature work is included.
Native fixtures now require the staged collector executable instead of motel.capnp and find
the process by
--data=<fixture>instead of Motel's workerd directory argument. Native Goshutdown calls the collector supervisor, not the removed Motel supervisor.
The upstream search-statements assertion is tightened from exactly 12 to exactly 10 SQL
statements: the fork already carries access with its app list and does not reread those two
access folds. The original fork warm search still requires four backend operations; its
scenario is retained. Both small/large app counts, forbidden private apps and reconnect
refusals remain asserted. No assertion is relaxed to allow more work or less security.
Migration/data impact and remaining release gates
The full 69-commit range adds no product schema migration and no hosted/Cloud data step.
The sole changed migration file changes a comment from Motel to telemetry collector.
Fork Cloud 14 remains immutable; upstream 14/15/16 stay fork 15/16/17. SDK/product/registry
journals and the pending personal-account decision remain unchanged. Existing installed app
versions, credentials, source pins and app data are not migrated for telemetry.
The Rust collector owns a separate SQLite store, never reads/resets/deletes nested
motel/,and does not import old history. Exact old image + independently preserved old telemetry bytes
are still required to read old traces. Live mounted data, old-reader restoration, existing
personal-account impact, current private builder resolution, exact-image rollback, deployed
Cloud and non-Linux-x64 platforms are not established by fresh fixture tests. These remain
lead-owned release gates, not inferred from PR CI.
Guidance followed
Read charter/lead handoff, AGENTS, CONTEXT, RELEASING, executor-e2e skill, migration numbering,
personal-account decision, approved plan/summary/resolutions/approval/amendment, #92 and fork CI.
Missing public-export engineering notes remain known papercut
pc_dcf8902b5987.Rat-stack pages read:
ratstack://repo/AGENTS.md,ratstack://skills/ship,ratstack://skills/investigate-a-failure,ratstack://skills/add-a-store.Only language-neutral fence/evidence/migration/rollback rules apply; Executor conventions win.
Evidence
Command logs and receipts are copied from
.local/upstream-sync/to/home/shuv/.cache/agent-ws/executor-upstream-sync-20261117/. The final PR and handoff giveexecuted command/scenario receipts, including failures and fixes; an unmatched filter is never
a pass. Real-server diagnostics/results and privacy-safe named evidence are retained outside
the prunable
.local/e2e/; no sessions or product databases are published.Executed command and scenario receipts
Filtered-out cases are not counted. Initial failures and unmatched filters remain explicit.
selection-00
bun run e2e:self-host --test-name 'An exchange with the local app runtime that never connected|A failed exchange with the local app runtime records how far'2 passed (2). Evidence:
selection-00.log.selection-01
bun run e2e:local --test-name 'local logs a restarted app runtime and reports lost calls'1 passed (1). Evidence:
selection-01.log.selection-02
bun run e2e:self-host --test-name 'MCP search reads every app'2 failed (2). INITIAL FAILURE: superseded by additional-00 and final-60s-paths after unified prefetch reconciliation and stricter 10-statement assertion. Evidence:
selection-02.log.selection-03
bun run e2e:local --test-name 'MCP search resolves namespace-relative dotted paths|A broad MCP tool search returns concise pages'2 passed (2). Evidence:
selection-03.log.selection-04
bun run e2e:self-host --test-name 'Cold MCP discovery serves 8549'1 passed (1). Evidence:
selection-04.log.selection-05
bun run e2e:self-host --test-name 'cannot create an all-apps connection|cannot widen a connection or mint'2 passed | 7 skipped (9). Evidence:
selection-05.log.selection-06
bun run e2e:self-host --test-name 'Members create, list, update and revoke their own scoped connection|a connection key minted by its connection'2 passed | 9 skipped (11). Evidence:
selection-06.log.selection-07
bun run e2e:self-host --test-name 'apps see each MCP user|a tool that requires a person refuses'2 passed (2). Evidence:
selection-07.log.selection-08
bun run e2e:self-host --test-name 'callers of an app that declares sharedRuntime|an app that does not declare sharedRuntime keeps a runtime for each account selection'2 passed (2). Evidence:
selection-08.log.selection-09
bun run e2e:self-host --test-name 'Group resource grants and account connections cannot cross organizations|only an owner of the self-host root organization creates organizations'2 passed | 3 skipped (5). Evidence:
selection-09.log.selection-10
bun run e2e:self-host --test-name 'a self-host with several organizations signs in|a self-host upgraded with several organizations and no root record'2 passed | 1 skipped (3). Evidence:
selection-10.log.selection-11
bun run e2e:self-host --test-name 'an account linked for everyone is named on the app|a member sees the App accounts greyed out'2 passed | 3 skipped (5). Evidence:
selection-11.log.selection-12
bun run e2e:self-host --test-name 'App builds retain their selected npm framework across rebuilds|Existing apps are pinned to an explicit apps framework by a data step'2 passed | 2 skipped (4). Evidence:
selection-12.log.selection-13
bun run e2e:self-host --test-name 'a rejected legacy registry upgrade preserves the old SDK|Publishing dialog explains readiness'2 passed (2). Evidence:
selection-13.log.selection-14
bun run e2e:self-host --test-name 'Builds refuse an app'1 passed | 1 skipped (2). Evidence:
selection-14.log.selection-15
bun run e2e:local --test-name 'apps CLI deploy reports a file over the compile limit'1 passed | 1 skipped (2). Evidence:
selection-15.log.selection-16
bun run e2e:self-host --test-name 'MCP call and execute return app images, audio and files'1 passed | 3 skipped (4). Evidence:
selection-16.log.selection-17
bun run e2e:local --test-name 'the CLI.s tool commands call the host.s MCP tools'1 passed | 3 skipped (4). Evidence:
selection-17.log.selection-18
bun run e2e:self-host --test-name 'executor apps call runs an app tool with an API key'1 passed | 1 skipped (2). Evidence:
selection-18.log.selection-19
bun run e2e:self-host --test-name 'a self-host with flat app hosts publishes'1 passed (1). Evidence:
selection-19.log.selection-20
bun run e2e:self-host --test-name 'Pending webhook sources are served first in, first out'1 passed (1). Evidence:
selection-20.log.selection-21
bun run e2e:self-host --test-name 'self-host feedback webhook awaits acceptance|self-host feedback webhook works with analytics disabled'2 passed (2). Evidence:
selection-21.log.selection-22
bun run e2e:self-host --test-name 'A trace the collector answers in part fails|The bundled collector at its size bound'2 passed (2). Evidence:
selection-22.log.selection-23
bun run e2e:local --test-name 'The local collector serves the trace viewer'1 passed (1). Evidence:
selection-23.log.selection-24
bun run e2e:self-host --test-name 'Every error tools/call and tools/run declare|Every error a write reports after its app code received the call'2 passed | 35 skipped (37). Evidence:
selection-24.log.selection-25
bun run e2e:self-host --test-name 'a registration without application_type'1 passed (1). Evidence:
selection-25.log.selection-26
bun run e2e:self-host --test-name 'Team registry publishes, isolates, copies and unpublishes organization-only source|Self-host resolves an older client.s short package name'2 passed (2). Evidence:
selection-26.log.selection-27
bun run e2e:self-host -- --test-name 'application_type|fetch without a User-Agent names Executor|cannot create an all-apps connection|cannot widen a connection or mint|fails to load fails only its own reads'5 passed | 7 skipped (12). Evidence:
selection-27.log.selection-28
bun run e2e:self-host --test-name 'self-host feedback webhook|self-host with DO_NOT_TRACK|self-host analytics pseudonymize|Hosted feedback enforces'5 passed | 4 skipped (9). Evidence:
selection-28.log.selection-29
bun run e2e:pglite6 passed (6). Evidence:
selection-29.log.selection-30
bun run e2e:typecheck-runner15 passed (15). Evidence:
selection-30.log.selection-31
bun run e2e:prepare-cache25 passed (25). Evidence:
selection-31.log.selection-32
bun run e2e:emulator-failures13 passed (13). Evidence:
selection-32.log.selection-33
bun run e2e:dashboard-file-names1 passed (1). Evidence:
selection-33.log.selection-34
bun run e2e:release-archives10 passed (10). Evidence:
selection-34.log.selection-35
bun run e2e:collector-job --testNamePattern 'another target.s collector job does not decide|an earlier attempt.s successful collector job never'2 passed | 16 skipped (18). Evidence:
selection-35.log.selection-36
bun run e2e:prepare-cache --testNamePattern 'a damaged executable is never taken as up to date'1 passed | 24 skipped (25). Evidence:
selection-36.log.selection-37
bun run e2e:lost-connections --testNamePattern 'does not send a written POST again|does not send a GET that changes state again'26 skipped (26). ZERO EXECUTED: NOT A PASS. Frozen-plan names changed upstream; additional-09 executes all 26 current cases. Evidence:
selection-37.log.selection-38
bun run e2e:lost-connections-lifecycle --testNamePattern 'a request lost and sent again in a scenario|the record the scenario before made is on disk'1 failed | 1 skipped (2). INCOMPLETE FILTER: omitted the first ordered lifecycle case; additional-10 runs both current titles and passes. Evidence:
selection-38.log.selection-39
bun run e2e:conflict-markers --testNamePattern 'a conflict left in a tracked file fails'1 passed | 1 skipped (2). Evidence:
selection-39.log.selection-40
bun run e2e:npm-channel --testNamePattern 'a beta publication that moved latest fails at once|a tag naming a newer version fails at once'2 passed | 9 skipped (11). Evidence:
selection-40.log.selection-41
bun run e2e:publish-guard --testNamePattern 'npm.s tag naming a newer release stops the npm step'1 passed | 35 skipped (36). Evidence:
selection-41.log.additional-00
bun run e2e:self-host --test-name 'MCP search reads every app'2 passed (2). Evidence:
additional-00.log.additional-01
bun run e2e:self-host --test-name 'a run.s sleep whose engine call failed|A build whose framework write storage refused'2 passed (2). Evidence:
additional-01.log.additional-02
bun run e2e:self-host --test-name 'Live OpenAPI sends and returns HuJSON|an OpenAPI app whose resources expand into one another, linked through several accounts'2 passed | 10 skipped (12). Evidence:
additional-02.log.additional-03
bun run e2e:self-host --test-name 'Executor for Google is offered|keeps renewing grants that hold a scope it may no longer ask for|keeps no grant holding a scope outside its allowed scopes'3 passed | 15 skipped (18). Evidence:
additional-03.log.additional-04
bun run e2e:self-host --test-name 'with private fetch off, a build|with private fetch on, a build installs tarball|an app page whose srcset holds a long run of commas'5 passed (5). Evidence:
additional-04.log.additional-05
bun run e2e:self-host --test-name 'Cold MCP discovery serves 8549'1 passed (1). Evidence:
additional-05.log.additional-06
bun run e2e:self-host --test-name 'cannot create an all-apps connection|cannot widen a connection or mint|Members create, list, update and revoke their own scoped connection|a connection key minted by its connection|a scoped connection refuses a call after its pinned account is replaced'5 passed | 6 skipped (11). Evidence:
additional-06.log.additional-07
bun run e2e:apps-published --reporter=verbose12 passed (12). Evidence:
additional-07.log.additional-08
bun run e2e:webhook-sweep-waits --reporter=verbose18 passed (18). Evidence:
additional-08.log.additional-09
bun run e2e:lost-connections --reporter=verbose26 passed (26). Evidence:
additional-09.log.additional-10
bun run e2e:lost-connections-lifecycle --testNamePattern 'a request lost in a scenario is saved|the record the scenario before made is on disk' --reporter=verbose2 passed (2). Evidence:
additional-10.log.additional-11
bun run e2e:test-stage-branch --reporter=verbose11 passed (11). Evidence:
additional-11.log.additional-12
bun run e2e:test-stage-unreadable --reporter=verbose18 passed (18). Evidence:
additional-12.log.final-60s-paths
bun run e2e:self-host --test-name 'MCP search reads every app|apps see each MCP user|a tool that requires a person refuses|callers of an app that declares sharedRuntime|an app that does not declare sharedRuntime keeps a runtime for each account selection|a run.s sleep whose engine call failed|A build whose framework write storage refused'8 passed (8). Evidence:
final-60s-paths.log.cloud-selected
bun run e2e:cloud --test-name 'Cloud.s database pool runs a statement whose connection the far end dropped|Cloud.s own Executor for Google registration refuses before Google'2 passed | 26 skipped (28). Evidence:
cloud-selected.log.Fix round 1 — November 17, 2026 (PST)
Head
0784871519f9f76cf1cb4bbe3804a8f7a783982cadds three commits on top ofb9b8a5062b05cabf0f587d5ee382d51b226833b9. No rebase, amend or force-push; merge commitae24c3euntouched.F1 — the private-SDK gate now refuses a tarball the builder would refuse
Commit
ce0d406cf.scripts/releases/apps-self-host.tskeeps every existing check (status, version, integrity, file-by-file comparison) and adds two origin rules againstEXECUTOR_NPM_REGISTRY:dist.tarballmust be on the builder registry's exact origin. Metadata naming another origin fails closed with anAppsReleaseMismatchthat names the registry origin and the tarball URL with its origin.{ redirect: "manual" }and each3xxhop is resolved and checked. A hop whose origin is not the registry's is refused with a message naming both origins, before any connection to it; same-origin hops are followed up to five.fetchno longer follows a redirect past the origin check.Unchanged by design:
packages/sdk/src/implementation/workerd-entry.ts,patches/@cloudflare%2Fworker-bundler@0.2.4.patch,EXECUTOR_APPS_ALLOW_PRIVATE_FETCHand every network policy. Only this gate script and its scenario file changed.Commit
ce0d406cfalso adds one scenario toe2e/tests/apps-published.spec.ts, extending the existing synthetic registry harness with an advertised off-origindist.tarball, a same-origin URL that answers302to another origin, and anotherOrigincounter server:self-host gate refuses an SDK tarball or redirect on another origin: both topologies exit 1 withoutside the builder registry's origin, the message names the registry origin and the other origin, and the other origin received zero requests; the same registry serving its own archive with matching bytes still exits 0 withBuilder registry serves matching apps@.Planted-bug check: with the gate script reverted to
b9b8a5062, the new scenario fails (expected 1, received 0); restored, it passes. Receipt:fix-r1/apps-published-gate-planted-bug.log.F3 — fork CI guards the new contracts
Commit
ab5f26631..github/workflows/fork-ci.ymlsecurity-e2e:--test-namefilter addswith private fetch off, a build,App dependency registry,keeps renewing grants that hold a scopeandown Google client still signs in gmail.modify. Each alternative was checked againste2e/test-plan.ts: 3, 0, 1 and 1 scheduled self-host scenarios. The suite label matches no scheduled title —e2e/run.tsfilters on scenario titles, not suite names — so theApp dependency registrysuite's only scenario is selected by thewith private fetch off, a buildprefix; the workflow says so beside the step.SDK release gate scenariosstep runsbun run apps:buildandbun run e2e:apps-published -- --testNamePattern 'self-host gate'. The gate suite is its owne2e/apps-published.config.tssuite and never runs undere2e:self-host; plain--test-nameis not a vitest 5 flag, so the step uses--testNamePattern.actionlint .github/workflows/fork-ci.yml: PASS.F6 — self-host README
Commit
078487151.apps/hosted/self-host/README.mdtrace sampling now says "the telemetry collector" at both former "Motel" sites (the image runsexecutor-collector). The remaining "Motel" at:262is deliberately kept: it names the old pre-cutover store that cannot read the new Rust traces.Checks and scenarios run
All logs are in
/home/shuv/.cache/agent-ws/executor-upstream-sync-20261117/fix-r1/. Node 24.22.2 / npm 11.19.1 (CI's major), Bun 1.4.4.bun run formatbun run checkcheck.logactionlint .github/workflows/fork-ci.ymlbun run e2e:apps-published -- --testNamePattern 'self-host gate'bun run e2e:self-host -- --test-name 'with private fetch off, a build installs from a private registry'No full suite, no Docker image scenario (host-gateway remains broken here), no merge, publish, deploy or host/registry/network change.
Note for the runner: this host's default Node 26 / npm 12 returns
npm pack --jsonas an object, which the suite'sPackedschema rejects (SchemaError: Expected array) before any gate code runs; the pinned Node 24 toolchain CI uses returns the array. The suite was therefore run with Node 24.22.2 onPATH.