Preserve ts-check across reference directives

[Copilot]

// @ts-check was being overridden by later triple-slash reference pragmas, causing checked files to be treated like ts-nocheck. This affected JS and TS files when a reference directive followed the check directive.

• Parser directive handling

  • Limit check-mode selection to ts-check / ts-nocheck pragmas.
  • Preserve existing “last check directive wins” behavior without letting reference pragmas participate.

• Regression coverage

  • Add a compiler test covering @ts-check followed by /// <reference lib="dom" /> in both .ts and .js inputs.

// @ts-check
/// <reference lib="dom" />

let a = "";
a = 1; // still reports TS2322

[Copilot]

Pull request overview

Fixes a parser bug where // @ts-check could be overridden by subsequent triple-slash reference pragmas, because the inner loop in processPragmasIntoFields iterated over all pragmas (not just check directives) and set Enabled based on whether each pragma's name was "ts-check". The fix removes the redundant inner loop, relying on the outer switch's ts-check/ts-nocheck case to provide the correct pragma.

Changes:

• Replace the inner pragma loop with direct use of the current pragma in the ts-check/ts-nocheck case.
• Add a regression compiler test covering .ts and .js files with @ts-check followed by /// <reference lib="dom" />.
• Add the corresponding errors baseline.

Show a summary per file

File	Description
internal/parser/parser.go	Fix CheckJsDirective resolution to use only the current ts-check/ts-nocheck pragma.
testdata/tests/cases/compiler/tsCheckPreservedAfterReference.ts	New regression test for both TS and JS files.
testdata/baselines/reference/compiler/tsCheckPreservedAfterReference.errors.txt	Expected TS2322 baseline for the regression test.

Copilot's findings

• Files reviewed: 3/3 changed files
• Comments generated: 0