Browser foundation — open your eyes before you work

Every autonomous loop here drives one shared, logged-in Chromium over CDP :9222
(profile ~/.cloak/profiles/daily-driver). That browser is the single point of failure for the
whole business: when it dies, every loop goes blind and keeps "running" while doing nothing.

This actually happened (2026-07-13): Chromium died from memory pressure, the gig loop kept waking up
hourly for twelve hours and accomplished nothing, and the only recovery lived outside the loop in a
guard that fired once and gave up.

Self-healing belongs inside the loop. Call this at the top of every pass, before any browser step.

Call this first, every pass

bash $LIFE_MANAGER_REPO/skills/browser/ensure_browser.sh          # ALIVE | RECOVERED | FAILED
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/cdp_tab_gc.py   # close the tabs the last pass left behind

If ensure_browser.sh prints FAILED, do not hang or retry forever — skip the browser steps,
run whatever file-only work the pass can still do, and report the failure honestly.

What each piece is for

python3 $LIFE_MANAGER_REPO/skills/browser/scripts/session_vault.py dump      # snapshot logins (cookies + localStorage)
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/session_vault.py restore   # push them back into the browser
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/session_vault.py status    # how many cookies, which origins, how old
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/session_vault.py keepalive https://coconala.com/mypage/dashboard  # warm + detect logout
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/session_vault.py totp @coconala   # fresh 2FA code from stored secret

Run dump right after any fresh login, so that login is banked forever.

Staying logged in with ZERO human — the re-login ladder every loop follows

"Logged out" must never reach a human (a Telegram asking Dais to log in does not scale to hundreds of
accounts). When a page redirects to /login, the loop climbs this ladder itself, in order, and only
records a report — it never waits for a person:

1. session_vault.py restore            # push the banked cookies + localStorage back
2. session_vault.py keepalive <authed-url>   # still logged out?
3. still out → self-login with the account's OWN credentials:
     email + password (from env)  →  if 2FA asked: session_vault.py totp @<service>
   ★ Every earn account is created with an AI-owned email + app-based 2FA (TOTP secret stored in
     ~/.cloak/vault/daily-driver/totp-secrets.json, chmod 600). NEVER Dais's Google/passkey account —
     passkey and SMS-2FA cannot be finished by a machine. ★
4. only if all of the above fail: append a one-line report and run the file-only path. Do NOT block on a human.

The profile itself (--user-data-dir, never deleted, caches capped) is what keeps you logged in 99%
of the time; the ladder is for the rare server-side expiry. To cut expiry frequency: keep the profile,
keep a stable fingerprint, and (at scale) pin a sticky proxy per account.

Rules for browser loops

• Never launch your own Chromium and never point at your own --user-data-dir. One browser, one
  profile. A second profile means a second set of logins, which means a human logging in twice.
• Never close a tab you did not open, and never kill the browser to "reset" it — that throws away
  everyone else's work. Use the tab GC.
• Close what you open. Tabs are the leak that kills the browser.
• Caches are capped at launch (--disk-cache-size, cache dir under /tmp). An uncapped profile grew
  to 1.0GB, 97% of it disposable cache, and filled the disk the loops write their ledgers to.

Lease your own space — never share a tab with another loop

Loops used to share one tab space, so a navigate from clip would destroy the form gig was halfway
through filling, and neither could tell. Take a context instead: CDP Target.createBrowserContext is
"Similar to an incognito profile but you can have more than one", and nothing outside your context can
reach into it.

LEASE=$(AI_BROWSER_HOLDER_PID=$$ python3 $LIFE_MANAGER_REPO/skills/browser/scripts/cdp_context_lease.py acquire gig)   # your own space
WS=$(echo "$LEASE" | python3 -c 'import sys,json;print(json.load(sys.stdin)["ws"])') # drive this tab
# ... do the work over $WS ...
python3 $LIFE_MANAGER_REPO/skills/browser/scripts/cdp_context_lease.py release gig            # tabs die with it

A fresh context starts logged out, so acquire seeds it from the vault's cookies — verified live:
a leased context reaches coconala.com/mypage/dashboard already authenticated. A loop killed with -9
never releases, so run cdp_context_lease.py gc --idle-min 45 from the healthcheck to reap what it
left holding.

Rules: one context per task, always release when done, never touch another task's context.

TikTok authenticated identity readback

Do not infer authentication from page body text or a public /@handle URL. Under the
registered identity lease, use the shared adapter; it verifies the official navigation's
own-profile link, rejects a different signed-in identity, and closes only its owned tab.

bash skills/browser/with-browser.sh tiktok-anicca-jp -- \
  python3 skills/browser/scripts/tiktok_identity_readback.py \
  --expected-handle @anicca.jp --owner paid-tiktok-readback

Exit 0 means the expected identity is authenticated. Exit 2 means logged out,
indeterminate, or a different identity; consume its JSON status as an exact retry blocker.

For fresh candidate discovery, use the shared official user-search reader under the same
registered identity. It returns profile URLs only; the model still decides eligibility from
each official profile and excludes prior effect keys before sending.

bash skills/browser/with-browser.sh tiktok-anicca-jp -- \
  python3 skills/browser/scripts/tiktok_user_search.py "社会人 日常" \
  --owner paid-tiktok-search --output /absolute/project-owned/search.json

Google Sheets bookkeeping

Use the installed authenticated gog sheets API CLI before browser automation. API
authentication does not require a registered browser identity, so a browser resource
resolver miss is not evidence that Sheets is unavailable.

For an append effect: read the target range first and reject a duplicate key, append one
exact row, atomically preserve the JSON response, then gog sheets get the response's
exact updatedRange. Only matching returned values are an official effect readback.
Never count an append request, selected cell, or browser draft as a recorded row.