client: defaultCallOptions on createClient (0.216.1)

[jackyzha0]

Why

Consumers of river that need to inject a default signal (or other CallOptions field) into every leaf RPC currently have to wrap the client with a recursive Proxy. That's fragile against river's callable intermediate segments — client.<service> is itself callable, so naive wrappers silently drop the signal at the leaf if the recursion doesn't special-case function-valued targets.

What changed

• ClientOptions gains optional defaultCallOptions?: CallOptions | (() => CallOptions).
• The createClient dispatch path resolves the default (calling the function form per leaf invocation) and spreads it under the caller's options. Caller wins field-by-field.
• Function form lets consumers parameterize a single pooled client without re-creating it (e.g. an ambient signal that changes between invocations).
• Exports CallOptions and ClientOptions from the router index so consumers can name them.
• Patch bump 0.216.0 → 0.216.1 (additive, no breaking changes).

Tests

Three new E2E cases under the existing transport×codec matrix (12 runs total):

1. defaultCallOptions provides signal when caller omits it — eager form drives cancellation.
2. caller-supplied signal overrides defaultCallOptions — verifies caller wins.
3. function-form defaultCallOptions is resolved per call — two subscribes capture different signals from a closure variable; aborting one signal cancels only its subscribe.

Full suite: 661 passed | 1 pre-existing skip.

Test plan

• npx tsc --noEmit
• npx eslint .
• npx prettier . --check
• npx vitest run (full suite, 661/662)
• New tests: 12/12 across the matrix

Revertibility

One commit. The new field is optional; existing call sites are unaffected.

🤖 Generated with Claude Code