build(deps-dev): bump @effect/tsgo from 0.41.0 to 0.45.0

docs/effect-conventions.md

@@ -853,5 +853,5 @@ soon as the trigger fires and retire the row.
 | Recorded | Pin (where) | Observed registry state | Trigger / action |
 | --- | --- | --- | --- |
 | 2026-09-03 | `effect-rstest` **pkg.pr.new preview `e5f8d5f`** (`https://pkg.pr.new/ScriptedAlchemy/effect-rstest@e5f8d5f`), `packages/agent-bundle`, `packages/rsc-runtime`, `packages/create-agent-bundle` devDependencies (three pins). Needs a real release pin once published. | `npm view effect-rstest versions`: **E404, not published to npm** (no versions, no dist-tags). | First npm publish of `effect-rstest`. Replace all three preview URLs with the exact published version, refresh `pnpm-lock.yaml`, re-run `pnpm test:unit` (`it.effect` / `it.live` suites). |
-| 2026-09-03 | `effect` **`4.0.0-rc.112`** (`packages/agent-bundle`, `packages/rsc-runtime`, `packages/workbench`, `packages/create-agent-bundle`), `@effect/atom-react` `4.0.0-rc.112` (`packages/workbench`), `@effect/platform-node` `4.0.0-rc.112` (`packages/create-agent-bundle`), `@effect/platform-node-shared` `4.0.0-rc.112` (`packages/agent-bundle`), `@effect/language-service` `0.87.2` and `@effect/tsgo` `0.39.0` (root). Auto re-pin in lockstep + `repos/effect` subtree + Workbench atom phase 4 unblock (stream-backed derived atoms) once the post-rc.112 disposal fix ships. | `npm view effect dist-tags`: `rc` **`4.0.0-rc.112`** (unchanged), `beta` `4.0.0-beta.107`, `latest` `3.22.1`. `@effect/atom-react`: `rc` `4.0.0-rc.112`. `@effect/language-service`: `latest` `0.87.2`. `@effect/tsgo`: `latest` `0.39.1` (patch ahead of the `0.39.0` pin; rides the lockstep chore). | `effect@rc` advances past `4.0.0-rc.112`. Run the re-pin chore steps 1–6 above, bumping `effect`, `@effect/atom-react`, `@effect/language-service`, and `@effect/tsgo` together, then lift the stream-backed derived-atom ban in the Workbench if the disposal fix is in the new RC. |
+| 2026-09-03 | `effect` **`4.0.0-rc.112`** (`packages/agent-bundle`, `packages/rsc-runtime`, `packages/workbench`, `packages/create-agent-bundle`), `@effect/atom-react` `4.0.0-rc.112` (`packages/workbench`), `@effect/platform-node` `4.0.0-rc.112` (`packages/create-agent-bundle`), `@effect/platform-node-shared` `4.0.0-rc.112` (`packages/agent-bundle`), `@effect/language-service` `0.87.2` (root). `@effect/tsgo` is not part of this row: it detects the Effect major version rather than pinning an RC, and moves on its own (`0.45.0`, 2026-09-24, #817; `effect-tsgo diagnostics` output identical to `0.41.0` on the root, Workbench, and scaffolder projects). Auto re-pin in lockstep + `repos/effect` subtree + Workbench atom phase 4 unblock (stream-backed derived atoms) once the post-rc.112 disposal fix ships. | `npm view effect dist-tags`: `rc` **`4.0.0-rc.112`** (unchanged), `beta` `4.0.0-beta.107`, `latest` `3.22.1`. `@effect/atom-react`: `rc` `4.0.0-rc.112`. `@effect/language-service`: `latest` `0.87.2`. 2026-09-24: `rc` **`4.0.0-rc.117`**; the trigger has fired but the re-pin is **blocked** (#832): every `effect-rstest` build imports `effect/testing/FastCheck`, removed in rc.113 (Effect-TS/effect#7254, native Arbitraries), so six unit-test files fail to load on any RC after rc.112. | `effect-rstest` ships a build ported to `effect/unstable/arbitrary/Arbitrary` (as upstream `@effect/vitest` did); then run the re-pin chore steps 1–6 above (#832 has steps 1 and 3), bumping `effect`, `@effect/atom-react`, and `@effect/language-service` together, then lift the stream-backed derived-atom ban in the Workbench if the disposal fix is in the new RC. |
 | 2026-09-03 | Agent Plugins specification **`1.0.0`**, `packages/agent-bundle/src/adapters/schemas/portable/{plugin,mcp}.schema.json` + `PROVENANCE.json` (spec repo `agentplugins/agent-plugins-spec` @ `ff8ab5e392cc87bd88d87c060815a87490e51003`, 2026-08-19), portable `adapterRevision` `1.8.0`, pins in `tests/adapter-metadata.test.ts`. Spec watch for #426; not an npm pin, so re-verify with `curl`/`gh api`, not `npm view`. | Live `https://agent-plugins.org/schemas/1.0.0/{plugin,mcp}.schema.json` rehash to the pinned sha256 (1805 / 3408 bytes). Repo `main` HEAD unchanged at the pinned commit; **no tags, no GitHub releases**. `spec/1.1.0.md` is "Status: Working Draft" (started 2026-08-15, `a2afd7ec`); in-repo `schemas/1.1.0/*.schema.json` differ from 1.0.0 only in the `$id`/`const`/`description` version strings; `https://agent-plugins.org/schemas/1.1.0/*.schema.json` → 404. Observed latest published version: **1.0.0**. | `spec/1.1.0.md` (or later) flips to "Published" **and** `agent-plugins.org/schemas/<version>/` serves both schemas. Re-pin under `schemas/portable/` with a dated `PROVENANCE.json` (sha/bytes/date/commit), bump the portable `adapterRevision`, refresh the metadata pins, run `pnpm test:unit` (portable adapter + plugin-validation suites) and `pnpm test:host-install:build`, and add a capability row per additive field. |

package.json

@@ -63,7 +63,7 @@
     "@arethetypeswrong/cli": "0.18.5",
     "@changesets/cli": "3.0.2",
     "@effect/language-service": "0.87.2",
-    "@effect/tsgo": "0.41.0",
+    "@effect/tsgo": "0.45.0",
     "@lydell/node-pty": "1.2.0-beta.15",
     "@modelcontextprotocol/conformance": "0.1.16",
     "@modelcontextprotocol/server": "2.0.0",

pnpm-workspace.yaml

@@ -22,15 +22,6 @@ allowBuilds:
   '@google/genai': false
   msgpackr-extract: false
   protobufjs: false
-minimumReleaseAgeExclude:
-  - '@effect/tsgo-darwin-arm64@0.39.0'
-  - '@effect/tsgo-darwin-x64@0.39.0'
-  - '@effect/tsgo-linux-arm64@0.39.0'
-  - '@effect/tsgo-linux-arm@0.39.0'
-  - '@effect/tsgo-linux-x64@0.39.0'
-  - '@effect/tsgo-win32-arm64@0.39.0'
-  - '@effect/tsgo-win32-x64@0.39.0'
-  - '@effect/tsgo@0.39.0'
 # LocalProvider.init() awaits FlexSearch addAsync so the first search query
 # cannot race the index build (#590; upstream web-infra-dev/rspress#3658).
 # Drop the patch once a release awaits the adds.