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	9699
title	Test: GraphService SQLite Lazy-Loading Coverage
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Apr 4, 2026, 6:44 PM
updatedAt	Apr 4, 2026, 6:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9699
author	tobiu
commentsCount	1
parentIssue	9680
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 6:54 PM

Test: GraphService SQLite Lazy-Loading Coverage

Closed v13.0.0/archive-v13-0-0-chunk-2 enhancementai

tobiu commented on Apr 4, 2026, 6:44 PM

Problem

The Native Edge Graph Database distributed caching architecture was recently stabilized (Issue #9697), enabling GraphService to lazily hydrate its in-memory RAM cache from the underlying SQLite datastore. However, there is currently no unit test coverage explicitly verifying that the memory layer successfully rehydrates automatically upon a cache miss.

Expected Behavior

test/playwright/unit/ai/mcp/server/memory-core/services/GraphService.spec.mjs should explicitly clear GraphService.db.nodes and edges, and ensure that requesting getNode(), getNeighbors(), and getContextFrontier() seamlessly restores properties directly from SQLite without data loss.

tobiu Apr 4, 2026, 6:54 PM

Completed via 99343e0c7. The integration tests correctly isolate the RAM cache miss simulation by suppressing cascade deletions into the SQLite native layer using autoSave = false. The tests now successfully verify the lazy-loading synchronous data rehydration.