What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	14856
title	E2E: LivePreview Learn-route popout cannot find live preview across build modes
state	Open
labels	bugaitestingregression
assignees	[]
createdAt	5:35 PM
updatedAt	5:35 PM
githubUrl	https://github.com/neomjs/neo/issues/14856
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

E2E: LivePreview Learn-route popout cannot find live preview across build modes

Open Backlog/active-chunk-4 bugaitestingregression

neo-gpt commented on 5:35 PM

Problem

The LivePreview multi-window E2E matrix fails every Learn-route / FormsEngine popout variant across Dev, Dist Dev, and Dist Prod. The Home-route Helix popout still passes in each environment, so the breakage is route/content specific rather than a total LivePreview or popup outage.

Evidence

Verified on dev at merge commit ecbb21cde9a72f40f7a6c7132baedecd25db6bdd after PR #14849 merged.

Command run:

./node_modules/.bin/playwright test -c tmp/e2e-full-8097.config.mjs

The temporary config matched the E2E config but used http://localhost:8097 with reuseExistingServer: false, because port 8080 was already occupied by another Neo checkout.

Suite result: 73 tests run, 56 passed, 17 failed.

Failure family: all failing LivePreview cases time out waiting for .neo-code-live-preview to be visible.

Dev failures:

test/playwright/e2e/rendering/LivePreviewMultiWindow.spec.mjs:84: Popout LivePreview from Learn Route (FormsEngine).
test/playwright/e2e/rendering/LivePreviewMultiWindow.spec.mjs:89: Sequential Route: Home -> Learn -> Popout.
test/playwright/e2e/rendering/LivePreviewMultiWindow.spec.mjs:105: Sequential Route: Learn -> Home -> Popout.

Dist Dev failures:

Same three Learn-route / Learn-sequence variants failed.

Dist Prod failures:

Same three Learn-route / Learn-sequence variants failed.

Controls that passed in the same run:

Popout LivePreview from Home Route (Helix) passed in Dev, Dist Dev, and Dist Prod.
Later rendering specs MarkdownStreamingCoherenceNL.spec.mjs passed.

Acceptance Criteria

The Learn / FormsEngine route exposes a .neo-code-live-preview target when the test reaches it, or the E2E route fixture is updated to a current Learn page that intentionally contains a live preview.
Sequential Home -> Learn and Learn -> Home route flows preserve the live-preview popout affordance across Dev, Dist Dev, and Dist Prod.
Home-route Helix coverage stays green.
Focused rerun passes:

./node_modules/.bin/playwright test -c test/playwright/playwright.config.e2e.mjs test/playwright/e2e/rendering/LivePreviewMultiWindow.spec.mjs

Duplicate Sweep

Latest 30 open issues checked: no matching open ticket.
Targeted GitHub search checked: LivePreviewMultiWindow FormsEngine Learn Route live preview popout returned no open issues.
Local synced issue/discussion cache checked for LivePreviewMultiWindow and FormsEngine; hits were historical/archived context for the original coverage and docs pages, not an open active duplicate.