[adelrodriguez]

Summary

Stacked on #79.

• Update adamantite 0.43.0 → 0.44.0. adamantite update moves the tools it manages: knip 6.42.0, oxfmt 0.73.0, oxlint 1.88.0, oxlint-tsgolint 7.0.2004, @effect/tsgo 0.54.0.
• Update effect, @effect/platform-node and @effect/platform-node-shared 4.0.0 → 4.0.5. @effect/platform-node-shared stays pinned in dependencies. Adamantite 0.44.0 pins the same three packages at 4.0.5, so the lockfile has one version of each.
• Add the unstable modules that Packref uses on purpose to allowedUnstableApis in tsconfig.json: @effect/platform-node, effect/FileSystem, effect/Path, effect/PlatformError and effect/Terminal. The Adamantite 0.44.0 changelog recommends this for Effect 4.0.2 and later.
• Rename the name payload field to packageName in PackageNotReferencedError, PackageNotFoundError, PackageVersionNotFoundError, StoreSourceMismatchError and RepositoryDirectoryConflictError. The new error-payload-shadows-name rule found this: the field replaced the error's own name, so logs showed the package name instead of the error type. The CLI messages do not change.
• Run packref sync: the dependency-tracked effect and adamantite references move to 4.0.5 and 0.44.0.
• pnpm added minimumReleaseAgeExclude entries for @effect/tsgo 0.54.0, which was published today. You can remove them after 2026-10-20.

Verification

• pnpm run check
• pnpm run analyze
• pnpm run test: 295 passed, 2 skipped
• pnpm run build:verify: npm and pnpm consumer installs pass
• pnpm why: one version each of effect and @effect/platform-node-shared

🤖 Generated with Claude Code

---

Note

Low Risk
Mostly dependency and tooling version bumps plus a non-breaking error payload rename; runtime behavior changes are limited to how errors identify themselves in logs.

Overview
Bumps Effect (effect, @effect/platform-node, @effect/platform-node-shared) to 4.0.5 and adamantite to 0.44.0, with matching dev-tool updates (@effect/tsgo, knip, oxfmt, oxlint, etc.) and lockfile refresh. A patch changeset calls out the Effect upgrade and improved error logging.

Renames the name payload field to packageName on several tagged errors (PackageNotReferencedError, PackageNotFoundError, PackageVersionNotFoundError, StoreSourceMismatchError, RepositoryDirectoryConflictError) and updates constructors in references/npm code so the field no longer shadows Error.name—user-facing messages stay the same, but logs should show the error type.

Expands allowedUnstableApis in tsconfig.json for the Effect language service (platform-node, FileSystem, Path, PlatformError, Terminal). Adds minimumReleaseAgeExclude entries in pnpm-workspace.yaml for newly published @effect/tsgo 0.54.0 platform packages.

^{Reviewed by Cursor Bugbot for commit d4ee6cd. Configure here.}

[pullfrog]

✅ No new issues found.

Reviewed changes Reviewed all 11 changed files, the affected error constructors, and the dependency versions.

• Effect runtime: Updates all three runtime packages to 4.0.5 and keeps the direct @effect/platform-node-shared pin aligned.
• Managed tools: Updates Adamantite to 0.44.0, updates its managed tools and lockfile, and adds version-specific release-age exclusions for @effect/tsgo.
• Error payloads: Renames the package field to packageName in five error classes and their constructors, which preserves Error.name without changing the package messages.
• Configuration and release: Permits the intentional unstable Effect APIs and adds a patch changeset.

Validation passed: frozen dependency install, check, analyze, compiler type check, 295 unit tests, 3 integration tests, and build:verify with fresh npm and pnpm consumer installs. Two unit tests were skipped. Direct assertions also confirmed the names and package messages for all five changed error classes.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}