fix(lint): repair the three remaining parse errors on master

[Sensei-Victor]

fix(lint): remove duplicate vitest import in tests/csp.test.js

tests/csp.test.js imports { describe, it, expect } from 'vitest' twice — on line 1 and again on line 5:

1: import { describe, it, expect } from 'vitest';
2: import fs from 'fs';
3: import path from 'path';
4: import { fileURLToPath } from 'url';
5: import { describe, it, expect } from 'vitest';   // <- duplicate

ESLint rejects the file outright:

5:10  error  Parsing error: Identifier 'describe' has already been declared

Because the file does not parse, ESLint cannot check it and Vitest cannot transform it, so the whole file was silently excluded from both the lint result and the test run. Removing the duplicate import is the entire fix — no behaviour change.

Effect

pnpm exec eslint tests/csp.test.js   -> exit 0
pnpm exec vitest run tests/csp.test.js
  before:  0 tests collected (file could not be transformed)
  after:   Tests  8 passed (8)

Context

This is the last of master's parse errors that is not also a build blocker. pnpm run lint on master (a0c6c845) reports 10 errors:

Count	Kind	Fixed by
3	local/no-direct-submit … plus 5 more of the same	#1121
1	AuditLog.tsx unterminated JSX	#1108
1	tests/csp.test.js duplicate describe	this PR
5	other local/no-direct-submit	#1121

With all three PRs applied, pnpm run lint reports 0 errors and exits 0 — verified on a clean cherry-pick of all three onto master:

✖ 2260 problems (0 errors, 2260 warnings)
exit=0

Independence

One file, one deleted line. No overlap with #1108 or #1121; all three cherry-pick onto master cleanly together and merge in any order.

[vercel]

Someone is attempting to deploy a commit to the nanle-code's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

Hey @Sensei-Victor! 👋 It looks like this PR isn't linked to any issue.

If this PR is for one of the issues assigned to you as part of a Wave, please link it to ensure your contribution is tracked properly. You can do this by adding a keyword to the PR description (e.g., Closes #123), or by clicking a button below:

Issue	Title
#167	Auto-generate Soroban client bindings from contract spec	Link to this issue
#739	[2026 Hardening] Enforce type-checking as a required CI gate	Link to this issue

ℹ️ Learn more about linking PRs to issues