Unskip 14 passing formatting fourslash tests

[Copilot]

These 14 formatting tests were skipped but now pass consistently after recent formatter fixes in #2793 and #2852.

Root cause

The tests exercised three bugs in internal/format/span.go, all now fixed:

• lastIndentedLine zero-value bug (Fixed a formatting crash on comments inside blocks starting on first line #2793): Go zero-value 0 matched line 0 in computeIndentation, returning -1 indentation. Fixed by initializing to -1.
• Always-truthy list guard (Fixed an always-truthy condition in span.go (porting bug) #2852): listStartToken != -1 was always true since ast.Kind uses 0 (KindUnknown), not -1. Fixed to compare against ast.KindUnknown.
• Reparsed node crash (Fixed a formatting crash on comments inside blocks starting on first line #2793): Formatter panicked on reparsed JSDoc nodes. Fixed by adding child.Flags&ast.NodeFlagsReparsed != 0 guard in processChildNode.

Potential race (not confirmed)

warmAutoImportCache runs in a background goroutine and calls getSnapshot → flushChanges, which drains pendingFileChanges. The dispatch loop does the same for formatting requests. If the background task runs between a didChange being queued and the formatting request's getSnapshot, it could drain the change first. The snapshot ends up correct either way, but goroutine scheduling determines who flushes. Unable to reproduce flakiness despite 200+ runs with race detector, stress conditions, and full suite repetition.

Changes

• Removed 14 test names from internal/fourslash/_scripts/failingTests.txt

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.