[earakely-scale]

What and why

M8.14 (FD-4961): the default website browser is added to a multi env with sites, and signed in. #598 and M5.15 (#556) already built all of it, so this PR proves M8.14's "done when" on the code that shipped and adds no production code.

• Default browser (feat(multi): a multi env names its website browser (browser_envs), a browser computer on a sandbox of its own #598): a multi env with a site and no browser_envs gets the run's browser, website_browser_env_id, which resolves to the config's default_website_browser_env_id. Under a chromium default it deploys chromium unnamed, on a sandbox of its own. browser_envs = [] deploys none, and child_envs.chromium carries its settings, such as start_urls.
• Sign-in (feat(browser): browser_sign_in, and browser steps reach a multi env's computers (FD-4944) #556, decision D1a): the multi env doesn't sign in by itself. A browser_sign_in {site, user, browser?} step does, placed after the load and again after reset_env. Since feat(multi): a multi env names its website browser (browser_envs), a browser computer on a sandbox of its own #598, browser steps find a browser_envs browser computer.

Until now the default was tested only through the run override, and sign-in only on a desktop computer carrying a browser app, never on a browser computer the multi env added itself.

What changes

Tests only:

• Integration (browser_computer_test.py): under a config whose default website browser is the chromium computer, a multi env with a site that offers session names no browser and deploys chromium as its one computer child, with its start tab loaded at the site.
  • browser_sign_in signs it in as alex.
  • reset_env leaves it signed out.
  • A second browser_sign_in signs it in again.
  • The step's record names shop.test.
• Unit (test_multi_env_computers.py): without a run override, a multi env with websites gets the config's default browser, and browser_envs = [] still gets none.

How it was tested

• Unit: test_multi_env_computers.py's browser tests, 43 passed, the new one included.
• Integration, local Docker on an agent-environments-admin amd64 VM: the new test passes. Beside it, browser_computer_test.py -k multi_env, the five tests feat(multi): a multi env names its website browser (browser_envs), a browser computer on a sandbox of its own #598 added, passed 5 of 5 on the same VM.
  • The test's first run started chromium at /api/health, which this site doesn't serve. The deploy refused the 404 start tab, as designed, so it now starts at the site's /api/session.
• ruff check passes on both files.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Adds tests for a multi env that gets Chromium from the config default.

• Tests cover default-browser sign-in across resets.

_{Reviews (1) · Last reviewed commit: "test(multi): under a chromium default, a..." · Reviewed by Greptile}