chore(refs): sync Effect reference to rc.112#10653

merged1
t3code/bump-effect-alchemy
t3code/bump-effect-reference
openedSep 8, 2026byJJulius Marminge
View on GitHubTwo-way sync enabledPR last imported 4d ago

Refreshes .repos/effect-smol to the exact effect@4.0.0-rc.112 release, matching the dependency upgrade below this PR. This layer contains only upstream reference files.

The subtree sync helper could not find historical subtree metadata after earlier squashed merges. Imported the tagged Git tree directly and verified that the resulting directory tree hash equals upstream 2600f62. No hand edits or runtime imports from the reference repository.

Model: GPT-6. Harness: Codex.

Note

Sync Effect reference to rc.112 with new doctest, api-diff, and platform-deno packages

  • Adds the @effect/doctest package for extracting and running inline documentation tests, the @effect/api-diff CLI tool for comparing TypeScript APIs across Git refs, and the @effect/platform-deno package providing Deno-native platform services (crypto, filesystem, path, socket server, terminal, worker, stdio)
  • Migrates error schema classes from Schema.ErrorClass/Schema.TaggedErrorClass to Schema.Error/Schema.TaggedError across worker, socket, terminal, HTTP, and Redis modules
  • Restructures platform packages from platform-node/platform-browser/platform-bun to platform/node/platform/browser/platform/bun directory layout and updates workspace, tsconfig, and Deno references accordingly
  • Fixes core runtime bugs: RcRef.getState now rechecks state after serialization and closes the temporary scope on failure; ScopedRef.set closes the new scope when the old scope close fails; SynchronizedRef.getAndUpdateSome targets the backing Ref; Scheduler.MixedScheduler uses a cancellable microtask in sync mode; Schema.makeEffect no longer wraps parser failures through a removed conversion
  • Hardens HTTP modules: cookie validation with dedicated syntax rules, HttpBody.file/fileFromInfo report partial-range content length, HttpServerResponse explicit headers override body-derived headers, HttpClientResponse.schemaJson accepts JSON reviver options, and a new MultipartParser public API replaces the Multipasta re-export
  • Improves SQL clients: SQLite Node/Bun clients add configurable busyTimeout (default 5s) and BEGIN IMMEDIATE; MSSQL defaults to encrypted connections with certificate validation; ClickHouse client is scope-managed and classifies JSON parse failures as SqlError
  • Fixes ResourceRef to preserve acquisition failure causes so later await calls fail instead of hanging; OtlpMetrics snapshots now use per-snapshot candidate state and commit only newer sequences
  • Risk: Toolkit.WithHandler handlers now receive encoded tool parameters (Tool.ParametersEncoded) instead of decoded parameters — existing handler implementations need updating. Internal schema report API and SchemaError namespace export are removed from effect/src/index.ts. Several packages block the ./index subpath export. Platform package paths changed; out-of-tree consumers referencing old paths need updating.

Macroscope summarized 98eb810.

Synced from GitHub

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ No successful main baseline artifact is available yet. This run establishes the initial measurement.

ProviderMetricMain baselineThis PRImpactPR ceiling
CodexTotal thread wire—13.6 KiB—15.1 KiB✅
CodexThread snapshot wire—7.0 KiB—7.3 KiB✅
CodexLive turn WebSocket wire—6.6 KiB—7.8 KiB✅
CodexLive turn WebSocket decoded—57.1 KiB—66.4 KiB✅
CodexLive turn messages—10—21✅
ClaudeTotal thread wire—13.6 KiB—15.1 KiB✅
ClaudeThread snapshot wire—7.0 KiB—7.3 KiB✅
ClaudeLive turn WebSocket wire—6.6 KiB—7.8 KiB✅
ClaudeLive turn WebSocket decoded—57.9 KiB—66.4 KiB✅
ClaudeLive turn messages—10—21✅

Baseline: unavailable · PR result: 98eb810 · Source CI: success

Scenario and decoded snapshot size

10 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.

  • Codex decoded thread snapshot: 113.9 KiB
  • Claude decoded thread snapshot: 114.6 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

Synced from GitHub

Macroscope skipped reviewing this pull request. Per-review cost limit exceeded (workspace setting).

This review would cost an estimated $163.72, which exceeds your per-review limit of $8.00.

The top 3 files driving up this estimate:

FileDiff SizeEstimate
.repos/effect-smol/packages/effect/src/Graph.ts292.23KB$14.61
.repos/effect-smol/packages/effect/src/Schema.ts192.48KB$9.62
.repos/effect-smol/packages/effect/src/unstable/encoding/SchemaBinary.ts174.36KB$8.72

Tip

To get this pull request reviewed, you can:

  1. Comment @macroscope-app on this PR to request a manual review (monthly spend limits still apply).
  2. Exclude the file(s) above from review by adding a pattern to your .macroscope/ignore.md — note that creating this file replaces Macroscope's built-in default ignores rather than extending them.
  3. Raise your cost limit in your workspace billing settings.

Turn off this reminder going forward

Synced from GitHub

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The changes are confined to the vendored Effect reference and do not enter t3code’s production workspace, but the sync adds language-service diagnostic suppressions for several static-analysis checks. Those configuration-level overrides require human review.

Not approved because:

  • Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

No code changes detected at 98eb810. Prior analysis still applies.

Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.

Added 1 commit

  • chore(refs): sync Effect reference to rc.11298eb810
Synced from GitHub

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.