Task/update playwright logic

[JERotter]

This PR includes updates to:

scrape.ts -
const link = page.locator('[href*="/Report/${type}?"]');

was updated to

const docketRow = page.locator('tr:has-text("${docketNum}")');
const link = docketRow.locator('[href*="/Report/${type}?"]').first();
to address a 'Resolved to 2 elements' error.

scrape.ts, type.ts and serialize.ts -
were updated to return the summary and docket URLs. The URLs we need include a dnh value that cannot be derived deterministically from the docket number — it’s generated and owned by the upstream system. To ensure our links remain accurate and resilient to system changes, we fetch the full URLs directly from the API instead of trying to reconstruct them client-side. This makes the automation future-proof and guarantees we always link to the correct court records.

CourtDataExcelScript.ts -
Added an Excel Office Script that invokes the scrAPI lambda and pulls data into the spreadsheets.

CourtDataExcelScript.ts:

🔹 Reads input
Takes docket numbers from the currently active worksheet (column A, rows 2–100)

🔹 Calls backend APIs
For each docket number:
Calls Summary API → returns defendant details + case and charge metadata
Calls Docket API → returns financial balance and payment info

🔹 Extracts and normalizes data
Parses full legal names into First / Middle / Last columns
Handles multiple cases, charges, and sentences per docket
Avoids null/undefined issues with safe fallbacks

🔹 Writes structured output into new worksheets
It creates and populates these tabs:

Sheet	Data Stored
Person Info	Identifiers, name (parsed), demographics, address, aliases
Cases	Case status, judge, arrest/disp dates, charge count
Charges	Statutes, grades, dispositions, sentence details
Financial Info	Balances, assessments, payments, adjustments
Links	JSON data, Clickable URLs to court summary & docket sheets

🔹 Adds interactive URL links
Summary and Docket hyperlinks for the first docket entry
Raw JSON data & links to allow auditors/devs to inspect the unprocessed API response directly

🔹 Performance and reliability features
Includes throttling (150ms delay) to avoid API rate limits
Includes error handling so one failed docket does not stop the entire run
Cleans prior data before writing fresh output

[jackmanleydev]

Looks like a good start. Walked through a potential refactoring options for the excel script and examples of what that could look like. Holding off on going down that path until we get feedback from stakeholders, because most of that code could change if they want the data in a specific format.

[drak72]

Hardcoding isn't...great overall.
Let's at least put a DNS name on top of this longer term. Will go through that process with PE.