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	16357
title	Second tear-out resumes with the wrong pointer delta
state	Closed
labels	bugaitesting
assignees	neo-fable
createdAt	Aug 2, 2026, 3:41 PM
updatedAt	Aug 22, 2026, 12:31 AM
githubUrl	https://github.com/neomjs/neo/issues/16357
author	neo-gpt-emmy
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 22, 2026, 12:31 AM

Second tear-out resumes with the wrong pointer delta

Closed Backlog/active-chunk-12 bugaitesting

neo-gpt-emmy commented on Aug 2, 2026, 3:41 PM

Context

#16341 isolated three preview failures. In the same-gesture witness, tear-out and re-entry now succeed: the first popup retires and the in-window proxy resumes under the still-held pointer. A second tear-out in that gesture then fails its motion receipt: a requested pointer delta of {x:120,y:70} produced a fresh popup delta of {x:44,y:-84}.

Closed #15895 / PR #15897 restored initial re-entry reachability. This is a later generation/coordinate failure; that predecessor stays closed.

The Problem

After native → local → native conversion under one held pointer, the fresh vessel can resume with the wrong offset and movement direction. The exact pane survives, but its physical embodiment no longer follows the continuing gesture.

The Fix

Instrument the second vessel generation's drag offsets, pointer screen/client projection, manager.Window rect, and first two move frames. Repair the lifecycle owner that retains or reprojects stale coordinates across re-entry/re-exit. Do not reacquire the pointer or loosen the delta oracle.

Acceptance Criteria

One held pointer can tear out, re-enter, and tear out again.
The second vessel is a fresh generation and follows both pointer axes within the existing pixel tolerance.
Grab offset remains stable across both embodiment changes.
Dock document and pane identity remain unchanged; live data keeps advancing.
Focused headed witness passes repeatedly without added waits.

Out of Scope

#16341 tour/indicator/toolbar repair
#16356 fixed-stage zero-rect frame
#16353 grid repaint after splitter drag
Popup-over-popup conversion

Decision Record impact

aligned with ADR 0029 §2.8; no amendment expected unless the measured owner contradicts its coordinate authority.

Post-merge successor to #15895 / PR #15897. Related: #16341 · #15252.

Latest-open, exact GitHub, semantic KB, and all-state A2A sweeps on 2026-08-02 found no open equivalent or competing claim.

Retrieval Hint: same gesture re-entry second tear-out fresh vessel wrong pointer delta