effect-app 4.0.0-beta.25 → 4.0.0-beta.250

package/CHANGELOG.md

@@ -1,5 +1,1136 @@
 # @effect-app/prelude
 
+## 4.0.0-beta.250
+
+### Patch Changes
+
+- 3053760: fix: restore context map container behavior
+
+## 4.0.0-beta.249
+
+### Minor Changes
+
+- ba789a2: Move core service contracts and runtime-agnostic modules into `effect-app`, keep `infra` and `vue` focused on adapters, and drop the temporary `infra` compatibility re-export paths in favor of the new canonical imports.
+
+  `@effect-app/infra` no longer re-exports moved core modules such as `./Model`, `./Emailer/service`, `./QueueMaker/service`, `./Store/service`, `./adapters/*`, or `./api/*` entrypoints.
+
+## 4.0.0-beta.248
+
+### Patch Changes
+
+- 2a86a17: improve tsgo compat: avoid deferred `Schema.Type`/`Codec.Encoded`/`Codec.DecodingServices`/`Codec.EncodingServices` conditional helpers in generic positions where the type parameter is already constrained to `Schema.Top`. Index the property directly (`X["Type"]`, `X["Encoded"]`, `X["DecodingServices"]`, …) so tsgo doesn't leak `unknown` into `Effect` channels (notably `R`).
+
+  Sites: `client/clientFor.ts` (`RequestHandlerFor`, `FinalTypeOf`, `ExtractResponse`, `ExtractEResponse`), `client/makeClient.ts` (`InputFromPayload`, `OutputFromSuccess`, `InvalidationConfigForCommand`, `TaggedRequestWithMeta` overloads), `rpc/MiddlewareMaker.ts` (`Errors`), `rpc/RpcMiddleware.ts` (`Failure`, `FailureContext`), `Schema/ext.ts` (`ReadonlySetFromArray`, `ReadonlyMapFromArray`), `infra/routing.ts` (`GetSuccessShape`, handlers, route matcher), `vue/makeClient.ts` (`MutationExt.project`, `MutationWithExtensions`, `QueryProjection`), `vue/routeParams.ts` (`parseRouteParams*`).
+
+## 4.0.0-beta.247
+
+### Patch Changes
+
+- 01bab22: Work around tsgo failing to reduce `S.Codec.DecodingServices<X>` (`X extends Top ? X["DecodingServices"] : never`) in generic positions, which left `unknown` and polluted the `R` channel of client handlers and RPC middleware failure context. Since the schemas involved are already constrained to `S.Top`, read `["DecodingServices"]` directly in `RequestHandlerFor`, `TagClass.FailureContext`, and the Vue `MutationExt` / `QueryProjection` types.
+
+## 4.0.0-beta.246
+
+## 4.0.0-beta.245
+
+## 4.0.0-beta.244
+
+### Patch Changes
+
+- b8b9080: update packages
+
+## 4.0.0-beta.243
+
+## 4.0.0-beta.242
+
+### Patch Changes
+
+- da83c1f: Align `InvalidationEntry` (vue) with `InvalidateQueryInstruction` (effect-app).
+
+  `InvalidateQueryInstruction` is now parametrized over `Filters` / `Options`
+  (defaulting to `Record<string, unknown>` so the core stays framework-agnostic).
+  `@effect-app/vue` exposes `InvalidationEntry` as a narrowed alias substituting
+  `@tanstack/vue-query`'s `InvalidateQueryFilters` and `InvalidateOptions`. Single
+  source of truth for the union shape across both packages.
+
+- 21017d5: `InvalidationSet.add` accepts arrays and is exposed as a static shortcut.
+
+  - Single item: `yield* InvalidationSet.add(UserRsc.GetMe)`
+  - Batch: `yield* InvalidationSet.add([UserRsc.GetMe, ["custom", "key"]])`
+  - Skips the `.use(_ => _.add(...))` boilerplate.
+
+  Existing `InvalidationSet.use(_ => _.add(...))` form still works; the service
+  identity is preserved via `Object.assign` so `Effect.provideService` and
+  `.use` / `.useSync` continue to operate on the same `Context.Reference`.
+
+- 2495ace: `InvalidationSet.add` accepts RPC handler shorthand.
+
+  Server-side handlers may now pass an RPC handler object directly to
+  `InvalidationSet.add`; its query key is derived via `makeQueryKey`. Raw
+  `InvalidationKey` arrays continue to work.
+
+  ```ts
+  // before
+  yield *
+    Invalidation.InvalidationSet.use((_) => _.add(makeQueryKey(UserRsc.GetMe)));
+
+  // after
+  yield * Invalidation.InvalidationSet.use((_) => _.add(UserRsc.GetMe));
+  ```
+
+## 4.0.0-beta.241
+
+### Patch Changes
+
+- b035b1c: Isolate per-call `Effect.provide(layers)` / `Stream.provide(layers)` in the
+  RPC api client factory via `{ local: true }`.
+
+  `layers` here is built per RPC invocation from a caller-supplied
+  `requestLevelLayers` plus a fresh `RequestName` layer. Today both pieces are
+  stateless, so no observable bug — but `Effect.provide(layer)` without
+  `local: true` resolves its `MemoMap` from the ambient fiber context, and on a
+  long-lived runtime (browser app, server fiber) any stateful layer slipped into
+  `requestLevelLayers` by a caller would be memoized and shared across every
+  subsequent RPC call. `{ local: true }` builds the layer fresh per call and
+  skips the ambient MemoMap entirely.
+
+  Also documents the rule in `AGENTS.md` ("Per-request `Effect.provide(layer)`
+  must isolate its MemoMap") so the pattern is enforceable in code review and
+  caught early. Companion to the `provideOnRequestScope` MemoMap fix in
+  `@effect-app/infra`.
+
+## 4.0.0-beta.240
+
+## 4.0.0-beta.239
+
+## 4.0.0-beta.238
+
+## 4.0.0-beta.237
+
+## 4.0.0-beta.236
+
+## 4.0.0-beta.235
+
+### Patch Changes
+
+- ba4bdc3: improve: support .ts extension
+- 6cfd83d: update effect to latest beta
+
+## 4.0.0-beta.234
+
+## 4.0.0-beta.233
+
+### Patch Changes
+
+- 57a1862: Update to effect 4.0.0-beta.67. Switch deps from `pkg.pr.new` snapshot back to npm beta tag.
+
+## 4.0.0-beta.232
+
+### Patch Changes
+
+- 0263827: Fix `Date` / `DateValid` default helpers to pipe from their own schema.
+
+  `withConstructorDefault` and `withDecodingDefaultType` on `DateValid` previously piped from `DateFromString`, dropping the `isDateValid()` check (and, after the recent identifier split, the `DateValid` annotations) from the resulting defaulted schema. Both `Date` and `DateValid` now use `extendM` so the helpers attach to the underlying schema (`DateFromString` / `DateValidFromString`).
+
+- 0263827: Distinguish `Date` and `DateValid` in JSON Schema output.
+
+  - `Date` now emits identifier `DateOrInvalid` with description noting the value may be invalid.
+  - `DateValid` now emits its own annotated string (identifier `Date`) with description stating a valid ISO 8601 date is required.
+
+- 0263827: Update to effect `pkg.pr.new` snapshot at `a42ef66` (4.0.0-beta.66). Remove `Yieldable` and `asEffect()` (service tags are now `Effect` directly).
+
+## 4.0.0-beta.231
+
+### Patch Changes
+
+- 7ca66ce: Update to effect 4.0.0-beta.66. Remove `Yieldable` and `asEffect()` (service tags are now `Effect` directly).
+
+## 4.0.0-beta.230
+
+## 4.0.0-beta.229
+
+## 4.0.0-beta.228
+
+## 4.0.0-beta.227
+
+## 4.0.0-beta.226
+
+## 4.0.0-beta.225
+
+## 4.0.0-beta.224
+
+## 4.0.0-beta.223
+
+## 4.0.0-beta.222
+
+## 4.0.0-beta.221
+
+### Patch Changes
+
+- 439cbeb: Adopt module system from effect-smol: replace barrel imports with specific submodule imports (`import * as X from "effect-app/X"` / `import * as X from "effect/X"`).
+
+## 4.0.0-beta.220
+
+## 4.0.0-beta.219
+
+### Patch Changes
+
+- d738811: remove double prefix
+
+## 4.0.0-beta.218
+
+## 4.0.0-beta.217
+
+### Patch Changes
+
+- 0e824ef: add missing Brand
+
+## 4.0.0-beta.216
+
+## 4.0.0-beta.215
+
+## 4.0.0-beta.214
+
+## 4.0.0-beta.213
+
+## 4.0.0-beta.212
+
+### Patch Changes
+
+- 8792221: Rename `withDefault` schema extensions to `withConstructorDefault` for clarity.
+
+  Document that `.withConstructorDefault` is **construction-only** (applied during `.make(...)` when a field is omitted) and is **not** applied during decode — it cannot be used to JIT-migrate database fields. Per-property JSDoc on every `.withConstructorDefault` / `.withDecodingDefaultType` exposed by `Schema/ext.ts`, `Schema/numbers.ts`, `Schema/moreStrings.ts`, and `ids.ts` so the caveat is visible on hover.
+
+  Re-export `withConstructorDefault`, `withDecodingDefault`, `withDecodingDefaultKey`, `withDecodingDefaultType`, and `withDecodingDefaultTypeKey` from `effect-app/Schema` with explicit JSDoc. `withDecodingDefault*` is discouraged for persisted data: a missing field may be data corruption rather than an old-shape document, and silently substituting a default hides the problem. Prefer an explicit, preferably versioned migration of database data over decode-time fallbacks.
+
+## 4.0.0-beta.211
+
+## 4.0.0-beta.210
+
+## 4.0.0-beta.209
+
+### Patch Changes
+
+- c991be1: update packages
+- 3bae238: Remove lodash type imports from utils.ts, replacing with native TypeScript equivalents.
+
+## 4.0.0-beta.208
+
+## 4.0.0-beta.207
+
+### Patch Changes
+
+- 8fffc3c: cleanup
+
+## 4.0.0-beta.206
+
+### Patch Changes
+
+- 54bfc59: Require middleware to flow through `makeRpcClient` and the live layer through `makeRouter`.
+
+  ### `makeRpcClient(middleware, generalErrors?)`
+
+  Signature drops the `rcs` (request-context map wrapper) parameter. `rcs` was only load-bearing on the type side for `RequestConfig` inference; that information is now derived from `middleware.requestContextMap`. `middleware` is required — the previous "rcs + optional middleware" overload is gone.
+
+  **Migration**:
+
+  ```diff
+  -makeRpcClient(RequestContextMap, undefined, AppMiddleware)
+  +makeRpcClient(AppMiddleware)
+  ```
+
+  For tests/clients without a real middleware, build a minimal stub (`{ requestContextMap, requestContext }`) or pass any value satisfying `ClientMiddleware<RCM>`.
+
+  ### `makeRouter(middlewareLive)`
+
+  `makeRouter()` no longer infers the live middleware layer from `meta.middleware.Default`. The Live layer is now passed explicitly to `makeRouter`, and the request classes only carry the middleware tag (schema-only). This decouples the router from any assumption that the middleware tag exposes a `Default` static.
+
+  **Migration**:
+
+  ```diff
+  -export const { Router, matchAll } = makeRouter()
+  +export const { Router, matchAll } = makeRouter(AppMiddleware.Default)
+  ```
+
+## 4.0.0-beta.205
+
+### Patch Changes
+
+- f313973: fix type make interface
+
+## 4.0.0-beta.204
+
+### Patch Changes
+
+- 0a0030f: fix missing overloads
+
+## 4.0.0-beta.203
+
+### Patch Changes
+
+- 992d9fa: fix more branded types
+
+## 4.0.0-beta.202
+
+### Patch Changes
+
+- 1186b09: improve branded types, keep types through Rebuild
+
+## 4.0.0-beta.201
+
+### Patch Changes
+
+- d67d17a: Source middleware errors exclusively from the rpc middleware tag, and move command/stream invalidation wrap/unwrap entirely into the routing layer (server) and `apiClientFactory` (client). `InvalidationMiddleware` and `InvalidationMiddlewareLive` are removed.
+
+  ### Resource error schemas
+
+  Three sites that used to fold `RequestContextMap[*].error` into a request's own error schema now stop doing so:
+
+  - `makeRpcClient` / `makeRequestClass` — `failureSchema` is just `config.error` (still merged with the optional `generalErrors` parameter, which is the only remaining error mix on both type and runtime levels).
+  - `MiddlewareMaker.rpc()` — `error: options.error` only; the previous union with `rcm.config[*].error` is gone.
+  - Routing and `apiClientFactory.makeRpcGroupFromRequestsAndModuleName` — `Invalidation.makeCommandRpc` is called with `error: resource.error` (no widening with the composite middleware error union).
+
+  Middleware errors reach the client through the rpc's `middlewares[*].error` failure-union channel of `Rpc.exitSchema`, exposed by attaching the middleware tag to the rpc on both sides:
+
+  - **Server**: `makeRouter(middleware)` attaches the live composite tag (existing behavior).
+  - **Client**: new `middleware` option on `ClientForOptions` / `ApiClientFactory.makeFor(layer, { middleware })` attaches the same tag schema-only (no Live invoked). Threaded through `makeRpcGroupFromRequestsAndModuleName` to `RpcGroup.middleware(tag)`. Without it, stream rpcs (whose top-level `errorSchema` is forced to `Never` by effect-rpc) hit `SchemaError: Expected never | { _tag: "error", ... }` decoding middleware-thrown errors that bypass the in-stream `Stream.catch` wrap.
+
+  **Migration**: handlers that yield errors previously sourced from rcm (e.g. `yield* new UnauthorizedError()`) now require those errors to be declared explicitly on the resource — `Req.Query<T>()("...", fields, { success, error: UnauthorizedError })`. The handler error type no longer auto-includes the rcm union.
+
+  ### Invalidation wrap/unwrap
+
+  - `routing.ts` (server) provides a per-request `InvalidationSet` for commands, wraps the success value as `CommandResponseWithMetaData`, and converts handler-thrown failures into `CommandFailureWithMetaData` so accumulated invalidation keys reach the client on either path. Stream wrap (per-chunk envelope + final `done` chunk) was already in routing and is unchanged.
+  - `apiClientFactory.ts` (client) `unwrapCommand` strips both envelopes and forwards keys to `InvalidationKeysFromServer`.
+  - `InvalidationMiddleware` (the tag) and `InvalidationMiddlewareLive` (the layer) are **removed**. The middleware was the previous home of the wrap; with the wrap moved to routing/apiClientFactory, the middleware became a thin pass-through and is no longer needed. `DefaultGenericMiddlewares` and `DefaultGenericMiddlewaresLive` shrink accordingly — no migration needed for callers that used the defaults; callers that referenced `InvalidationMiddleware` / `InvalidationMiddlewareLive` directly should drop those imports.
+
+  Middleware-thrown errors are never wrapped: by definition the handler never ran, so there is nothing to invalidate. They flow raw on the Cause and the client decodes them via the middleware-tag failure-union channel described above.
+
+## 4.0.0-beta.200
+
+### Patch Changes
+
+- 8f1cf6a: able to configure schema concurrency
+- 0cff7c1: workaround middleware error issue
+
+## 4.0.0-beta.199
+
+## 4.0.0-beta.198
+
+### Patch Changes
+
+- 32dbc54: fix stream type when no success specified
+
+## 4.0.0-beta.197
+
+### Minor Changes
+
+- 3dc0d2a: Add streaming as a `stream: true` config option on `Query` / `Command` instead of a separate request type.
+
+  `TaggedRequestFor` now exposes only `Query` and `Command` factories — the standalone `Stream` factory is removed. To produce a Stream of `success` values, pass `stream: true` in the request config. The request `type` field stays `"command" | "query"`; a new `stream: boolean` field carries the streaming flag (stripped from the stored handler config).
+
+  ```ts
+  // Query that streams results
+  Req.Query<T>()("Tag", {}, { stream: true, success: ... })
+
+  // Command that streams results
+  Req.Command<T>()("Tag", {}, { stream: true, success: ... })
+  ```
+
+  Vue client mapping (per-handler properties mirror the non-stream API — `.query`, `.fn`, `.mutate`):
+
+  - `query` + `stream: true` → exposes `.query` (read-only streaming, tracked Vue Query). Helper map key: `${name}Query`.
+  - `command` + `stream: true` → exposes `.fn` and `.mutate` (mutating streaming).
+  - Plain `query` / `command` unchanged.
+
+  Server routing dispatches via the new `stream` flag (`makeStreamRpc` for streaming commands/queries, `makeCommandRpc` / `Rpc.make` otherwise).
+
+  Also lifts the `Struct` / `TaggedStruct` and `Opaque` definitions in `effect-app/Schema` to use `S.Bottom` / `S.Opaque` directly, exposing `fields`, `mapFields`, and a `MakeIn` that allows `void` when all fields are optional. `TaggedRequestFor` request classes now use `Opaque(TaggedStruct(...))` instead of `TaggedClass`, and decoding/encoding services are derived from `success` / `error` rather than stored on the request.
+
+  **Migration**: replace `Req.Stream` with `Req.Query` or `Req.Command` and add `stream: true` to the config — `Query` for read-only streams, `Command` for mutating streams.
+
+## 4.0.0-beta.196
+
+## 4.0.0-beta.195
+
+### Patch Changes
+
+- 774a9b3: `MiddlewareMaker.makeMiddlewareBasic` now derives each middleware's effective error from both the static `error` field on the tag AND the `rcm` config entry referenced by `dynamic.key`, rather than relying on the static field alone.
+
+  Middlewares declared with `dynamic: RequestContextMap.get("foo")` (instead of an explicit static `error: ...`) end up with `tag.error = Schema.Never` at runtime — `RpcMiddleware.Tag` defaults the static error to `Never` when not provided. The composite `MiddlewareMaker.Tag(...).middleware(...)` walked `make[*].error` to build its own error union, collapsing to `Union<Never, ...> ≡ Never`.
+
+  `Rpc.exitSchema` walks `rpc.middlewares[*].error` when building the wire-level failure union for every rpc kind. Empty-union meant middleware-thrown errors (`NotLoggedInError`, `UnauthorizedError`, etc.) never reached the wire schema. Query/command happened to work because their wire `errorSchema = resource.error` already covered the merge from `makeRpcClient`. Stream rpcs have `errorSchema` force-set to `Schema.Never` by effect-rpc, so the resource-level merge never reached the wire — middleware errors decoded as "Expected never, got X".
+
+  Per middleware, the new logic pushes both the static `_.error` (if non-`Never`) and `rcm[_.dynamic.key].error` (if non-`Never`) into the composite's failure union.
+
+## 4.0.0-beta.194
+
+## 4.0.0-beta.193
+
+## 4.0.0-beta.192
+
+## 4.0.0-beta.191
+
+### Patch Changes
+
+- 50ce7e6: Replace typescript-eslint with oxlint-tsgolint for type-aware lint. Drop ESLint entirely from non-vue packages (cli, effect-app, infra) — they now use only `oxlint --type-aware`. Vue packages keep ESLint to run `@effect-app/no-await-effect` (no tsgolint equivalent) via `@typescript-eslint/parser` + `vue-eslint-parser`.
+
+## 4.0.0-beta.190
+
+### Patch Changes
+
+- 985176b: Align request handler input typing with the request's `make` signature. Handlers are now classified as no-input only when the request schema declares no payload fields; any payload (even fully-optional) yields a function handler whose input matches `make`'s first parameter. Adds `HandlerInput<I>` and threads it through `CommandFromRequest`.
+
+## 4.0.0-beta.189
+
+### Patch Changes
+
+- ea32222: Update to effect 4.0.0-beta.60 and use native `Rpc.custom` constructors (`makeCommandRpc`, `makeStreamRpc`) for metadata-wrapped RPC schemas instead of manually wrapping/unwrapping schemas inline.
+
+## 4.0.0-beta.188
+
+### Patch Changes
+
+- b2e438f: Remove Operations service and repo
+
+## 4.0.0-beta.187
+
+### Patch Changes
+
+- 0d4e0b8: Fix `isGeneratorFunction` using `isObject` instead of `isFunction`: generator functions have `typeof === "function"`, not `"object"`, so the check always returned `false`. This caused `Command.streamFn` generator-form handlers to silently pass a raw `Generator` object rather than an `Effect<Stream>`, meaning the mutation was never executed.
+
+## 4.0.0-beta.186
+
+## 4.0.0-beta.185
+
+## 4.0.0-beta.184
+
+## 4.0.0-beta.183
+
+## 4.0.0-beta.182
+
+## 4.0.0-beta.181
+
+### Patch Changes
+
+- 583393f: Default the stream `mutateStream` execute resolved value to the request's success type when no `final` schema is declared.
+
+  Previously the type defaulted to `void`, but the runtime already resolves with the last emitted value. Types now match runtime behaviour: `execute` returns `Final` if a `final` schema is set, otherwise the success type.
+
+## 4.0.0-beta.180
+
+### Minor Changes
+
+- 7fa3045: V1/V2/V3: stream and command requests carry invalidation metadata
+
+  **V1** – stream final response includes metadata
+
+  - `Invalidation.StreamResponseChunk` wraps each stream item as `{ _tag: "value", value }` and appends `{ _tag: "done", metadata }` at the end carrying all accumulated invalidation keys.
+
+  **V2** – invalidation keys included in failures
+
+  - `Invalidation.CommandFailureWithMetaData` and `Invalidation.StreamFailureChunk` carry keys accumulated up to the point of failure, so clients can invalidate queries even when a command or stream errors.
+  - `InvalidationMiddlewareLive` wraps command failures; `routing.ts` wraps stream failures.
+  - `apiClientFactory.ts` unwraps both on the client side, forwarding keys before re-failing with the original error.
+
+  **V3** – mid-stream metadata chunks
+
+  - `Invalidation.StreamResponseChunk` now also includes `{ _tag: "metadata", metadata }` for mid-stream invalidation.
+  - After each emitted value, the server drains accumulated keys and emits a "metadata" chunk if any keys were collected since the last drain (bucket reset via `InvalidationSet.drain`).
+  - `apiClientFactory.ts` processes "metadata" chunks the same as "done" chunks, forwarding keys to `InvalidationKeysFromServer` immediately.
+  - `makeInvalidationKeysService` accepts an optional `onAdded` callback that fires after each key addition, enabling `mutate.ts` to trigger query invalidation mid-stream without waiting for the stream to complete.
+
+## 4.0.0-beta.179
+
+### Minor Changes
+
+- 828d264: Stream requests now support an optional `final` schema that models the final success type of the stream. When declared, `mutateStream`'s execute effect resolves with the last emitted value typed as `Final` instead of `void`.
+
+  ```ts
+  class MyStream extends SomethingStream<MyStream>()(
+    "MyStream",
+    { id: S.String },
+    {
+      success: S.Union([OperationProgress, ExportComplete]),
+      final: ExportComplete, // execute now resolves with ExportComplete
+    }
+  ) {}
+  ```
+
+## 4.0.0-beta.178
+
+## 4.0.0-beta.177
+
+### Minor Changes
+
+- 89d8b3a: Add Effect RPC `Stream` support to the wrapper.
+
+  - New `Stream` request constructor on `TaggedRequestFor` parallel to `Query`/`Command`. Emits resources with `type: "stream"`.
+  - Server router (`@effect-app/infra` `routing.ts`) accepts stream resources whose handlers return a `Stream.Stream<A, E, R>` (or a function from input to one). Forwards `stream: true` to `Rpc.make` so `RpcSchema.Stream` wrapping is applied. Streams bypass `applyRequestTypeInterruptibility` and the `Effect.withSpan` wrapping (the RPC server adds its own span).
+  - Client (`apiClientFactory.ts`) detects stream resources, forwards `stream: true` when constructing `RpcGroup`, and exposes the per-request `handler` as a `Stream.Stream` (via `Stream.unwrap` over the `ManagedRuntime` context) instead of an `Effect`. `Invalidation.CommandResponseWithMetaData` continues to apply only to commands.
+  - New `RequestStreamHandler` / `RequestStreamHandlerWithInput` shapes in `clientFor.ts`; `RequestHandlers` dispatches on `type: "stream"`.
+
+## 4.0.0-beta.176
+
+### Patch Changes
+
+- pass options
+
+## 4.0.0-beta.175
+
+## 4.0.0-beta.174
+
+### Minor Changes
+
+- 821468d: Add server-driven cache invalidation via RPC response headers.
+
+  - `effect-app/rpc`: new `Invalidation` module with `InvalidationKey` / `InvalidationKeys` schemas, `Invalidates` annotation (for declaring static invalidation on Rpc definitions), `InvalidationSet` reference (request-scoped accumulator), and `makeInvalidationSet` helper.
+  - `effect-app/middleware`: new `InvalidationMiddleware` RPC middleware tag; included in `DefaultGenericMiddlewares`.
+  - `effect-app/client`: new `InvalidationKeys` module with `InvalidationKeysFromServer` reference and `makeInvalidationKeysService` helper; `apiClientFactory` now taps HTTP responses to read the `x-invalidate` header and forward keys to `InvalidationKeysFromServer`.
+  - `@effect-app/infra`: new `InvalidationMiddlewareLive` RPC middleware implementation that owns the full lifecycle — creates a request-scoped `InvalidationSet` (backed by a `Ref`), pre-populates it from the `Invalidates` annotation, provides it to the handler, and after the handler completes registers an HTTP pre-response handler (via `appendPreResponseHandlerUnsafe`) to write the accumulated keys as an `x-invalidate` response header. No separate HTTP middleware is needed.
+  - `@effect-app/vue`: `invalidateQueries` / `useMutation` now reads server-provided invalidation keys from `InvalidationKeysFromServer` after each mutation and applies them alongside the client-side invalidation.
+
+## 4.0.0-beta.173
+
+## 4.0.0-beta.172
+
+## 4.0.0-beta.171
+
+### Patch Changes
+
+- d71d976: fix
+
+## 4.0.0-beta.170
+
+### Patch Changes
+
+- 8f09f77: fix
+
+## 4.0.0-beta.169
+
+### Patch Changes
+
+- 8ae8b53: input mess
+
+## 4.0.0-beta.168
+
+### Patch Changes
+
+- 178480a: Fix request handler input classification to use request schema fields instead of `make` parameters, preventing defaulted/nullable input fields from being treated as no-input handlers.
+
+## 4.0.0-beta.167
+
+### Patch Changes
+
+- 140e192: Relax invalidation resource value constraints to allow arbitrary values while preserving query-only filtering in invalidation handling.
+
+## 4.0.0-beta.166
+
+### Patch Changes
+
+- dbcc53b: Refactor command invalidation typing: declare resources via `Command<Self, Resources>()`, pass `invalidatesQueries` as the optional 4th argument, and enforce exact `clientFor` invalidation resources when required.
+
+## 4.0.0-beta.165
+
+### Minor Changes
+
+- f88ea34: Move `makeQueryKey` into `effect-app/client` and update Vue source and tests to import it from the shared client module. Vue still re-exports `makeQueryKey` from `src/lib` for compatibility.
+
+## 4.0.0-beta.164
+
+### Minor Changes
+
+- 8cb3de4: Add command invalidation helpers that preserve query-only resource types and pass mutation input and `Exit` results into invalidation callbacks. Update Vue `clientFor` to merge request-level invalidation config with call-site invalidation and require matching invalidation resources.
+
+## 4.0.0-beta.163
+
+### Patch Changes
+
+- b952f19: bye cruft
+
+## 4.0.0-beta.162
+
+### Patch Changes
+
+- b52b424: restore annotations for now
+
+## 4.0.0-beta.161
+
+## 4.0.0-beta.160
+
+### Patch Changes
+
+- 505bfa9: Add concurrent decode helper APIs and migrate decode callsites to use them.
+
+  - Add `withDefaultParseOptions` and keep `DefaultParseOptions` centralized.
+  - Export `decodeEffectConcurrently` and `decodeUnknownEffectConcurrently` from Schema and SchemaParser modules.
+  - Update repository, queue, client, form, and CLI decode paths to use concurrent decode helpers.
+  - Keep schema constructors free of hardcoded parse concurrency overrides.
+
+## 4.0.0-beta.159
+
+### Patch Changes
+
+- c1e73de:
+
+## 4.0.0-beta.158
+
+### Patch Changes
+
+- 3c1f52d: improve: class strictness enabled by default again, allow `strict: false` as opt out for now.
+- 6ae3050: Preserve class annotation parseOptions in relaxed declaration struct decoding so custom parse options (including concurrency defaults) are applied consistently.
+
+## 4.0.0-beta.157
+
+### Patch Changes
+
+- 6fff09c: unify encoded function for when you use encodedKeys
+
+## 4.0.0-beta.156
+
+## 4.0.0-beta.155
+
+### Patch Changes
+
+- c215db8: align TaggedUnion with array arg
+
+## 4.0.0-beta.154
+
+## 4.0.0-beta.153
+
+## 4.0.0-beta.152
+
+## 4.0.0-beta.151
+
+## 4.0.0-beta.150
+
+### Patch Changes
+
+- 85a8275: Expose `make`, `makeOption`, and `makeEffect` static helpers on request classes created via `Query`/`Command`.
+
+## 4.0.0-beta.149
+
+### Patch Changes
+
+- f317c5e: Preserve omitted-input make helpers through Schema.Opaque when the wrapped schema allows optional or default-only constructor input.
+
+## 4.0.0-beta.148
+
+### Patch Changes
+
+- 199e9a5: Allow Struct and TaggedStruct make helpers to omit input when every constructor field is optional or defaulted, and preserve widening copy typings through a lighter named public type to improve TypeScript editor responsiveness.
+
+## 4.0.0-beta.147
+
+### Patch Changes
+
+- 47e3742: Preserve Struct.copy through `annotate`, `annotateKey`, and `mapFields` chains, and add tests covering chained copy behavior on Struct schemas.
+
+## 4.0.0-beta.146
+
+### Patch Changes
+
+- a4dff57: Adjust Struct and TaggedStruct copy typing to follow class-style widening constraints while keeping structural copy runtime behavior.
+
+## 4.0.0-beta.145
+
+### Patch Changes
+
+- 12abb55: Refine schema copy behavior by keeping class copy constructor-based while using structural copy for Struct and TaggedStruct helpers.
+
+## 4.0.0-beta.144
+
+### Patch Changes
+
+- 11422f8: Update request helper typing and runtime invocation to rely on schema `.make` instead of class constructors, avoiding `new`-based assumptions for request schemas.
+- d31253f: Refactor eligible schema classes and tagged classes to Opaque schemas, and migrate constructor call sites to use `.make` for those models.
+
+## 4.0.0-beta.143
+
+### Patch Changes
+
+- 79eb019: Remove redundant schema `title` annotations when they duplicate the schema `identifier`.
+
+## 4.0.0-beta.142
+
+### Minor Changes
+
+- 025de47: Fold the encoded-override support from `ExtendedClass` and `ExtendedTaggedClass` into `Class`, `TaggedClass`, `ErrorClass`, and `TaggedErrorClass`, and update model codegen to detect the new second-generic form.
+
+### Patch Changes
+
+- 3436d44: Extend `Schema.Opaque` in `effect-app/Schema` to support an optional encoded-type generic while preserving the original single-generic behavior.
+
+## 4.0.0-beta.141
+
+### Patch Changes
+
+- 7c25dbb: Add relaxed wrapper support for `ErrorClass` and `TaggedErrorClass` in `effect-app/Schema`, matching the existing class wrapper behavior (`copy`, cached `ast`, and unbounded parse concurrency).
+
+## 4.0.0-beta.140
+
+## 4.0.0-beta.139
+
+## 4.0.0-beta.138
+
+## 4.0.0-beta.137
+
+## 4.0.0-beta.136
+
+## 4.0.0-beta.135
+
+### Patch Changes
+
+- c7bbc41: fix - class should check type side
+
+## 4.0.0-beta.134
+
+### Patch Changes
+
+- 9d3495e: Preserve field-level schema decode errors for relaxed Class and TaggedClass declarations so decode failures report nested constraints (for example min-length violations) instead of only a generic class-type mismatch.
+- f353d48: Rename the Class/TaggedClass relaxed declaration option to `strict` (default `false`) and apply it to `Class`, `TaggedClass`, `ExtendedClass`, and `ExtendedTaggedClass`.
+
+  When `strict: true`, class decoding keeps strict class-level declaration behavior; by default, decoding remains relaxed and preserves field-level schema errors.
+
+## 4.0.0-beta.133
+
+### Patch Changes
+
+- c3299f7: update packages
+
+## 4.0.0-beta.132
+
+## 4.0.0-beta.131
+
+## 4.0.0-beta.130
+
+### Patch Changes
+
+- ea1bd46: fix: prevent expansion of nominal brands
+
+## 4.0.0-beta.129
+
+## 4.0.0-beta.128
+
+### Patch Changes
+
+- 57db551: Split `TaggedRequestFor` into `Query` and `Command` factories, and mark generated request classes with `type: "query" | "command"`.
+
+  Vue client helpers now expose query-only helpers (`query`, `suspense`, `fetch`) for query requests and mutation-only helpers (`mutate`, `fetch`) for command requests.
+
+## 4.0.0-beta.127
+
+## 4.0.0-beta.126
+
+### Patch Changes
+
+- 458bb1b: fix type
+
+## 4.0.0-beta.125
+
+## 4.0.0-beta.124
+
+### Patch Changes
+
+- 256ae85: cleanup
+
+## 4.0.0-beta.123
+
+### Patch Changes
+
+- 14aba14: fix: clientFor
+
+## 4.0.0-beta.122
+
+### Patch Changes
+
+- f052d38: Replace `(...) => Effect.gen` with `Effect.fnUntraced` in `apiClientFactory`.
+
+## 4.0.0-beta.121
+
+### Patch Changes
+
+- 5ac46cb: Make `Schema.provide` dual (pipeable)
+
+## 4.0.0-beta.120
+
+### Minor Changes
+
+- f21190c: Add `copy` property to `Class` and `TaggedClass` for creating modified instances with updated fields. The `copy` method is cached per-class and supports both object and function-based updates, with pipeline support.
+
+## 4.0.0-beta.119
+
+## 4.0.0-beta.118
+
+### Minor Changes
+
+- 08d2e70: Add `concurrency: "unbounded"` parseOptions annotation to Schema constructors (Struct, Array, NonEmptyArray, Record, TaggedStruct, ReadonlySet, ReadonlyMap, Class, TaggedClass) so all encode/decode operations automatically run with unbounded concurrency. Also override `mapFields` on Struct and Class/TaggedClass to preserve the annotation.
+
+### Patch Changes
+
+- bd26832: Add nested anyOf flattening to JSON Schema post-processing
+- Update effect packages to 4.0.0-beta.52
+
+## 4.0.0-beta.117
+
+## 4.0.0-beta.116
+
+## 4.0.0-beta.115
+
+## 4.0.0-beta.114
+
+## 4.0.0-beta.113
+
+## 4.0.0-beta.112
+
+## 4.0.0-beta.111
+
+### Patch Changes
+
+- ca94edf: fix typo
+
+## 4.0.0-beta.110
+
+## 4.0.0-beta.109
+
+## 4.0.0-beta.108
+
+### Patch Changes
+
+- 3e46e7b: allow excess props in openapi schemas
+
+## 4.0.0-beta.107
+
+## 4.0.0-beta.106
+
+## 4.0.0-beta.105
+
+## 4.0.0-beta.104
+
+### Minor Changes
+
+- e944bca: Add `generateGuards` and `generateGuardsFor` to `TaggedUnion` / `ExtendTaggedUnion` for property-scoped type guards.
+
+  - `generateGuards("key")` — generic per-guard, no need to specify the container type
+  - `generateGuardsFor<A>()("key")` — curried, fixes `A` for concrete guard signatures
+
+  Both return `{ is{Tag}, isAnyOf }` guards that narrow the container type by its tagged union property.
+
+## 4.0.0-beta.103
+
+### Minor Changes
+
+- 7119320: Add `generateGuards` to `TaggedUnion` / `ExtendTaggedUnion` for generating property-scoped type guards.
+
+  Usage: `MyUnion.generateGuards<MyType>()("propertyKey")` returns `{ is{Tag}, isAnyOf }` guards that narrow the container type by its tagged union property.
+
+## 4.0.0-beta.102
+
+## 4.0.0-beta.101
+
+## 4.0.0-beta.100
+
+## 4.0.0-beta.99
+
+## 4.0.0-beta.98
+
+## 4.0.0-beta.97
+
+## 4.0.0-beta.96
+
+### Patch Changes
+
+- 5615e47: bs
+
+## 4.0.0-beta.95
+
+### Patch Changes
+
+- 88838fb: Remove pick/omit customizations from Class/TaggedClass/Struct/TaggedStruct. Use `Struct.pick(X.fields, [...])` from `effect-app` instead.
+
+## 4.0.0-beta.94
+
+## 4.0.0-beta.93
+
+## 4.0.0-beta.92
+
+## 4.0.0-beta.91
+
+### Minor Changes
+
+- 738b482: Add pick/omit to Struct and TaggedStruct
+
+## 4.0.0-beta.90
+
+## 4.0.0-beta.89
+
+## 4.0.0-beta.88
+
+## 4.0.0-beta.87
+
+## 4.0.0-beta.86
+
+## 4.0.0-beta.85
+
+## 4.0.0-beta.84
+
+## 4.0.0-beta.83
+
+## 4.0.0-beta.82
+
+## 4.0.0-beta.81
+
+## 4.0.0-beta.80
+
+## 4.0.0-beta.79
+
+### Minor Changes
+
+- d16845e: Remove `TaggedRequest` from `makeRpcClient`, now only `TaggedRequestFor` is returned. Remove all legacy `meta.moduleName` support — `id` and `moduleName` are now required on `Req` type. Remove `makeRpcGroup` (use `makeRpcGroupFromRequestsAndModuleName` instead).
+
+## 4.0.0-beta.78
+
+## 4.0.0-beta.77
+
+### Minor Changes
+
+- 3613e87: Add `TaggedRequestFor` helper to `makeRpcClient` that curries a `moduleName`, producing request classes with static `id` and `moduleName` properties. This enables passing request classes directly to `makeQueryKey` without going through `clientFor` first. The `clientFor` function no longer requires a `meta` property on the module when requests carry `moduleName`. The meta codegen preset now generates `Req = TaggedRequestFor(moduleName)`. Original `TaggedRequest` remains for backwards compatibility.
+
+## 4.0.0-beta.76
+
+### Patch Changes
+
+- a5248a9: use new schema features
+- fac725d: update effect to latest beta
+
+## 4.0.0-beta.75
+
+### Patch Changes
+
+- 24f0a5a: rename Literal to Literals, no longer hiding Schema's singular Literal.
+
+## 4.0.0-beta.74
+
+### Patch Changes
+
+- 54ec1ef: fix bs
+
+## 4.0.0-beta.73
+
+## 4.0.0-beta.72
+
+### Patch Changes
+
+- 0541f0d: fix withDefault types
+
+## 4.0.0-beta.71
+
+### Minor Changes
+
+- beae3a0: Remove `withDefaultConstructor` wrapper, use `S.withConstructorDefault` directly with `Effect.succeed`/`Effect.sync`.
+
+## 4.0.0-beta.70
+
+## 4.0.0-beta.69
+
+### Patch Changes
+
+- dc465e3: update to latest effect beta
+
+## 4.0.0-beta.68
+
+### Patch Changes
+
+- e6f2341: Add SecretURL tests and switch secretURL config to use Config.nonEmptyString
+
+## 4.0.0-beta.67
+
+## 4.0.0-beta.66
+
+### Patch Changes
+
+- edc52e4: update
+
+## 4.0.0-beta.65
+
+### Minor Changes
+
+- 1f103b2: Replace `proxify` with explicit service accessor helpers: `accessFn`, `accessEffectFn`, `accessCn`, `accessEffectCn`.
+
+### Patch Changes
+
+- 31739d7: Fix JSON schema output for Email, Date, PhoneNumber, and Url schemas. The `jsonSchema` annotation key is not recognized by Effect v4's JSON schema generator — use proper v4 annotations (`format`, `description`) and built-in checks (`isMinLength`, `isMaxLength`) instead.
+
+## 4.0.0-beta.64
+
+### Patch Changes
+
+- c1a6fdc: fix proxify
+
+## 4.0.0-beta.63
+
+## 4.0.0-beta.62
+
+### Patch Changes
+
+- 0b21a02: fix: flatten simple allOf constraints in JSON Schema output for better codegen compatibility
+
+## 4.0.0-beta.61
+
+## 4.0.0-beta.60
+
+## 4.0.0-beta.59
+
+### Patch Changes
+
+- cec026d: update packages
+
+## 4.0.0-beta.58
+
+## 4.0.0-beta.57
+
+## 4.0.0-beta.56
+
+## 4.0.0-beta.55
+
+## 4.0.0-beta.54
+
+### Patch Changes
+
+- d867272: the return of `Context`
+
+## 4.0.0-beta.53
+
+### Patch Changes
+
+- ee9694e: fix type issue?
+
+## 4.0.0-beta.52
+
+### Minor Changes
+
+- 6252808: Add `ReadonlySetFromArray` and `ReadonlyMapFromArray` schema transformations that decode from annotated arrays to Set/Map. Update `ReadonlySet` and `ReadonlyMap` to use these internally.
+
+## 4.0.0-beta.51
+
+## 4.0.0-beta.50
+
+## 4.0.0-beta.49
+
+### Patch Changes
+
+- e585c9c: fix config nested
+
+## 4.0.0-beta.48
+
+### Patch Changes
+
+- 0c88f78: Remove `TaggedError` compatibility re-export, use `TaggedErrorClass` directly
+
+## 4.0.0-beta.47
+
+### Patch Changes
+
+- 3365758: workaround effect error messages
+
+## 4.0.0-beta.46
+
+## 4.0.0-beta.45
+
+### Patch Changes
+
+- 10b55ff: update packages
+
+## 4.0.0-beta.44
+
+### Patch Changes
+
+- a37aa38: Update to effect beta 43
+
+## 4.0.0-beta.43
+
+## 4.0.0-beta.42
+
+## 4.0.0-beta.41
+
+## 4.0.0-beta.40
+
+## 4.0.0-beta.39
+
+### Patch Changes
+
+- 10e90d5: fix: TaggedRequest should be an Opaque Schema Class
+
+## 4.0.0-beta.38
+
+### Patch Changes
+
+- 0b3e00e: fix bug
+
+## 4.0.0-beta.37
+
+### Patch Changes
+
+- 947fe20: fix input date
+
+## 4.0.0-beta.36
+
+## 4.0.0-beta.35
+
+## 4.0.0-beta.34
+
+### Patch Changes
+
+- 8c645d5: update to latest effect
+
+## 4.0.0-beta.33
+
+### Patch Changes
+
+- 4b95009: use Finite instead of Number
+
+## 4.0.0-beta.32
+
+### Patch Changes
+
+- 01d862a: again
+
+## 4.0.0-beta.31
+
+### Patch Changes
+
+- 6b6d601: fix ForceVOid
+
+## 4.0.0-beta.30
+
+### Patch Changes
+
+- 5ec1f45: fix ForceVoid for real
+
+## 4.0.0-beta.29
+
+### Patch Changes
+
+- a899d46: Replace `ForceVoid` in `makeClient` with a typed codec transformation instead of an unsafe cast.
+
+## 4.0.0-beta.28
+
+### Patch Changes
+
+- 0099208: Refactor `Pure` helpers to use typed `useSync` calls instead of unsafe casts.
+
+## 4.0.0-beta.27
+
+### Patch Changes
+
+- 601a1ff: update effect to 4.0.0-beta.37 and drop the Schema Class disableValidation workaround now that the patched effect schema covers it
+
+## 4.0.0-beta.26
+
+### Patch Changes
+
+- 4da28e2: Change `Schema.Class` and `Schema.TaggedClass` wrappers to default constructor options to `{ disableValidation: true }`.
+
+  This avoids strict class identifier validation by default when constructing wrapper classes (for example passing a compatible view class), while keeping existing behavior when explicit options are provided.
+
 ## 4.0.0-beta.25
 
 ### Patch Changes