fix(docs): correct plugin doc claims that contradict the source code

[stijnvanhulle]

🎯 Changes

A docs validation audit checking documentation pages against the actual kubb and plugins source. Two groups of fixes, each confirmed against the code.

1. Individual factual errors

• plugin-react-query — suspense-hooks recipe: said suspense is "on by default"; it defaults to false (plugin.ts, types.ts, and the options reference). Reworded.
• plugin-react-query — infinite-scroll recipe: the config omitted hooks: true, so it would generate no file at all — infiniteQueryGenerator returns null when hooks is false. Added hooks: true.
• plugin-zod — options reference: the output.mode table listed the default as 'directory', contradicting the prose above it and core (output.mode ?? 'file'). Corrected to 'file'.
• plugin-zod — options reference: the ResolverZodPatch example annotated the grouped param.path / param.query / param.headers methods with individual-parameter names. Corrected to the grouped schema names the resolver returns (deletePetPathSchema, findPetsByStatusQuerySchema, deletePetHeadersSchema).
• plugin-zod — prefix-every-schema-type-name recipe: said the schema constant is renamed via resolver.schema.type; it is named by the top-level resolver.name. Corrected the caveat.
• plugin-fetch — index: the feature list linked #validator and #sdk as same-page anchors, but those headings live on the options reference page. Pointed both at /plugins/plugin-fetch/reference/options#….

2. Systemic: recipes showed per-file output without output.mode: 'directory'

Every plugin's output.mode defaults to 'file', which writes all generated code into one file at output.path (definePlugin.ts output.mode ?? 'file'; Resolver.ts returns output.path directly for any non-directory mode). Per-operation / per-schema layout (e.g. src/gen/zod/petSchema.ts) only happens under output.mode: 'directory', which every working example project sets.

33 recipe configs showed that per-file layout but never set the mode, so following them literally produced one merged file instead of the files shown. Added output: { path: '<plugin default>', mode: 'directory' } to the plugin whose output each recipe illustrates, matching the example projects.

Audit coverage: verified plugin option/recipe pages for the 12 published plugins plus the adapter-oas, parser-ts, parser-md, diagnostics (index + 20 codes), and configuration reference pages (all of which validated clean). One residual nuance is left for a follow-up: in the query recipes the generated hook files import per-operation client/type paths, so a fully byte-accurate reproduction would also set mode: 'directory' on the dependency pluginFetch() / pluginTs() calls, not only the subject plugin.

✅ Checklist

• I have followed the steps in the Contributing guide.
• I am using USA English (serialize, color, center, canceled, analyze, license).
• I ran the humanizer check on any new documentation I wrote.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SCPrdJtFTDnWFxJtzpbt6i

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0682be8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR