wyuc fb4ce5341c
fix(619): keep-alive e2e aligns with #777 edit-mode visibility (+ pi-ai server-external) (#781)
* fix(agent): mark pi-ai/pi-agent-core server-external to fix #619 e2e

The editor-agent packages `@earendil-works/pi-ai` and `pi-agent-core` lazily
load node builtins via a computed `import(specifier)` (deliberately, to avoid
breaking browser/Vite builds). webpack cannot statically analyze that, so once
these run on the server (the Pro-mode "Edit with AI" path) the bundled form
throws `Cannot find module as expression is too dynamic` as an unhandled
rejection. That broke the #619 interactive-iframe keep-alive e2e: entering Pro
mode no longer settled, so the keep-alive iframe stayed visible
(`interactive-iframe-keepalive-619.spec.ts:189` expected hidden).

Add both packages to `serverExternalPackages` so Next loads them natively and
their dynamic import resolves as a real Node call.

Refs #619, #777.

* test(619): interactive iframe stays visible in edit mode since #777

#777 intentionally dropped the `mode !== 'edit'` guard in InteractiveIframeHost
so the interactive iframe stays visible during Pro-mode editing — the editor
agent ("Edit with AI") fixes interactive HTML, so the teacher must see the live
page while editing. The keep-alive e2e was still asserting the old "hidden in
edit mode" behavior (toBeHidden at line 189) and so failed on every run since
#777 landed.

Update Trigger A to the new contract: after the Pro-mode toggle the iframe is
visible and its in-iframe counter state is preserved (the real keep-alive
proof — neither unmounted nor reloaded). Trigger B (scene switch to a slide)
still hides it via ownership release, unchanged.

Refs #619, #777.
2026-06-24 14:39:21 +08:00
..