browser-repro-ui-triage

To triage a browser UI bug, systematically reproduce the issue in-browser, capture deterministic repro steps, collect DevTools evidence like console logs and network traces, and pin the responsible layer for routing to the correct fix.

Finding if a visual glitch is caused by client state or an API contract issue requires in-browser triage that captures network traces and console logs to isolate the symptom across UI, client state, auth/session, network, API contract, backend behavior, or deployment/config drift.

Capture deterministic repro steps and browser evidence for a broken frontend interaction by reproducing the issue systematically, documenting exact user actions, and recording visual screenshots, console logs, and network traces for diagnostic context.

This triage process is not intended for backend-first incidents or repro-pack packaging, but it does diagnose deployment/config drift when it manifests as a browser-visible symptom with an unclear root cause before escalation.

You should not use browser UI triage for blank screens when the root cause is already known as a backend-first incident, or when you need repro-pack packaging instead of first-pass visual triage and layer routing.

Routing a blank screen symptom to the correct fix requires diagnostic data including deterministic repro steps, browser evidence such as screenshots and network traces, and explicit context to identify whether the UI, auth/session, or network layer is responsible.