fix(cli): pin the shared Effect runtime for npm installs - #508
Conversation
(cherry picked from commit 5eecc24a10013be14e496b485f8d1d9491c75f6a)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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. |
|
Independent review of head 259b25a found no blocking issue: the direct shared-runtime dependency matches the existing Effect rc.112 catalog and lock resolution; the unused-dependency exception is limited to the standalone CLI runtime pin. Packaging tests and final-head CI are green. Landing under the standing upstream-cycle approval. |
The server manifest now declares the shared Effect Node runtime directly, keeping standalone npm dependency resolution on the same pinned rc.112 version as the platform packages. Pylon’s bundled desktop server continues to inline this dependency under the existing package-boundary rules.
Cycle #497, frozen range
6c583620ff7ad3235b135af7107c0543467eecfa..4a4c6dd2adc350a68ba18bb28b24b5a7e4660dab. Adopted5eecc24a10013be14e496b485f8d1d9491c75f6a; retained Pylon’s Effect patch and lockfile graph. Added the documented dependency-usage exception for the deliberate runtime pin.Validation: frozen-lockfile install; server-scoped dependency knip; focused CLI packaging-boundary tests; formatting/diff checks. No version upgrade, publication, or deployment performed.
Implemented with GPT-6 in Codex.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.