pj 557bd9d815 fix(chrome): honor the caller context in Launch ...

Launch and clearState ran against d.tabCtx, so a target that accepts the
connection and never answers wedged the process past its own --duration and
through SIGTERM, needing SIGKILL. Unattended that is a campaign worker lost for
the rest of the sweep with no diagnostic.

The browser is still allocated against d.tabCtx first, because chromedp starts
Chrome under whichever context calls Run first and allocating under a caller
deadline would kill the browser when Launch returns. Everything after
allocation goes through runCtx.

Claude-Session: https://claude.ai/code/session_01A5KmftdEJ49A9z5mF5ESrX

2026-08-12 21:38:09 +05:30

..

testdata

test(chrome): compare the facts both hosts derive from one DOM

2026-08-12 20:42:52 +05:30

driver_test.go

fix(chrome): honor the caller context in Launch

2026-08-12 21:38:09 +05:30

driver.go

fix(chrome): honor the caller context in Launch

2026-08-12 21:38:09 +05:30

fact_parity_test.go

test(chrome): compare the facts both hosts derive from one DOM

2026-08-12 20:42:52 +05:30

launch_test.go

fix ltl semantics and unify action enumeration (#71)

2026-08-12 18:06:04 +05:30

translate_test.go

fix ltl semantics and unify action enumeration (#71)

2026-08-12 18:06:04 +05:30

translate.go

style: remove every em-dash and en-dash

2026-08-12 20:48:33 +05:30