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	13519
title	aiConfig snapshot/restore test-isolation helper (AC1 of #12435)
state	Closed
labels	enhancementaitesting
assignees	neo-opus-grace
createdAt	Jun 19, 2026, 7:17 AM
updatedAt	Jun 19, 2026, 8:25 AM
githubUrl	https://github.com/neomjs/neo/issues/13519
author	neo-opus-grace
commentsCount	1
parentIssue	12435
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 19, 2026, 8:25 AM

aiConfig snapshot/restore test-isolation helper (AC1 of #12435)

Closed v13.1.0/archive-v13-1-0-chunk-4 enhancementaitesting

neo-opus-grace commented on Jun 19, 2026, 7:17 AM

Context

The AC1 foundation of #12435 (aiConfig Provider singleton mutated without restore across ~11 specs → latent cross-test live-DB-bleed). Ships the shared snapshot/restore helper as a complete, independently-testable unit; the ~11-spec adoption + the negative full-suite --workers=1 isolation test (#12435 AC2/AC3) follow in #12435.

Live latest-open sweep: checked latest 20 open issues at ~2026-06-19T05:15Z; no equivalent — sub of #12435. Release classification: boardless (test-hygiene; post-v13).

The Fix

test/playwright/util/aiConfigSnapshot.mjs — snapshotConfigKeys(target, keys) returns a restore() closure that captures the given dotted keys at snapshot time and re-assigns them on restore. Generalizes the in-tree capture/restore precedent (DestructiveOperationGuard.spec). Pure (operates on the object handed in → unit-testable, no singleton import-coupling), supports dotted deep paths (storagePaths.graph), idempotent restore.

Acceptance Criteria

Shared helper snapshots + restores mutated aiConfig keys — deep dotted paths, idempotent, capture-at-snapshot-time. (#12435 AC1)
7 unit specs green (top-level, deep, multi-key, idempotent, capture-time, missing-path, non-array).

Out of Scope (remains in #12435)

Adopting the helper across the ~11 enumerated specs + removing their unrestored aiConfig.* writes (#12435 AC2).
The negative full-suite --workers=1 isolation run (#12435 AC3).

Parent: #12435 (retains adoption + the negative isolation test).
Precedent: test/playwright/unit/ai/mcp/server/shared/services/DestructiveOperationGuard.spec.mjs.

Origin Session ID

045a6048-1e1d-44c1-9738-7f09b62cc998