fix(test): stop a failing screen-family check orphaning its browser

probe-fams.mjs had no try/finally, so a throw skipped chrome.kill() and left the headless browser alive on its port. The next run connected to that survivor and reported results from a stale page: old widgets.js, chips already clicked. It cost me a debug loop today, insisting a card's default ink was green and another's chips were missing, neither of which was true of the page on disk.

A probe that answers from the previous run is worse than one that crashes. Its two siblings already had the guard.

0 files changed, 0 insertions, 0 deletions