chore: update vendored Effect source

[pullfrog]

Updates vendored Effect source at repos/effect/ to match upstream Effect-TS/effect main branch.

64 files changed, 9059 insertions, 5672 deletions.

This is a read-only vendored reference — no code outside repos/effect/ is modified.

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using Big Pickle (free) ｜ 𝕏}

[pullfrog]

Diagnosis: CI failure is pre-existing and unrelated to this PR. The Build step fails because elm-pages build in apps/docs tries to fetch lamdera/codecs/1.0.0/elm.json from static.lamdera.com and gets a ResponseTimeout — the Lamdera package registry is unreachable from this CI runner. No files were changed by this PR (diff is empty after the vendored source sync to main), so no fix is applicable here.

Task list (4/7 completed)

• Checkout PR branch
• Fetch check suite logs to diagnose failure
• Verify failure was introduced by this PR
• Diagnose and fix the issue
• Verify fix with pnpm test and pnpm lint
• Commit and push changes
• Report progress

  ^{｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[pullfrog]

No upstream changes since last sync — the vendored Effect source is already current. Closing without action.

  ^{｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[pullfrog]

CI failure diagnosis

The failing step is packages/devtools-ui build (Elm UI build), which errors with:

-- PROBLEM BUILDING DEPENDENCIES -----------------------------------------------
I ran into a compilation error when trying to build the following package:
    elm/core 1.0.5

This is unrelated to the vendored Effect update in this PR — the PR only touches files under repos/effect/. The packages/devtools-ui/ directory has zero changes.

I verified the devtools-ui build passes locally:

Starting downloads...
  ● elm/core 1.0.5
  ...
Dependencies ready!
Success! Compiled 13 modules.
devtools-ui build complete.

The CI failure was a transient download/compilation error for elm/core 1.0.5 from the Elm package registry. This is a CI environment flake, not a code issue.

Recommended action: Re-run the CI workflow (no code changes needed).

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using Big Pickle (free) ｜ 𝕏}