fix(test): remove duplicate taskToIssuePayload import

[Arthur742Ramos]

Why

test/issues-coverage.test.ts imports taskToIssuePayload twice — once at the top of the file, once mid-file alongside generateIssuePreview:

// Top of file (line 2)
import { createIssuesFromTasks, taskToIssuePayload } from "../src/issues.js";

// ...

// Mid-file (line 74)
import { taskToIssuePayload, generateIssuePreview } from "../src/issues.js";

The current esbuild/vitest pinned in main tolerates this silently. Stricter versions reject it as a parse error:

[PARSE_ERROR] Error: Identifier `taskToIssuePayload` has already been declared

This already blocks the open Dependabot dev-dependencies bump (#28), where the new esbuild/vitest combo surfaces it as a hard CI failure on Node 22. Will also block any future major bump of esbuild, vitest, or @vitest/coverage-v8.

What changes

Consolidate to a single top-of-file import that includes generateIssuePreview. Drop the redundant mid-file import.

-import { createIssuesFromTasks, taskToIssuePayload } from "../src/issues.js";
+import { createIssuesFromTasks, generateIssuePreview, taskToIssuePayload } from "../src/issues.js";

-// Additional branch coverage for issues.ts
-import { taskToIssuePayload, generateIssuePreview } from "../src/issues.js";
+// Additional branch coverage for issues.ts (using imports declared at the top)

Validation

• 11/11 tests in the affected file pass.
• 985/985 unit tests pass overall.
• typecheck, lint clean.

No behavior change — same symbols are imported from the same module, just deduplicated.

Follow-up

Once this lands, I'll trigger a Dependabot rebase on #28 (dev-deps bump). With this fix in place, the bump should go from FAILURE to CLEAN.