Clear the lint backlog and refresh dependencies

[maxholman]

12 commits on top of e4021ae. No behaviour change to the generator: the fixtures and snapshots are untouched.

Lint: 275 warnings to 29, 0 errors

196 of the 275 were comment-rule warnings, spread across 105 comments.

• Deleted commented-out jsdoc and enum experiments that nothing read
• Reworded comments to the shared prose rules, and collapsed the comment above each private declaration to one line
• Where that one-line budget had no room for a reason (why deepObject normalises its explode, why int64 maps to bigint, what RFC 3339 adds over ISO 8601), the reason moved into the function body rather than being dropped
• Replaced casts that were standing in for guards: a type predicate for query style, a $ref check for parameter schemas, Array.isArray for the CLI tags. The casts that remain sit at a boundary the checker cannot see and now carry a TYPESAFETY: reason
• Dropped return annotations that inference already gives. Three stay: QueryParamSpec | undefined, [string, string] and WriterFunction supply the contextual type over an object literal, and removing them widens the literal properties and fails the build
• Manifest revisions build from one pass over the files, so the writes no longer await in sequence
• typedEntries keeps the middleware target keys through Object.entries

Tests

The regression tests fell back to "" when a type alias or regex match was absent, which let a later toContain pass for the wrong reason. They now fail with the name of what the generator did not emit.

Build

• @types/node to 26.6.1, type-fest to 5.10.0
• Dropped three @ts-expect-error workarounds. @types/node 26.6.1 depends on undici-types ~8.9.0, which is the condition their own comments named, and tsc reports all three as unused
• Pruned an expired release-age exclusion. @block65/rest-client was listed without a version, which exempts every future release; the entry was 16 days stale and named 14.0.0 while the tree resolves 14.0.1. minimumReleaseAgeExcludePrune now drops an entry once its version ages out

Not done

14 warnings remain in the processOpenApiDocument size cluster: 1097 lines, 238 statements, complexity 187. Splitting it is a separate change and wants its own review. Two no-filled-object-literal warnings in valibot.ts sit inside that same function and need the same restructure.

Verification

make typecheck clean, 40/40 tests, 0 lint errors, 29 warnings. Regenerating pnpm-lock.yaml from scratch reproduces it byte for byte, so no resolution depended on the exclusion that went.