docs: align client route-tree guidance

Update README, context docs, and public TSDoc after removing low-level request factories and renaming the client metadata property. The docs now emphasize generated route action calls, the required routes option, and clientConfig as the non-colliding metadata property.

Author: aleclarson

README.md

@@ -2,6 +2,7 @@
 
 Rouzer lets you declare an HTTP route tree once and share its TypeScript types
 and Zod validation between a Hattip-compatible server and a typed fetch client.
+The client is always created from that route tree.
 
 ## What it does
 
@@ -45,7 +46,7 @@ Consider something else if:
 - Zod v4 or newer
 - a Hattip adapter when using `createRouter(...)`
 - a Fetch API implementation when using `createClient(...)`
-- an absolute `baseURL` for generated client URLs
+- an absolute `baseURL` and shared `routes` tree for generated client URLs
 
 ## Installation
 
@@ -101,9 +102,9 @@ const { message } = await client.hello({
 })
 ```
 
-`handler` can be mounted with any Hattip adapter. Client action calls validate
-route arguments before `fetch`; server handlers validate matched path, query,
-headers, and JSON bodies before your handler runs.
+`handler` can be mounted with any Hattip adapter. Generated client action calls
+validate route arguments before `fetch`; server handlers validate matched path,
+query, headers, and JSON bodies before your handler runs.
 
 ### Typed status responses
 

docs/context.md

@@ -233,7 +233,8 @@ const client = createClient({
 
 Default headers can be supplied with `headers`, per-request headers are merged on
 top, and a custom `fetch` implementation can be supplied for tests or non-browser
-runtimes.
+runtimes. The returned client exposes the original options as `clientConfig`, so
+route actions named `config` remain available as `client.config(...)`.
 
 ## Lifecycle
 
@@ -459,7 +460,7 @@ await client.profiles.update({
 - Export route trees from a small shared module and import that module on both
   server and client.
 - Use `rouzer/http` actions for routes that are registered with
-  `createRouter().use(...)` or `createClient({ routes })`.
+  `createRouter().use(...)` or the required `createClient({ routes })` option.
 - Add Zod schemas when you need runtime guarantees; rely on inferred path params
   only when string params are sufficient.
 - Use `response: $type<T>()` for JSON endpoints that should have typed client
@@ -489,8 +490,9 @@ await client.profiles.update({
 - Resource and action keys are API names only; paths come from the pattern
   strings passed to `http.resource(...)` and action helpers.
 - Extra `RequestInit` fields in route args, such as `signal` or `credentials`,
-  are forwarded by `createClient`; `method`, `body`, and `headers` are reserved
-  for Rouzer's action metadata and validated call arguments.
+  are forwarded by `createClient`; `method` and `body` are reserved for Rouzer's
+  action metadata and validated call arguments. Use route args or client defaults
+  for request headers.
 - The HTTP action API has no `ALL` fallback route. Declare explicit actions for
   supported methods.
 - Rouzer does not automatically set `Access-Control-Allow-Credentials`; set it in

src/client/index.ts

@@ -58,12 +58,12 @@ export function createClient<
   /** Response codec plugins used by generated action functions. */
   plugins?: readonly ClientResponsePlugin[]
   /**
-   * Custom handler for non-2xx responses from `.json()` and generated response
-   * helpers.
+   * Custom handler for non-2xx responses from generated client action
+   * functions.
    *
-   * @remarks When provided, the return value is returned from the response
-   * helper as-is; Rouzer does not automatically parse a `Response` returned by
-   * this hook.
+   * @remarks When provided, the return value is returned from the client action
+   * as-is; Rouzer does not automatically parse a `Response` returned by this
+   * hook.
    */
   onJsonError?: (response: Response) => Promisable<unknown>
   /** Custom `fetch` implementation to use for requests. */

src/types/args.ts

@@ -35,7 +35,7 @@ type MutationArgs<T> = T extends MutationRouteSchema
   : unknown
 
 /**
- * Arguments accepted by a client action function or low-level request factory.
+ * Arguments accepted by a generated client action function.
  *
  * @remarks The type is derived from an action schema and route pattern. `path`,
  * `query`, `body`, and `headers` are validated by the client before `fetch` when