@gjermundgaraba/effect-actions 0.10.0 → 0.12.0

package/docs/Testing.md

@@ -1,174 +1,209 @@
 # Testing
 
-In-memory calls against served layers, through Effect's own `HttpClient`. Needs no extra
-dependency and opens no port. It tests what the wire does: routes and tools, authentication,
-statuses and codecs as sent. What an implementation does, its authorization and its handlers, is tested in process with `Action.client` ([Implementations](#implementations)).
+Two ways to test, and neither opens a port. `Action.client` calls an implementation in process:
+what its handlers and its `authorize` do. `Testing.layer` answers the real routes in memory,
+through Effect's own `HttpClient`: what a surface adds, such as authentication, statuses,
+challenges and tool results as sent. The examples put a domain's tests in `test/<domain>/` and
+tests of the surfaces beside them, in `it.effect` from `@effect/vitest`, which supplies the
+`Scope` that `Action.client` and `ActionRpc.client` require, a `TestClock` and a `TestConsole`
+(both imported from `effect/testing`).
+
+Read this page alone, in one tool call: pages read together are cut. When something fails,
+search [Testing-failures.md](Testing-failures.md). Reading order: [README.md](README.md).
 
 ## API
 
 Import `@gjermundgaraba/effect-actions/Testing`.
 
-| API                                     | Purpose                                                                             |
-| --------------------------------------- | ----------------------------------------------------------------------------------- |
-| `layer(routes)`                         | A `Layer<HttpClient>` answering requests with `routes` in memory.                   |
-| `layer(handler)`                        | A `Layer<HttpClient>` answering requests with a web handler the test serves.        |
-| `mcpClient(actions, options?)`          | An Effect of a client calling each action's tool, like `ActionHttp.client`.         |
-| `mcpRequest(method, params?, options?)` | One request an `ActionMcp` endpoint serves, as the native request the test sends.   |
-| `McpCallError`                          | What a client method fails with for an answer it cannot decode; `message` holds it. |
-
-| Option                         | Meaning                                                                                                                                               |
-| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `url`                          | The endpoint, resolved by the `HttpClient` (relative under `layer`, or one prepending a base URL); default `/mcp`, the `ActionMcp.layerHttp` default. |
-| `mcpClient`: `transformClient` | Wraps the native `HttpClient`, as `ActionHttp.client` takes it: `HttpClient.mapRequest(HttpClientRequest.bearerToken(token))`.                        |
-| `mcpRequest`: `headers`        | Request headers.                                                                                                                                      |
-
-Exported types: `McpClient<Actions>`, a client's type; `McpClientOptions` of `mcpClient`; `McpRequestOptions` of `mcpRequest`, and `McpParams`, its `params`.
-
-`mcpClient(actions, options)` builds a client on the `HttpClient` in context, one method per
-action, called as a client method is: `mcp.getUser({ id })`. For every tool one implementation
-serves, pass its actions: `Testing.mcpClient(userActions.actions)`. A method succeeds with the
-action's decoded success. It fails with the action's declared errors and the built-in ones as
-decoded values, `SchemaError`, `HttpClientError`, or `McpCallError` for any other answer.
-Only a tool result carries the action's own errors; any other response decodes only as a
-refusal, as authentication and an authorizer send. The input may be left out when `{}` is a valid
-input, sending the input `{}` decodes to, and a given input is sent as given, as for a client's
-method.
-
-## Canonical
-
-```ts example=testing.ts
-import { Effect } from "effect";
-import * as ActionHttp from "@gjermundgaraba/effect-actions/ActionHttp";
-import * as Testing from "@gjermundgaraba/effect-actions/Testing";
-import { Greet, Http } from "./quickstart.js";
-import { routes } from "./quickstart-server.js";
-
-const program = Effect.gen(function* () {
-  const client = yield* ActionHttp.client(Http);
-  const greeting = yield* client.greet({ name: "Ada" });
-
-  // The same action as a tool of `/mcp`, called like the client's method.
-  const mcp = yield* Testing.mcpClient([Greet]);
-  const called = yield* mcp.greet({ name: "Ada" });
-
-  return { greeting, called };
-});
-
-// The routes answer in memory for the program's scope, and are released after it.
-console.log(await Effect.runPromise(program.pipe(Effect.provide(Testing.layer(routes)))));
+| API                                     | Purpose                                                                       |
+| --------------------------------------- | ----------------------------------------------------------------------------- |
+| `layer(routes)`                         | A `Layer<HttpClient>` answering requests with `routes` in memory.             |
+| `layer(handler)`                        | A `Layer<HttpClient>` answering requests with a web handler the test serves.  |
+| `mcpClient(actions, options?)`          | An Effect of a client calling each action's tool, like `ActionHttp.client`.   |
+| `mcpRequest(method, params?, options?)` | One MCP request, as the native `HttpClientRequest` the test sends.            |
+| `McpCallError`                          | A client method's failure for an answer it cannot decode; `message` holds it. |
+
+| Option                         | Meaning                                                                         |
+| ------------------------------ | ------------------------------------------------------------------------------- |
+| `url`                          | The endpoint; default `/mcp`, the `ActionMcp.layerHttp` default.                |
+| `mcpClient`: `transformClient` | Wraps the native `HttpClient`, as `ActionHttp.client` takes it: a bearer token. |
+| `mcpRequest`: `headers`        | Request headers.                                                                |
+
+Exported types: `McpClient<Actions>`, `McpClientOptions`, `McpRequestOptions`, and `McpParams`,
+the `params` of `mcpRequest`.
+
+## Test an implementation in process
+
+Acquire `Action.client(implementation)` and call its methods
+([Action-in-process.md](Action-in-process.md#call-actions-in-process)). A call runs the decoding,
+the `authorize` and the handler a server runs, but no authentication and no middleware. Provide
+the startup services around the test, as an entrypoint does, and what a request would carry, its
+caller first, around each call:
+
+```ts
+const as = (user: keyof typeof users) => Effect.provideService(CurrentUser, users[user]);
+
+it.effect("keeps each user's notes their own", () =>
+  Effect.gen(function* () {
+    const client = yield* Action.client(notes);
+    const note = yield* client.createNote({ title: "Plan", body: "Draft" }).pipe(as("ada"));
+
+    expect(yield* client.listNotes().pipe(as("grace"))).toEqual({ notes: [] });
+  }).pipe(Effect.provide(NoteStore.layerMemory)),
+);
 ```
 
-### Implementations
-
-What an implementation does, with no transport between: `Action.client` gives the methods
-`ActionHttp.client` gives, and each call runs the authorizer and the handler, with every
-check a surface makes on its input, its success and its failure ([Action.md](Action.md#clients)). Each
-call takes its caller, so one test has several, and an action no binding holds, such as a
-tool, has a method like any other.
-
-```ts example=in-process.ts
-import { Effect } from "effect";
-import * as Action from "@gjermundgaraba/effect-actions/Action";
-import { actors, CurrentActor } from "./authorization.js";
-import { userActions } from "./handlers.js";
-import { Users } from "./users.js";
+See [notes-service/test/notes/notes.test.ts](../examples/notes-service/test/notes/notes.test.ts).
 
-// Each call names its caller, as authentication names one per request.
-const asAlice = Effect.provideService(CurrentActor, actors.alice);
+- Replace the edge, not the service under test:
+  [mcp-tools/test/printers/printers.test.ts](../examples/mcp-tools/test/printers/printers.test.ts)
+  runs the real upstream service over a fake `HttpClient` Layer.
+- `it.effect` runs on a test clock: fork a call that waits, `TestClock.adjust`, then join it.
+- A stdio server runs the same implementations: test them here. A subprocess test adds only what
+  the process adds, stdout carrying nothing but the protocol.
+- A Toolkit and a CLI need no `Testing` export: call `toolkit.handle` or script a
+  `LanguageModel` ([assistant/test/toolkit.test.ts](../examples/assistant/test/toolkit.test.ts)),
+  and run commands with `Command.runWith`
+  ([assistant/test/commands.test.ts](../examples/assistant/test/commands.test.ts)).
 
-const asReader = Effect.provideService(CurrentActor, actors.reader);
+## Test routes in memory
 
-const program = Effect.gen(function* () {
-  // Acquired once, as a layer is built: the builders run here, not per call.
-  const users = yield* Action.client(userActions);
+Export the routes still requiring what an entrypoint chooses, give the test its own, and provide
+the layer to each test:
 
-  // The methods of `ActionHttp.client(Http)`, with no transport between: each call decodes
-  // its input, runs `authorize`, then the handler, and checks the success or the failure.
-  const renamed = yield* users.renameUser({ id: "1", name: "Bea" }).pipe(asAlice);
-  const refused = yield* Effect.flip(users.renameUser({ id: "1", name: "Cy" }).pipe(asReader));
-  const { changes } = yield* users.listChanges().pipe(asReader); // not an HTTP route
-
-  return { renamed, refused, changes };
-});
-
-// The builders are released with the program's scope, before the services they captured.
-console.log(
-  await Effect.runPromise(program.pipe(Effect.scoped, Effect.provide(Users.layerMemory))),
-);
+```ts
+const served = Testing.layer(routes).pipe(Layer.provide(NoteStore.layerMemory));
 ```
 
-### Signed-in callers
-
-Protected routes on the wire: serve them behind their authentication, the real provider or a
-test verifier of the same descriptor, and give each client its caller's credential. One `layer`
-serves every caller; the test program shares what the routes read, such as `Users`.
-
-```ts example=testing-caller.ts
-import { Effect, Layer } from "effect";
-import { HttpClient, HttpClientRequest } from "effect/http";
-import * as ActionHttp from "@gjermundgaraba/effect-actions/ActionHttp";
-import * as Testing from "@gjermundgaraba/effect-actions/Testing";
-import { authenticate } from "./authentication.js";
-import { Http } from "./binding.js";
-import { userActions } from "./handlers.js";
-import { Users } from "./users.js";
-
-// The routes behind their real authentication; the caller is the token each client sends.
-const routes = Testing.layer(
-  ActionHttp.layer(Http, userActions).pipe(Layer.provide(authenticate)),
-).pipe(Layer.provideMerge(Users.layerMemory));
-
+Under it, `ActionHttp.client(Http)` needs no `baseUrl`, and `HttpClient.get("/healthz")` reaches
+the host's own routes. Each test builds the routes anew, so each starts from an empty store. See
+[notes-service/test/routes.test.ts](../examples/notes-service/test/routes.test.ts); the smallest
+test is
+[quickstart/test/greeting/greeting.test.ts](../examples/quickstart/test/greeting/greeting.test.ts).
+
+- A service the test reads too goes around `layer` with `Layer.provideMerge`, so handlers and
+  test share one instance
+  ([kitchen-sink/test/identity/session.test.ts](../examples/kitchen-sink/test/identity/session.test.ts)).
+- Two `layer`s are two servers: a second one runs every builder again, and they share only what
+  is provided around both. For two ports, that is `Action.layer(implementations)` and the
+  services ([kitchen-sink/test/routes.test.ts](../examples/kitchen-sink/test/routes.test.ts),
+  [Action-in-process.md](Action-in-process.md#share-one-build-across-servers)).
+- The client is `layer`'s own. A fake upstream is another `HttpClient`: provide it to the service
+  that calls out ([mcp-tools/test/routes.test.ts](../examples/mcp-tools/test/routes.test.ts)).
+- Every request on `layer`'s client reaches the routes, whatever its host: a client given a
+  `baseUrl`, a remote `ActionCli` command's included, runs in memory unchanged.
+- Requests run in the test's context: a `ConfigProvider` or the test clock around the test
+  reaches middleware and handlers.
+- To send raw web `Request`s too, build one `HttpRouter.toWebHandler` and dispose it yourself;
+  `Testing.layer(web.handler)` gives the typed clients the same handler
+  ([kitchen-sink/test/request-policy.test.ts](../examples/kitchen-sink/test/request-policy.test.ts)).
+
+## Test as a signed-in caller
+
+The routes keep their real authentication. Serve them behind their provider
+([Authentication.md](Authentication.md#verify-credentials)), and give each client its caller's
+credential:
+
+```ts
 const as = (token: string) => ({
   transformClient: HttpClient.mapRequest(HttpClientRequest.bearerToken(token)),
 });
+```
+
+Both clients take it: `ActionHttp.client(Http, as("reader"))` and
+`Testing.mcpClient([GetStatus, ...Notes], as("ada"))`.
+
+- Never provide the identity to `layer`, around it or to the routes. It is a type error: only a
+  provider of their own descriptor satisfies them.
+- To change what a credential verifies as, replace the service the verifier reads (`servedWith`
+  in
+  [kitchen-sink/test/identity/identity.test.ts](../examples/kitchen-sink/test/identity/identity.test.ts)),
+  or provide a test verifier: another `Authentication.layer` of the same descriptor.
+
+A typed client decodes a refusal to its error. To assert on the answer as sent, build the request
+(`HttpClientRequest.post`, `bearerToken`, `bodyJsonUnsafe`) and send it with `HttpClient.execute`,
+which succeeds whatever the status. Read `response.status` and
+`response.headers["www-authenticate"]`, the challenge, as that file does. The status and body of
+each case are the table in [guarantees.md](guarantees.md#wire-behavior).
+
+## Test MCP tools
+
+`Testing.mcpClient(actions, options?)` gives one method per action, calling its tool and decoding
+the result as `ActionHttp.client` decodes a route's, an image included. Pass the contract values
+the endpoint serves, such as `implementation.actions`.
+
+A method fails with the action's declared errors and the built-in ones as decoded values, and with
+`McpCallError` for any other answer, a result without its structured content included;
+structured content that does not decode as the success is a `SchemaError`, and a request that
+fails Effect's `HttpClientError`. Only a tool's result carries the action's own errors: an HTTP
+answer other than 200 decodes as a refusal alone, so an error a verifier declares, typed over
+`ActionHttp.client`, is an `McpCallError` here
+([kitchen-sink/test/identity/identity.test.ts](../examples/kitchen-sink/test/identity/identity.test.ts)).
+
+A method decodes a refusal alike whether the endpoint answered a 401 or a 403 or returned a tool
+result in a 200 ([guarantees.md](guarantees.md#wire-behavior)): to assert which, send the call
+yourself and read its status.
+
+For that, and for what the client's types will not send or its decoding hides (`tools/list`, an
+`Origin` header, a refusal's challenge, a malformed call), build the request with
+`Testing.mcpRequest`. It returns a native `HttpClientRequest`:
+`yield* HttpClient.execute(Testing.mcpRequest("tools/call", { name: "whoAmI", arguments: {} }))`
+succeeds with the response whatever its status, to read `response.status`, `response.headers`
+and `yield* response.json`
+([kitchen-sink/test/identity/identity.test.ts](../examples/kitchen-sink/test/identity/identity.test.ts)
+asserts a 401 so, and
+[mcp-tools/test/routes.test.ts](../examples/mcp-tools/test/routes.test.ts) reads `tools/list`).
+For a web handler or `fetch`, pass an absolute `url`: `HttpClientRequest.toWebResult(request)` is
+then a `Result` holding the web `Request`, taken with `Result.getOrThrow`.
+
+## Test rpcs
+
+`Testing.layer` answers HTTP requests and cannot upgrade a WebSocket. Export the rpc layer without
+its protocol ([ActionRpc.md](ActionRpc.md#serve-the-rpcs)), and give it Effect's HTTP protocol in
+the test, on both sides:
+
+```ts
+const server = rpc.pipe(
+  Layer.provide(RpcServer.layerProtocolHttp({ path: "/rpc" })),
+  Layer.provide(RpcSerialization.layerJson),
+);
 
-const program = Effect.gen(function* () {
-  const reader = yield* ActionHttp.client(Http, as("reader"));
-  const refused = yield* Effect.flip(reader.renameUser({ id: "1", name: "Bea" })); // Forbidden
-  const users = yield* Users;
+const served = RpcClient.layerProtocolHttp({ url: "/rpc" }).pipe(
+  Layer.provide(RpcSerialization.layerJson),
+  Layer.provide(Testing.layer(server)),
+  Layer.provide(MessageStore.layerMemory),
+);
 
-  return { refused, unchanged: yield* users.get("acme", "1") };
-});
+const as = (token: string) => RpcClient.withHeaders({ authorization: `Bearer ${token}` });
+```
 
-console.log(await Effect.runPromise(program.pipe(Effect.provide(routes))));
+Authentication is per message, so each call carries its credential and one client serves every
+caller: `client.postMessage({ text }).pipe(as("ada"))`. See
+[live-rpc/test/routes.test.ts](../examples/live-rpc/test/routes.test.ts);
+[live-rpc/test/browser.test.ts](../examples/live-rpc/test/browser.test.ts) tests a page's client
+the same way. To call JSON routes in the same test, merge both route layers into the one
+`Testing.layer` and give it to the protocol with `Layer.provideMerge`, which keeps its `HttpClient`
+for the test
+([kitchen-sink/test/identity/session.test.ts](../examples/kitchen-sink/test/identity/session.test.ts)).
+Effect's `RpcTest.makeClient` is no substitute: it asks for handlers of the
+binding's group, which `ActionRpc.layer` does not provide (`Handler<"…">` stays required).
+
+## Assert on errors
+
+Take the failure with `Effect.flip(call)`, which alone asserts only that the call failed, then
+assert its class and its `message` separately:
+
+```ts
+expect(refusal).toBeInstanceOf(Action.Forbidden);
+expect(refusal.message).toBe("Requires notes:write.");
 ```
 
-A verifier needing infrastructure in production is replaced, for a test, by another `layer` of the
-same descriptor: `Authentication.layer(Login, (token) => ...)`.
-Any provider of that descriptor satisfies the routes; nothing else does.
-
-## Rules
-
-- `layer(routes)` builds the routes with request logging off, and releases them with the layer's scope. What the routes still require is the layer's, as under `HttpRouter.serve`: their builders' services, and any per-request service no middleware of theirs provides, including one a global middleware reads. Provide them around it, with `Layer.provideMerge` where the program reads them too, so the handlers and the program share one instance. A per-request service provided there, such as a tenant, reaches every request. A protected action's identity is not such a service: its routes require their authentication provider, which nothing provided around `layer` replaces ([Signed-in callers](#signed-in-callers)). Each `layer` builds the routes anew, builders included, unless `Action.layer` built them above it. Requests run in the context the layer is built in, as under `HttpRouter.serve`: a `TestClock` or a reference provided around the program reaches middleware and handlers.
-- `layer` never requires the platform services `FileSystem`, `Path`, `HttpPlatform` and `Etag.Generator`, but they follow the same rule: at build and per request, the routes get the ones provided around `layer`, and `HttpServer.layerServices`' defaults for the rest, whose `FileSystem` is a no-op. The default `HttpPlatform` reads files through the `FileSystem` provided around `layer`.
-- A relative URL resolves against `http://localhost`, once any `baseUrl` a client adds is applied, so `ActionHttp.client(Http)` needs no `baseUrl` under `layer`, and one given is kept. Every request on this client is answered by the routes, whatever its host, so the native `HttpApiClient` and a remote `ActionCli` command work in memory too.
-- The client is `layer`'s own: the program's other HTTP clients get none of its requests, and it none of theirs, whether a `FetchHttpClient` is built before or after it or a `FetchHttpClient.Fetch` is provided around the program.
-- `layer(handler)` gives the same client, answered by a web handler the test serves, such as `HttpRouter.toWebHandler(routes.pipe(Layer.provide(HttpServer.layerServices))).handler` shared with tests that send it `Request`s: the routes are built once, by the handler, for every `layer` given it. The web handler needs the routes' platform services, which `HttpServer.layerServices` provides and `layer(routes)` supplies itself. The test owns the handler: `layer` neither builds nor disposes it, so the test calls `dispose` when it is done.
-- A client method sends one stateless `tools/call` for the action's tool, at the protocol version `ActionMcp.layerHttp` serves, 2026-07-28, in both the header and `_meta`. It encodes the input with the action's schema, and decodes the success from `structuredContent`, as `ActionHttp.client` does for a route. It reads a JSON or an event-stream response.
-- A declared error, the action's own or a built-in one, is a typed failure of its decoded value: an `isError` result from the tool, or a 401 or 403 from the endpoint's authentication or an authorizer, whose body is the same JSON. Match it with `Effect.catchTag`, exactly as on the HTTP client.
-- Any other answer fails with `McpCallError`, whose `message` holds it: another status, the native server's own text (invalid arguments, a defect), no reply, a result without `structuredContent`, or a JSON-RPC error (an unknown tool). Match it with `Effect.catchTag("McpCallError", ...)`.
-- The input is typed, so a malformed call cannot be sent through a client method. To assert on a malformed call, another MCP method or the response itself, such as a refusal's status and `WWW-Authenticate` challenge, send `mcpRequest(method, params, options)`.
-- `mcpRequest` is one stateless request as a client method sends it, a native `HttpClientRequest` the test sends itself: with `mcp-name` from `params.uri` for `resources/read` and from `params.name` otherwise, and the client metadata in `_meta`. A `_meta` in `params`, such as a `progressToken`, is merged over the client metadata, and the protocol version is always the request's own.
-- Under `layer`, send it with `HttpClient.execute(Testing.mcpRequest("tools/list"))`, which succeeds with the response whatever its status.
-- A Promise test sends it as a web `Request`, to a web handler or to `fetch`, for a web `Response` back: `handler(Result.getOrThrow(HttpClientRequest.toWebResult(Testing.mcpRequest(method, params, { url: "http://localhost/mcp" }))))`. The `url` is absolute, the handler's origin or a listening server's, since a web `Request` has no `HttpClient` to resolve a relative one.
-- A tool call the typed client would not send is `mcpRequest("tools/call", { name, arguments })`, its result read from the response's JSON: `result.structuredContent`, or `result.isError` and `result.content`.
-- To assert on a result's exact bytes, such as a size bound, parse the text of an `mcpRequest`'s JSON response: `JSON.stringify` of the parsed message reproduces what the server wrote, less its final newline, so `JSON.stringify(message.result)` is the result as encoded.
-- A request under `layer` carries the `Host` header of its URL, `localhost` for a relative one, unless it sets its own, so middleware checking the host answers as it would over the network.
-- Add `Authorization` through `transformClient`, the same options for `mcpClient` and `ActionHttp.client`: one client per caller, `const alice = { transformClient: HttpClient.mapRequest(HttpClientRequest.bearerToken("alice")) }`. `mcpRequest` takes `headers`.
-- A client names each tool by its action and holds no connection. Duplicate action names throw `Duplicate action: <name>`.
-- Test what an implementation does in process, with `Action.client`: its authorizer, its handlers, and the checks every surface makes on input, success and failure, with several callers, an action no binding holds included. Test what a surface adds under `layer`: authentication, statuses, headers, bodies as sent and MCP results. The two call the same methods. Cover each surface the application exposes.
-
-## Failure modes
-
-- Fails with `Action.Unauthenticated`: the call reached authentication without a valid credential. Give the client a `transformClient` adding it, such as `HttpClient.mapRequest(HttpClientRequest.bearerToken(token))`.
-- `MCP tools/call "<name>" returned an error: Invalid parameters for tool ...`: the endpoint serves a different contract under that name than the one passed. Call it with the served contract value.
-- 404 from a client method: the action's implementation was not passed to any `ActionHttp.layer` call of its binding in the served routes, or `baseUrl` adds a path the routes do not have. Include `ActionHttp.layer(Http, implementations)` in the routes.
-- The program reads a service the handlers never changed: it was provided inside the routes and again to the program, two instances. Provide it once, around `layer`, with `Layer.provideMerge`.
-- `Type 'Provider<CurrentActor, "example.Login">' is not assignable to type 'never'` where the test runs, such as at `Effect.runPromise`: the routes serve a protected action and no provider of its descriptor is provided to them. Provide it to the routes, `ActionHttp.layer(Http, app).pipe(Layer.provide(authenticate))`, or a test verifier of the same descriptor. A caller provided around `layer` does not satisfy it ([Signed-in callers](#signed-in-callers)).
-- `Type 'CurrentActor' is not assignable to type 'never'` where the test runs: a public action's handler reads the identity, which no route provides it. Make the action protected.
-- A protected route answers 401 where the test expects a 415 or a 400: the request carries no credential that verifies, and authentication runs first. Send a token with requests about something else.
-- `Argument of type 'Layer<…, FileSystem | Generator | HttpPlatform | HttpRouter | Path>' is not assignable` at `HttpRouter.toWebHandler(routes)`, then `No overload matches this call` at `layer(web.handler)`, its last overload naming `Layer<unknown, unknown, unknown>`, or `Expected 2 arguments, but got 1` at `web.handler(request)`: the web handler's routes lack their platform services. Provide them: `HttpRouter.toWebHandler(routes.pipe(Layer.provide(HttpServer.layerServices)))`.
-- A builder or handler finds no file where one exists, failing with `NotFound: FileSystem.<method> (<path>)`, or a file route answers 500: nothing provided a `FileSystem` around `layer`, so the routes read a no-op one. Provide `NodeFileSystem.layer` or `NodeServices.layer` around it, with `Layer.provideMerge` where the program reads files too.
-- `MCP tools/call "<name>" answered 404`: the endpoint is not at `/mcp`. Pass its `url`.
-- `HttpClientRequest.toWebResult` or `toWeb` of an `mcpRequest` fails with `UrlError`: its `url` is the relative default. Pass an absolute `url`.
-- An `HttpClientError` whose reason is `InvalidUrlError`, from a client method or a sent `mcpRequest` on an `HttpClient` that prepends no base URL: a relative `url` resolves under `layer`, and under a client that prepends one, such as `NodeHttpServer.layerTest`'s. Pass an absolute `url`.
+`toEqual` never compares a tagged error's `message`, which is not an enumerable property:
+`expect(error).toEqual(new Action.Forbidden({ message: "anything" }))` passes for every message,
+and so does `toStrictEqual`. Other fields are compared, so `toEqual(new NoteNotFound({ id }))`
+asserts the `id`, and `toEqual(new Action.Forbidden({ scopes: ["issues:write"] }))` still needs the
+message asserted beside it. The message is all a model reads of a tool's failure.
+
+A Toolkit raises neither a refusal nor a declared error: each is a result the model reads, so
+assert `isFailure` and `result.message`
+([assistant/test/toolkit.test.ts](../examples/assistant/test/toolkit.test.ts)).