[bercedev]

Fixes #1243

the generated .d.ts had // @ts-nocheck before /* eslint-disable */, so a lint rule that flags @ts-nocheck (like @typescript-eslint/ban-ts-comment) still reported that line. the two lines are swapped now, so eslint is off before it.

@ts-nocheck still works there, ts reads it from any of the leading comments (the autogenerated banner was already above it). checked with tsc --strict on a file with that header and a type error: no errors reported.

added a check to the existing generateTsTypesSrc output test that the eslint-disable line comes first; it fails on main.

[pullfrog]

✅ No new issues found.

Reviewed changes Reviewed the generated TypeScript header fix and its regression coverage for #1243.

• Comment ordering: Moves /* eslint-disable */ before // @ts-nocheck, preventing @typescript-eslint/ban-ts-comment from reporting the generated directive while preserving TypeScript suppression.
• Regression coverage: Adds assertions that both directives are present and ordered correctly. All 94 focused type-generation tests passed; the build, changed-file lint, and direct ESLint/TypeScript behavior probes also passed.
• Release entry: Includes a varlock patch entry describing the generated-file lint fix.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}