fix(page-controller): index new (*-prefixed) elements in getElementTextMap

[JOhnsonKC201]

Problem

getElementTextMap (packages/page-controller/src/dom/index.ts) builds the index → line map that PageController uses to echo a descriptive result for clickElement / inputText. It matched interactive lines with:

/^\[(\d+)\]<[^>]+>([^<]*)/

But flatTreeToString renders new elements with a leading *:

const highlightIndicator = node.isNew ? `*[${node.highlightIndex}]` : `[${node.highlightIndex}]`

which the system prompt documents ("Elements tagged with *[ are the new clickable elements"). The ^\[ anchor never matches a *[...] line, so:

• new elements (dropdown options, freshly-rendered modals, etc.) get no entry, and
• on the first updateTree() every element is new, so the map is empty entirely.

PageController then falls back to the bare index — Clicked element (5). instead of Clicked element (*[5]<a role=button>Get started />). — losing traceability for exactly the elements the agent most often acts on, and for the whole first extraction.

Fix

Allow an optional leading * in the regex (/^\*?\[(\d+)\]<[^>]+>([^<]*)/). Existing (non-*) lines are unchanged, and plain text still can't match because the [i]<…> structure is still required.

Tests

Adds packages/page-controller/src/dom/index.test.ts covering the existing-element, new-element (*-prefixed), and indented cases. npm test passes across all packages; typecheck and eslint are clean.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}