User mode on a wand-owned profile directory #47

Parent

Spec: #33 (Baseline release). Section numbers refer to its Implementation Decisions.

What to build

NewUserMode() launches a visible branded Chrome 136 or later successfully, on a persistent profile wand owns, so logins and extensions survive between runs; the first Confirmed fix, with a test that fails on the Snapshot. Spec section 8; ADR-0010; ticket #15.

Acceptance criteria

• NewUserMode() defaults --user-data-dir to os.UserConfigDir()/wand/user-mode, created if missing; UserDataDir() overrides it; a flag-set unit test asserts both.
• A launch test against the branded Google Chrome found by discovery on ubuntu-latest (under xvfb), windows-latest and macos-latest: launches, connects, closes; skipped with a reason where no branded Chrome exists (ubuntu-24.04-arm). It runs on the current Gate.
• The same launch test run against the Snapshot fails with Chrome's refusal; the PR records that run.
• The guard stays off by default in User mode.

Blocked by

• Minimal Gate on linux/amd64 with 100 % coverage and the main ruleset #36 (Minimal Gate on linux/amd64 with 100 % coverage and the main ruleset)