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	8607
title	Advanced Fragment Lifecycle Testing (Moves & Nesting)
state	Closed
labels	aitestingcore
assignees	tobiu
createdAt	Jan 13, 2026, 5:37 PM
updatedAt	Jan 13, 2026, 8:42 PM
githubUrl	https://github.com/neomjs/neo/issues/8607
author	tobiu
commentsCount	2
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 8:42 PM

Advanced Fragment Lifecycle Testing (Moves & Nesting)

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

tobiu commented on Jan 13, 2026, 5:37 PM

Extending the coverage of #8606. Verify complex lifecycle scenarios for Neo.container.Fragment:

Move In: Move a component from a Container into a child Fragment.
Move Out: Move a component from a Fragment into its parent Container.
Cross-Fragment Move: Move a component from Fragment A to Fragment B (siblings).
Nested Moves: Move a component deeper into a nested Fragment hierarchy.
Renderer Parity: Ensure these work identically in DomApiRenderer and StringBasedRenderer (via Unit tests) and visually in Browser (via Component tests).

This will be a sub-issue of Epic #8601.

tobiu Jan 13, 2026, 7:13 PM

Input from Gemini 3 Pro:

✦ Verified VDOM delta generation for Fragment move operations via new unit tests (test/playwright/unit/vdom/FragmentMoves.spec.mjs).

Results:

Move In: Correctly targets Fragment ID as parent with relative index.

Move Out: Correctly targets physical Container ID with physical index.

Cross-Fragment: Correctly moves between logical Fragment parents.

Nested Moves: Correctly handles moves into deeper Fragment levels.

The Neo.vdom.Helper logic produces deltas that align with the expected DeltaUpdates handling for fragment anchors.

tobiu Jan 13, 2026, 8:41 PM

Input from Gemini 3 Pro:

✦ Verified comprehensive Fragment lifecycle (Moves, Nested Moves, Cross-Fragment) via test/playwright/component/container/FragmentLifecycle.spec.mjs. All underlying issues in DeltaUpdates (Fragment support, move logic) and App.mjs (moveComponent atomicity) have been resolved. E2E tests pass.