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	8469
title	Audit and Refactor all afterSetId Implementations
state	Closed
labels	epicairefactoringcore
assignees	tobiu
createdAt	Jan 9, 2026, 4:17 PM
updatedAt	Jan 9, 2026, 6:26 PM
githubUrl	https://github.com/neomjs/neo/issues/8469
author	tobiu
commentsCount	2
parentIssue	null
subIssues	8471 Refactor afterSetId in src/button/Base.mjs 8472 Implement Lazy VDOM Cloning in Component Base 8473 Refactor afterSetId in Split Button and Grid Body 8474 Enforce Eager VDOM Cloning in Component Constructor 8475 Remove redundant ensureStableIds from Button Base 8476 Refactor Gallery to remove manual afterSetId ID assignment 8477 Refactor Progress Component ID handling 8478 Refactor afterSetId in Form Fields to ensureStableIds
subIssuesCompleted	8
subIssuesTotal	8
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 6:26 PM

Audit and Refactor all afterSetId Implementations

Closed v11.19.1/archive-v11-19-1-chunk-1 epicairefactoringcore

tobiu commented on Jan 9, 2026, 4:17 PM

Following the VDOM ID stabilization fix (#8467), we need to audit all occurrences of afterSetId in the codebase.

Context: We discovered that Component.Base#afterSetId was previously mutating the class prototype's _vdom and that manual VDOM ID assignment is now handled centrally by VdomLifecycle#ensureStableIds.

Goals:

Redundancy Removal: Identify and remove any manual VDOM ID assignment logic that is now handled by ensureStableIds.
Safety Check: Ensure no other implementations are mutating class prototypes (e.g., modifying _vdom or vdom properties during the construction phase before initConfig completes).
Compatibility: Verify that component-specific logic (e.g., updating ARIA attributes, specific DOM lookups) is compatible with the new wrapper ID scheme.

Files to Audit:

src/button/Base.mjs
src/button/Split.mjs
src/component/Abstract.mjs
src/component/Base.mjs (Already refactored, double-check)
src/component/Gallery.mjs
src/component/Progress.mjs
src/core/Base.mjs
src/grid/Body.mjs

tobiu Jan 9, 2026, 5:09 PM

Input from Gemini 3 Pro:

✦ Completed refactoring of src/button/Base.mjs in sub-ticket #8471.

Replaced afterSetId with ensureStableIds.

Verified prototype safety with new unit tests.

tobiu Jan 9, 2026, 6:26 PM

Input from Gemini 3 Pro:

✦ I have completed the audit and refactoring of all afterSetId implementations.

Summary of Work:

Core Safety: Implemented eager VDOM cloning in Neo.component.Base.construct (#8474) to prevent prototype pollution from early VDOM access.

Logic Centralization:

Refactored src/button/Split.mjs, src/grid/Body.mjs, src/component/Progress.mjs, src/component/Gallery.mjs, src/form/field/CheckBox.mjs, src/form/field/FileUpload.mjs, and src/form/field/Text.mjs.

Replaced manual afterSetId logic with ensureStableIds overrides where appropriate.

Removed redundant ensureStableIds from src/button/Base.mjs.

Audit: Verified that src/component/Abstract.mjs and src/core/Base.mjs use afterSetId correctly for manager registration, which is outside the scope of VDOM stabilization.

Outcome: The codebase now enforces a consistent, safe, and centralized pattern for VDOM ID assignment.

I am closing this Epic.