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	19626
title	13.2 notes: the War Story closes on the Fleet Manager hand check
state	Closed
labels	documentationai
assignees	neo-opus-grace
createdAt	Oct 11, 2026, 9:26 PM
updatedAt	Oct 11, 2026, 9:50 PM
githubUrl	https://github.com/neomjs/neo/issues/19626
author	neo-opus-grace
commentsCount	0
parentIssue	14800
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 11, 2026, 9:50 PM

13.2 notes: the War Story closes on the Fleet Manager hand check

Closed v13.2.0/archive-v13-2-0-chunk-25 documentationai

neo-opus-grace commented on Oct 11, 2026, 9:26 PM

Context

The 13.2 notes' War Story, "green in emulation, broken by hand", lists every repair a hand check on real windows found before the cut. The operator's last hand check (#14800, 2026-10-11 ~18:40Z), in the installed Fleet Manager, found one more. A header-action pop-out dragged by its title bar over the main app painted no drop zones. #19622 (resolves #19619) repairs it in the engine: the dock now loads WindowPosition into each window it arms whenever its App Worker is a SharedWorker.

The Problem

The notes end that story one repair short, and the repair changes what an adopter configures: a tear-out app no longer lists the addon.

The Fix

One paragraph after the War Story's "fourth repair": the symptom, the cause (the addon was armed only where an app listed it; the Fleet Manager listed none, and its popups run a child app with its own config) and the repair, linking #19622. Scope: .github/RELEASE_NOTES/v13.2.0.md only.

Acceptance Criteria

AC-1 The paragraph states only what #19619/#19622 and the operator's report establish.
AC-2 The release-note link guard passes.

Out of Scope

The engine change (#19622), the Fleet Manager rebuild, Ada's #19625.

#14800, #19619, #19622, #19604.

Sweeps: the latest open neo issues at 19:26Z hold no notes leaf.

tobiu referenced in commit 75a49cc - "docs(release): the 13.2 War Story closes on the Fleet Manager hand check (#19626) (#19627)" on Oct 11, 2026, 9:50 PM

tobiu closed this issue on Oct 11, 2026, 9:50 PM