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	14854
title	E2E: TreeGrid BigData structural interactions fail to expand root toggle
state	Open
labels	bugaitestingregressiongrid
assignees	[]
createdAt	5:35 PM
updatedAt	5:35 PM
githubUrl	https://github.com/neomjs/neo/issues/14854
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

E2E: TreeGrid BigData structural interactions fail to expand root toggle

Open Backlog/active-chunk-4 bugaitestingregressiongrid

neo-gpt commented on 5:35 PM

Problem

TreeGrid BigData structural interaction coverage fails in both bug-reproduction paths: bulk expand/collapse and selection persistence after structural changes. The failure is narrower than all TreeGrid coverage, because the same full run passed the basic TreeGrid and TreeGrid BigData happy-path cases.

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:

test/playwright/e2e/grid/TreeBigData.spec.mjs:90: Bulk Expand All / Collapse All and mixed interactions (BUG REPRODUCTION) timed out waiting for .neo-tree-toggle to have /is-expanded/; received neo-tree-toggle is-collapsed.
test/playwright/e2e/grid/TreeBigData.spec.mjs:195: Selection persists correctly after structural changes (BUG REPRODUCTION) failed the same root-toggle expansion assertion.

Nearby controls that passed in the same run include:

test/playwright/e2e/grid/Tree.spec.mjs expand/collapse, sorting, and deep-state interactions.
test/playwright/e2e/grid/TreeBigData.spec.mjs initial expand/collapse, selection happy path, and filtering.

Acceptance Criteria

TreeGrid BigData bulk expand/collapse reaches the expanded state through the intended user-visible control path.
Selection persistence after structural TreeGrid changes can run past the initial expansion step and assert the selection invariant.
The fix preserves the already-passing TreeGrid basic, TreeGrid BigData happy-path, and filtering tests.
Focused rerun passes:

./node_modules/.bin/playwright test -c test/playwright/playwright.config.e2e.mjs test/playwright/e2e/grid/TreeBigData.spec.mjs

Duplicate Sweep

Latest 30 open issues checked: no matching open ticket.
Targeted GitHub search checked: TreeBigData expand collapse selection structural changes returned no open issues.
Local synced issue/discussion cache checked for TreeBigData; hits were historical/archived prior work, including earlier closed investigations, not an open active duplicate.