document-touched-code

Add JSDoc blocks to named functions, class methods, exported helpers, and reusable local helpers, documenting parameters and return values. Skip short anonymous callbacks that only serve as local wiring, since documenting them adds noise without value.

Comments should explain why a non-obvious block of code exists, not narrate what each obvious line does. When refactoring, prefer deleting stale comments over preserving guidance that no longer matches the code.

Yes, route or middleware inline handlers that contain real logic should be documented immediately above their registration. Handlers that are only trivial wiring do not need comments.

Avoid commenting short anonymous callbacks used only as local wiring and obvious statements that restate what the code already says. Excessive narration of self-evident lines creates maintenance burden and visual noise.

Yes, the standards include Event Hub conventions: MySQL helpers document centralized SQL behavior, render helpers document template-variable safety and falsy handling, and frontend model facades document the endpoint family they own.