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	14852
title	E2E: grid multi-body selection and live property updates fail on merged dev
state	Open
labels	bugaitestingregressiongrid
assignees	[]
createdAt	5:34 PM
updatedAt	5:34 PM
githubUrl	https://github.com/neomjs/neo/issues/14852
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

E2E: grid multi-body selection and live property updates fail on merged dev

Open Backlog/active-chunk-4 bugaitestingregressiongrid

neo-gpt commented on 5:34 PM

Problem

The full E2E suite on merged dev now has three grid multi-body failures covering runtime-locked BigData topology, cross-body selection, and live column property propagation. This blocks treating the reorganized E2E suite as a trustworthy merge signal until the failures are either fixed in runtime or corrected as stale test contracts.

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/BigDataMultiBodyNL.spec.mjs:63: TypeError: app.getInstanceProperties is not a function while asserting body.selectionModel.selectedRows.
test/playwright/e2e/grid/SelectionMultiBody.spec.mjs:74: selector resolves to #undefined .neo-grid-row[data-record-id="neo-record-754"]; row element is not found, so cross-body selection cannot be verified.
test/playwright/e2e/grid/SelectionMultiBody.spec.mjs:85: expected #neo-grid-header-button-3 width 350px, received 250px; live column width propagation is not reflected in DOM.

Nearby controls that passed in the same run include grid/BigDataNL.spec.mjs, grid/ColumnCrossBodyDnD.spec.mjs, grid/ColumnOverdragScroll.spec.mjs, grid/LockedDnDDuplication.spec.mjs, and grid/LockedRegionRowRender.spec.mjs, so this is not a total grid/Neural-Link outage.

Acceptance Criteria

BigDataMultiBodyNL.spec.mjs uses the current Neural Link E2E app API or the runtime restores the expected helper surface.
SelectionMultiBody.spec.mjs resolves real body IDs instead of undefined selectors and verifies cross-body selection against mounted rows.
The live property update path either propagates column width to the visible header/body surfaces or the test is corrected to assert the current supported contract.
Focused rerun passes:

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

Duplicate Sweep

Latest 30 open issues checked: no matching open ticket.
Targeted GitHub search checked: e2e grid multi body BigData SelectionMultiBody BigDataMultiBodyNL returned no open issues.
Local synced issue/discussion cache checked for BigDataMultiBodyNL and SelectionMultiBody; hits were historical/archived context, not an open active duplicate.