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	8611
title	Update DeltaUpdates.moveNode to support Fragments
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Jan 13, 2026, 7:41 PM
updatedAt	Jan 13, 2026, 8:04 PM
githubUrl	https://github.com/neomjs/neo/issues/8611
author	tobiu
commentsCount	1
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 8:03 PM

Update DeltaUpdates.moveNode to support Fragments

Closed v11.21.0/archive-v11-21-0-chunk-1 enhancementaicore

tobiu commented on Jan 13, 2026, 7:41 PM

Update Neo.main.DeltaUpdates.moveNode to correctly resolve parent and sibling nodes when the target is a Neo.container.Fragment.

Changes:

Check if parentNode is null (indicating a logical parent like a Fragment).
If null, use getFragmentStart(parentId) to find the anchor.
Resolve parentNode from the anchor.
Resolve siblingRef using getFragmentSibling(startNode, index).
Proceed with existing insertBefore logic (preserving the "HOT-SWAP" optimization).

This depends on #8609 (Helper methods).

tobiu Jan 13, 2026, 8:03 PM

Input from Gemini 3 Pro:

✦ Updated moveNode to correctly resolve Fragment parents using the new helper methods. Verified logic with FragmentDomMove.spec.mjs (direct DeltaUpdates verification). E2E testing (FragmentLifecycle) is still timing out and will be addressed separately.