experiments in a post-browser web
test(websearch-cmd): rewrite lazy-load comment for v2 dispatch hook path
Stale comment described the deleted v1 path (loadLazyExtension /
handleLazyExtensionReady / lazy-stub iframe). Replace with the
actual current path: tile-lazy.ts pre-publish dispatch hook →
launchTile → tile-lifecycle ready signal.
(Job 2 of the v1-removal cleanup: loadLazyExtension itself was
deleted in the prior commit alongside the rest of the v1 lazy
machinery, since it was only ever a no-op stub called from now-
deleted code. No FSM bookkeeping needed to migrate.)
+4
-4
+4
-4
tests/desktop-serial/websearch-cmd.spec.ts
+4
-4
tests/desktop-serial/websearch-cmd.spec.ts
···
159
159
await cmdWindow.keyboard.press('Enter');
160
160
161
161
// Wait for the command to complete.
162
-
// The full path is: stub intercepts → loadLazyExtension → iframe created →
163
-
// extension init() → ext:ready → handleLazyExtensionReady (assert-and-trust) →
164
-
// callbacks resolve → stub replays message → command executes → result published
165
-
// This should complete well within 20s even with the extension loading overhead.
162
+
// The full path is: tile-lazy dispatch hook intercepts cmd:execute →
163
+
// launchTile() → tile boot → tile-lifecycle ready signal → hook resumes
164
+
// delivery → tile's real handler runs → result published.
165
+
// This should complete well within 20s even with the tile load overhead.
166
166
const executionResult = await cmdWindow.waitForFunction(
167
167
() => {
168
168
const state = (window as any)._cmdState;