lib/fix.js ---------------------------------------- `gen-comments --lint --fix`'s engine. Rewrites EXISTING, malformed JSDoc blocks to resolve lintModule()'s findings — it does not add JSDoc to undocumented symbols (that's `--write`'s job; a require-jsdoc finding with no existing block at all is left alone here). Two fix strategies, matched to two kinds of symbol (see docs/backlog/adr-013-lint-autofix.md for the full reasoning): 1. Function-like symbols (functions, methods, constructors) — the whole block is REBUILT from real AST truth (actual param names/order/types, actual return type) merged with whatever valid prose already existed. This one rebuild naturally fixes require-param, require-param-description, check-param-names (ordering), require-returns, require-returns-description, require-returns-check, require-description, empty-tags, and no-multi-asterisks/no-blank-block-descriptions in a single pass — a symbol with zero lint issues is left completely untouched (byte-identical). 2. Generic symbols (classes, interfaces, typeAliases, enums, variables, getters, setters, properties) — a lighter, line-level fix: strip trailing text after a no-description tag, collapse stray asterisks, insert one placeholder description line if the block is blank or has none. No attempt to rebuild @property/@enum-style tag lists — those aren't lint-checked today and rebuilding them risks losing real content. One deliberate carve-out, in both strategies: `check-tag-names` (an unknown / typo'd tag) is NEVER auto-fixed. Every other fix here either applies a fixed, deterministic placeholder template (never invented prose) or performs a lossless mechanical transform (reorder, strip, collapse). Renaming a typo'd tag would mean guessing what the author meant to type — there is no safe default for that, so `check-tag-names` findings always survive a `--fix` run and are reported as such.