docs: document runtimeValidation both strategy

Update the angular, angular-query and fetch `runtimeValidation` reference entries
to document the object form `{ strategy: 'throw' | 'both' }` and the
log-then-throw behaviour of `both`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: the-ult

docs/content/docs/reference/configuration/output.mdx

@@ -1282,11 +1282,13 @@ Force a specific version for generated hooks.
 
 ### runtimeValidation
 
-**Type:** `Boolean`
+**Type:** `boolean | { strategy: 'throw' | 'both' }`
 **Default:** `false`
 
 Enable Zod runtime validation for Angular query responses. Requires `schemas: { type: 'zod' }`. When enabled, responses are validated via `Schema.parse()` in the RxJS pipeline. Skipped for primitive types and custom mutators.
 
+The boolean form is preserved for backward compatibility: `true` ≡ `{ strategy: 'throw' }`. With `{ strategy: 'both' }` an invalid response is first logged through `console.error('[orval] <operation> response validation failed', error)` with the raw `ZodError`, then re-thrown — so the failure still surfaces through the client's native error channel while giving production visibility into contract drift.
+
 ---
 
 ## override.swr
@@ -1668,7 +1670,7 @@ scope clearer.
 
 ### runtimeValidation
 
-**Type:** `Boolean`
+**Type:** `boolean | { strategy: 'throw' | 'both' }`
 **Default:** `false`
 
 Enable Zod runtime validation for Angular output. Requires
@@ -1679,6 +1681,13 @@ Enable Zod runtime validation for Angular output. Requires
 - For generated `httpResource` functions, eligible JSON resources receive a
   `parse: Schema.parse` option.
 
+The boolean form is preserved for backward compatibility: `true` ≡
+`{ strategy: 'throw' }`. With `{ strategy: 'both' }` an invalid response is first
+logged through `console.error('[orval] <operation> response validation failed', error)`
+with the raw `ZodError`, then re-thrown — so the failure still surfaces through
+the client's native error channel (RxJS error / `resource.error()` signal) while
+giving production visibility into contract drift.
+
 Validation is skipped for primitive types, non-JSON responses,
 `observe: 'events' | 'response'`, and custom mutator paths that bypass the
 generated validation flow.
@@ -1906,11 +1915,13 @@ Custom JSON reviver function (useful for date parsing).
 
 ### runtimeValidation
 
-**Type:** `Boolean`
+**Type:** `boolean | { strategy: 'throw' | 'both' }`
 **Default:** `false`
 
 Enable Zod runtime validation for fetch client responses. Requires `schemas: { type: 'zod' }`. When enabled, JSON responses are validated via `Schema.parse()` before being returned.
 
+The boolean form is preserved for backward compatibility: `true` ≡ `{ strategy: 'throw' }`. With `{ strategy: 'both' }` an invalid response is first logged through `console.error('[orval] <operation> response validation failed', error)` with the raw `ZodError`, then re-thrown (rejecting the returned promise) — giving production visibility into contract drift while still failing fast.
+
 ### arrayFormat
 
 **Type:** `'repeat' | 'brackets' | 'comma'`
@@ -2014,6 +2025,8 @@ export const load = async ({ fetch }) => {
 | `fetch` | `override.fetch.runtimeValidation` | ✅ | Validates JSON responses via `Schema.parse()` |
 | any client with custom mutator | varies | ⚠️ | Runtime validation may be bypassed depending on mutator path and signature (see [#2858](https://github.com/orval-labs/orval/issues/2858)) |
 
+All three supporting clients accept the object form `{ strategy: 'throw' | 'both' }`. `throw` (the default, equivalent to `true`) parses and throws; `both` additionally `console.error`s the raw `ZodError` before re-throwing, for production observability without giving up fail-fast behaviour.
+
 ---
 
 ## override.mock