Process completed with exit code 1.

Do not use JavaScript switch statements. Use Effect's Match module (Match.value(...).pipe(Match.tag(...), Match.exhaustive)) for type-safe, exhaustive pattern matching.

Do not construct built-in Error objects in Effect domain code. Use typed domain errors and Effect.fail instead; at true adapter boundaries use a narrow suppression with a boundary reason. Skill: wrdn-effect-typed-errors.

Do not collapse Effect failures with die/orDie escape hatches. Keep typed errors in the Effect error channel; at true runtime edges use a narrow boundary suppression. Skill: wrdn-effect-typed-errors.

Do not construct built-in Error objects in Effect domain code. Use typed domain errors and Effect.fail instead; at true adapter boundaries use a narrow suppression with a boundary reason. Skill: wrdn-effect-typed-errors.

Do not collapse Effect failures with die/orDie escape hatches. Keep typed errors in the Effect error channel; at true runtime edges use a narrow boundary suppression. Skill: wrdn-effect-typed-errors.

Avoid primitive casts like value as string. Remove redundant casts, or normalize unknown data with Schema/a typed adapter before use. Skill: wrdn-effect-schema-boundaries.

Avoid double casts through unknown/any; use a typed boundary, schema decode, or a narrow allow comment with a reason. Skill: wrdn-effect-schema-boundaries.

StorageError: Failed query: select "plugin_id", "kind", "name", "url", "can_remove", "can_refresh", "can_edit", "created_at", "updated_at", "row_id", "id", "scope_id" from "source" "source" where ("source"."scope_id" = $1 and "source"."scope_id" in ($2)) params: org_mcp_e2e_4_525e268a,org_mcp_e2e_4_525e268a ❯ fumaFailureFromCause ../../packages/core/sdk/src/fuma-runtime.ts:75:10 ❯ catch ../../packages/core/sdk/src/fuma-runtime.ts:87:23 ❯ catcher ../../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:992:46 ❯ body ../../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/Utils.ts:242:11 ❯ internalCall ../../node_modules/.bun/effect@4.0.0-beta.59/node_modules/effect/src/internal/effect.ts:992:27 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _tag: 'StorageError' } Caused by: Caused by: Error: Failed query: select "plugin_id", "kind", "name", "url", "can_remove", "can_refresh", "can_edit", "created_at", "updated_at", "row_id", "id", "scope_id" from "source" "source" where ("source"."scope_id" = $1 and "source"."scope_id" in ($2)) params: org_mcp_e2e_4_525e268a,org_mcp_e2e_4_525e268a ❯ PostgresJsPreparedQuery.queryWithCache ../../node_modules/.bun/drizzle-orm@0.45.2+5631fa75b35ac506/node_modules/drizzle-orm/pg-core/session.js:41:15 ❯ ../../node_modules/.bun/drizzle-orm@0.45.2+5631fa75b35ac506/node_modules/drizzle-orm/postgres-js/session.js:37:20 ❯ Object.findMany ../../packages/core/fumadb/src/adapters/drizzle/query.ts:306:9 ❯ Object.findMany ../../packages/core/fumadb/src/query/orm/index.ts:400:23 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { query: 'select "plugin_id", "kind", "name", "url", "can_remove", "can_refresh", "can_edit", "created_at", "updated_at", "row_id", "id", "scope_id" from "source" "source" where ("source"."scope_id" = $1 and "source"."scope_id" in ($2))', params: [ 'org_mcp_e2e_4_525e268a', 'org_mcp_e2e_4_525e268a' ] } Caused by: Caused by: Error: read ECONNRESET ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -104, code: 'ECONNRESET', syscall: 'read', query: undefined, parameters: undefined, args: [ 'org_mcp_e2e_4_525e268a', 'org_mcp_e2e_4_525e268a' ], types: null }

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/