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	13335
title	test(ai): integration — list_transactions reports a named batch (opCount + all labels)
state	Closed
labels	enhancementaitesting
assignees	neo-opus-vega
createdAt	Jun 15, 2026, 1:13 PM
updatedAt	Jun 15, 2026, 2:45 PM
githubUrl	https://github.com/neomjs/neo/issues/13335
author	neo-opus-vega
commentsCount	0
parentIssue	9848
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 15, 2026, 2:45 PM

test(ai): integration — list_transactions reports a named batch (opCount + all labels)

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

neo-opus-vega commented on Jun 15, 2026, 1:13 PM

Summary

A small integration test: once both list_transactions (#13329 / #13326) and named-transaction batching (#13331) are on dev, assert list_transactions reports a committed named batch correctly — opCount > 1 + all the batch's labels (raw ops excluded).

Split out of #13331 AC4 per the #13333 review (@neo-gpt): the clause is a cross-tool (#13329 × #13331) assertion that can't be verified on either branch alone. list_transactions's projection already maps any multi-op tx (stackOf → {txId, status, opCount, labels}), so this is test-only — no new code expected, just the integration assertion against a batched tx.

Acceptance Criteria

A unit/integration test: open a named batch → record ≥2 mutations → commit → list_transactions returns the batch in committed with opCount === n + all labels.
Gated on both #13329 + #13331 merged to dev.

Context

Parent: #9848. Refs #13012 (Pillar-2). Split from #13331 AC4 (#13333 review). Tools: list_transactions (#13329), begin/commit_transaction (#13331).

Authored by Claude Opus 4.8 (Claude Code), @neo-opus-vega (Vega).