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	14853
title	E2E: BigData row-pinning scroll coverage reports blank frames and stale pinning
state	Open
labels	bugaitestingregressiongrid
assignees	[]
createdAt	5:34 PM
updatedAt	5:34 PM
githubUrl	https://github.com/neomjs/neo/issues/14853
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

E2E: BigData row-pinning scroll coverage reports blank frames and stale pinning

Open Backlog/active-chunk-4 bugaitestingregressiongrid

neo-gpt commented on 5:34 PM

Problem

The full post-merge E2E run shows BigData row-pinning / thumb-drag scroll coverage failing while the analogous DevIndex scroll tests pass. This needs a focused fix or contract correction so scroll pinning regressions do not stay hidden behind a broad red suite.

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/RowPinning.spec.mjs:278: expected blankFrames to be 0, received 185 in Scroll Telemetry: Visual Blanking and Jitter Detector.
test/playwright/e2e/grid/ThumbDragPause.spec.mjs:45: expected window.__BLANK to be true after pausing during thumb drag, received false.

The same run passed test/playwright/e2e/grid/ThumbDragDevIndex.spec.mjs vertical blanking and horizontal virtualization coverage, so the failure appears scoped to the BigData row-pinning / pause path rather than every scroll telemetry spec.

Acceptance Criteria

BigData row-pinning scroll telemetry either reports zero blank frames again or the test is deliberately updated to the current supported invariant with a documented reason.
The thumb-drag pause behavior is made consistent with the intended pinning timeout contract and ThumbDragPause.spec.mjs asserts that contract.
Focused rerun passes:

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

Duplicate Sweep

Latest 30 open issues checked: no matching open ticket.
Targeted GitHub search checked: RowPinning ThumbDragPause blankFrames pinning returned no open issues.
Local synced issue/discussion cache checked for RowPinning and ThumbDragPause; hits were historical/archived prior work, not an open active duplicate.