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	9539
title	Add TreeStore override for updateKey()
state	Closed
labels	enhancementaicore
assignees	tobiu
createdAt	Mar 24, 2026, 9:49 AM
updatedAt	Mar 27, 2026, 10:26 AM
githubUrl	https://github.com/neomjs/neo/issues/9539
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 10:26 AM

Add TreeStore override for updateKey()

Closed v12.1.0/archive-v12-1-0-chunk-2 enhancementaicore

tobiu commented on Mar 24, 2026, 9:49 AM

Objective

The newly added updateKey(item, newKey) method in Neo.collection.Base (introduced via PR #9536) does not currently support Neo.data.TreeStore.

TreeStore extends Store (which extends Collection) but manages its own "Structural Layer" via two private maps: #allRecordsMap and #childrenMap.

If updateKey is called on a TreeStore, the base collection map is updated, but the private structural maps are not, which will cause the tree hierarchy to break (split-brain state).

Proposal

Implement an override for updateKey(item, newKey) inside src/data/TreeStore.mjs.

Call super.updateKey(item, newKey) to handle the base collection maps.
Update #allRecordsMap to reflect the new key.
If the item is a parent node, its key might be used as the parentId for other nodes in #childrenMap. The override needs to ensure that #childrenMap remains structurally sound (this might require re-mapping the children array to the new key).

tobiu cross-referenced by PR #9536 on Mar 24, 2026, 9:52 AM

tobiu Mar 27, 2026, 10:25 AM

Input from Gemini 3.1 Pro (Antigravity):

✦ Implementation for Neo.data.TreeStore.updateKey() override has been completed.

Summary of Changes:

Intercepted updateKey(item, newKey) on TreeStore.

Guaranteed the base layer (Projection maps) receives the update via super.updateKey.

Safely re-mapped the node in #allRecordsMap to ensure O(1) fetch integrity.

If the item was a parent node, correctly renamed its key inside #childrenMap and recursively iterated over its children to update their parentId references inline.

Added unit tests for TreeStore updates covering active projection mapping and Turbo Mode records.

The changes have been pushed to remote and the ticket is now closed.