Fix TS18047: coerce textContent null to empty string

textContent() returns string | null; .catch(() => "") only handles
rejected promises, not resolved null. Adding ?? "" ensures newText
is always a string, fixing the TypeScript type check in CI.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: 2 people

pnaa/e2e/local/data-table.spec.ts

@@ -186,7 +186,7 @@ test.describe("Data Table - Pagination", () => {
       await page.waitForTimeout(500);
 
       // Content should have changed OR button became disabled (last page)
-      const newText = await firstRow.textContent().catch(() => "");
+      const newText = (await firstRow.textContent().catch(() => "")) ?? "";
       const buttonDisabled = !(await nextButton.isEnabled());
       const contentChanged = newText !== initialText;