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	13186
title	feat: remove_component Slice 2 — existence-probe + snapshot-for-undo + e2e proof
state	Closed
labels	enhancementai
assignees	neo-opus-vega
createdAt	Jun 14, 2026, 7:04 AM
updatedAt	Jun 14, 2026, 10:26 AM
githubUrl	https://github.com/neomjs/neo/issues/13186
author	neo-opus-vega
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 14, 2026, 10:26 AM

feat: remove_component Slice 2 — existence-probe + snapshot-for-undo + e2e proof

Closed v13.1.0/archive-v13-1-0-chunk-2 enhancementai

neo-opus-vega commented on Jun 14, 2026, 7:04 AM

Summary

Slice 2 of remove_component (parent: #9847). Slice 1 (#13188, merged) shipped the thin write-locked tool. This ticket is re-scoped (2026-06-14) to the now-unblocked, high-value part: the e2e removal proof. The snapshot-for-undo + existence-probe are deferred (below) — the snapshot belongs to the Transaction/Undo stack #9848.

Delivered (this slice)

get_component_tree absence proof (e2e) — test/playwright/e2e/NeuralLinkRemoveComponent.spec.mjs: create a probe via create_component → assert present (tree + DOM) → remove_component it → assert gone from get_component_tree AND the live DOM. Proves Slice 1's destroy(true) behavior (instance deregistration + parent-vdom detach) end-to-end, and that create + remove compose over one live session. Now unblocked by #13188 (Slice 1) + the NL-e2e foundation (#13183 / #13191) all merging.

Deferred

Snapshot-for-undo (snapshot: true capturing config for recreate) + E2E snapshot integrity (remove → recreate round-trip) — these are reversibility, owned by the Transaction/Undo stack epic #9848. No standalone value until the undo stack exists; tracked there, not duplicated here.
Existence-probe (server-side pre-check before destroy) — a marginal hardening: Slice 1 presence-validates componentId, and a non-existent id already surfaces a worker-side error. Deferred as low-ROI unless an idempotent-no-op contract (à la the FM removeAgentRepo absent→no-op) is later wanted.

Architectural Context

Neo.component.Base.destroy(updateParentVdom, silent) is the core destruction method; Slice 1 pins updateParentVdom=true (the default destroy(false) orphans the DOM node).

Refs #9847, #9848.

Authored by @neo-opus-vega (Vega, Claude Opus 4.8) — origin session a0bc6b23-78c5-4bd7-b944-9db5e236f42d.