[marcinobel]

revcli auth closed the browser window as soon as Google Maps rendered, so it could never be used to sign in. The cause was an early return in authLoginCommand:

if (await isSignedIn(page)) {
  logger.success("Already signed in to Google Maps. No action needed.");
  return;   // -> finally { closeBrowser() }
}

Whenever the profile already held a session, the command declared "no action needed" about 4s after the map painted and shut the window — leaving revcli auth logout followed by revcli auth as the only way to sign in or switch accounts. That is backwards for the one command whose job is credential entry.

Changes

• src/commands/auth.ts — the early return is gone. The window now stays open either way: for credential entry when signed out, and for account switching when signed in. It closes when sign-in is detected, or when the user closes it.
• src/scraper/auth.ts — waitForSignIn() returns SignInOutcome ("signed-in" | "browser-closed") instead of void, so each caller states its closed-window policy: fatal for waitForUserAuth(), because a scrape cannot continue without a session, but a normal end for auth. New waitForBrowserClose() covers the signed-in case, polling pages() as well as the context close event — closing the last window on macOS leaves the process, and therefore the context, alive.
• tests/auth.test.ts — 10 new cases (287 → 297) pinning both end states of each waiter. waitForBrowserClose() takes the narrow structural ClosableBrowser rather than a BrowserContext, so it is testable against a fake with no browser.
• AGENTS.md, README.md, CHANGELOG.md — the test count, the auth-flow description, and the documented auth behaviour.

Also fixed

The 5-minute timeout threw out of an async Commander action. program.parse() does not await action handlers, so it surfaced as an unhandled rejection with a raw stack trace. It now reports the timeout and exits 1 cleanly.

Verified

• Reproduced on the installed 0.1.4 before the fix: revcli auth printed "Already signed in to Google Maps. No action needed." and closed 4s after the map loaded.
• After the fix, on the real command: still running after 12s; the CLI exited ~2s after the window was closed, logging ✔ Browser closed. Google session saved for later runs. with exit code 0 and no stack trace.
• The signed-out path was exercised in a throwaway profile: the browser stays open and polls, so the wait loop itself was never the problem.
• npm run typecheck, npm test (297 passed), npm run build, npm run check:pack, npm run test:package — all green locally.

Note

This machine's profile already holds a valid session (cookies good to 2027-10-22), so revcli auth now opens the window and waits to be closed; switching accounts means signing out inside that window first.