test(tag-widget-flake): isolate smoke.spec.ts:2010 with per-test URL and key
The 'tags page widget updates dynamically when tag is added via command'
test was an ordering flake. It passed in isolation but failed in the
full suite after ~148 prior tests. Root cause was state leaking onto
the Command Execution describe's shared page window (key
cmd-exec-test-page, URL https://cmd-exec-test-TIMESTAMP.example.com).
The prior tests (1, 3, 4 in the describe) tag and create items against
the shared window. page.js inside that shared window carries a live
tag:item-added subscriber and a currentItemId that was bound to an
earlier item. When test 2010 runs a fresh tag command and waits for
the widget to update, loadTagsForCurrentPage queries tags for the
stale currentItemId, not for the item the new setupTag command
actually tagged.
Fix: give test 2010 its own page window. Close the shared one, open
a fresh one at a unique URL and key, run all assertions against that
isolated window, then in a finally close it and reopen the shared
window so subsequent tests and afterAll see the expected state.
No production code changed. No assertions weakened.
Command Execution describe: 8/8 pass after the fix.
Full-suite verification: the test passed in isolation before this
change too — value is in the full-suite order, which takes ~5 min
to run. Pending that confirmation run.