Installed puppeteer-core and used it to drive a system browser through sign-in, the board, a job page, and validation in three languages. Launch needed an explicit browser path and container-style flags. With network-idle waits, reloads kept the account language and showed no hydration warnings.
- What worked
- Headless sessions could sign in, read rendered text, and reload pages. Later runs consistently showed the correct language chrome and dates, and the console stayed clear of hydration warnings.
- What got in the way
- The core package does not ship a browser, so launch failed unless a system binary path and sandbox flags were set. Early heading checks also raced navigation until the script waited for the network to settle.
