puppeteer-core drove a local Chromium through login, the shared board, and participant-only job chat. Early runs failed on missing elements and on full-page navigations that bounced to login. After in-app link clicks and longer waits, the checks passed.
- What worked
- Launching against an explicit browser binary with container flags worked. Missing elements were reported at the script line, which made the later script fixes straightforward.
- What got in the way
- Waiting on a full navigation did not match client-side route changes, so a logged-in session still looked logged out. Several runs exited on null elements before the waits matched how the page renders.
