chore: migrate Effect and Alchemy prerequisite APIs - #788
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
rynfar
marked this pull request as ready for review
September 24, 2026 10:26
rynfar
marked this pull request as draft
September 24, 2026 10:32
rynfar
marked this pull request as ready for review
September 24, 2026 10:44
Collaborator
Author
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.
Pylon's relay Alchemy upgrade requires Effect 4.0.0-rc.115. This moves the pinned Effect catalog from rc.112 to rc.115 and Alchemy from beta.76 to beta.79, adapts Pylon's CLI, configuration, socket, MIME, provider, and relay deployment APIs, and synchronizes the exact upstream reference tags in a separate commit. It is a prerequisite for the remaining relay portion of upstream #268; this PR does not claim that whole upstream dependency bundle is adopted.
The device hub WebSocket proxy now pumps rc.115 reader batches to scoped writers in both directions. A focused regression sends frames each way, closes one reader, and verifies both readers and writers are released. OpenCode environment parsing retains the prior exact accepted boolean literals; text generation exports strict JSON Schema under rc.115 so provider tool schemas keep rejecting excess properties. Relay deployment retains explicit apply confirmation and provides Alchemy's noninteractive internal prompt layer. No relay deployment was run.
This branch also merges the exact reviewed head of #746, which supplies Pylon’s OpenTelemetry export kill switch. Effect rc.112 exposes
Config.stringand rc.115 exposesConfig.String, so #746 can land independently first; this branch adapts its shared OTel reader for rc.115 while retaining Pylon’spylon-serverservice name. The dependency merge passed two independent reviews. Its six focused OTel test files passed 87 tests, server/shared/desktop typechecks and scoped lint/format passed, and the frozen lock install succeeded. No live collector or WSL startup was run.The rc.115 parser stopped honoring schema-local
parseOptions, which made Pylon’s explicitly strict private provider payloads and wire contracts silently strip unknown keys. A minimal pinned Effect patch restores the exact rc.112 annotation precedence; it leaves unannotated external payloads permissive. The regression tests cover direct and nested checked union/array schemas, encoding, and the rc.112 behavior when an annotation precedes or follows a check. Native compaction also exposed a deferred adapter event-worker startup race: a synchronous completion receipt could be published before the worker consumed it. Starting the scoped worker immediately preserves the original compaction recovery assertion atProviderService.test.ts:7411without a clock advance; the separate test near line 1393 does use TestClock.Final CI-fix validation: six focused files passed 470 tests; server and contracts typechecks, scoped lint/format, and a frozen install using the updated patch hash passed. The parser patch was verified in the installed rc.115 runtime and against rc.112 behavior. Both independent reviewers passed the strictness fix at 09db33c; two reviewers also passed the final #746 compatibility merge at 5af5d2f. All expected CI checks passed on that final head.
Validation: affected server, contracts, shared, SSH, ACP, relay, desktop, web, mobile, and scripts typechecks passed. Focused tests passed in transport/MCP/HTTP/shared (74), CLI/lifecycle/relay/build (305, one skipped), provider/SSH (71), Git/source-control/shared/release scripts (284), and the new socket lifecycle regression (9 DeviceHubProxy tests). Scoped lint passed; relay deploy
--helpparsed without planning/applying. Independent reviews covered core transport/lifecycle and CLI/provider/Alchemy; both passed final head. No live relay apply, real device WebSocket, or full Electron runtime launch was performed.Reference provenance:
effect@4.0.0-rc.115dereferences to4a05d4914fa2327a42bd75fe77c22c188becf3b4; Alchemyv2.0.0-beta.79to473c39591c7993a708199d0ef8f0d38416885dde. Each committed.repossubtree matches its exact task-local tag checkout byte for byte excluding.git. The repository subtree helper could not pull because inherited cherry-picked.reposhistory lacks git-subtree ancestry, so the exact local tag trees were synchronized directly. The separate reference commit is large and contains no hand-edited source.git diff --checkreports only a required single-space blank context line in the pinned Effect unified patch; the patch and lockfile hash remain intact.Reconciled with current
pylonat5befa0f1b2: preserved the current review ledger, newer Electron/Claude/mobile dependency pins, Pylon provider event-worker startup, and the OTel kill switch while retaining Effect rc.115/Alchemy beta.79. The frozen lockfile was regenerated and all ten affected package typechecks passed. Changed-scope lint/format and a code-only diff check passed; both pinned reference trees still match the prior reviewed head byte for byte. Eleven affected test files ran with 482 passing and one router fallback-snapshot test failing in the parallel run; the exact test passed alone, and its full 203-test router file passed alone. Four cross-feature suites (Grok limits, ingestion, title regeneration, title migration) passed 163 tests. Exact-head CI is pending; this note does not claim the parallel test failure is fully explained.Implemented with GPT-6 Sol in the Codex harness.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.