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	8478
title	Refactor afterSetId in Form Fields to ensureStableIds
state	Closed
labels	airefactoringcore
assignees	tobiu
createdAt	Jan 9, 2026, 6:20 PM
updatedAt	Jan 9, 2026, 6:25 PM
githubUrl	https://github.com/neomjs/neo/issues/8478
author	tobiu
commentsCount	1
parentIssue	8469
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 9, 2026, 6:25 PM

Refactor afterSetId in Form Fields to ensureStableIds

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

tobiu commented on Jan 9, 2026, 6:20 PM

Context: src/form/field/CheckBox.mjs, src/form/field/FileUpload.mjs, and src/form/field/Text.mjs all implement afterSetId to manually update ID attributes of their internal VDOM nodes (inputs, labels, icons, etc.). This pattern is consistent across these form fields.

Goal: Refactor afterSetId into ensureStableIds for all three files. This will:

Ensure ID synchronization happens during the VDOM update preparation phase.
Remove potential prototype pollution risks (mitigated by construct fix but still cleaner).
Standardize the codebase on ensureStableIds.

Files:

src/form/field/CheckBox.mjs: label, input, icon, valueLabel IDs.
src/form/field/FileUpload.mjs: input ID.
src/form/field/Text.mjs: input, label IDs.

Verification:

Create test/playwright/unit/form/field/IdSync.spec.mjs.
Test each field type:
- Create instance.
- Check internal node IDs match the component ID structure.
- Change ID.
- Verify internal node IDs update.

tobiu Jan 9, 2026, 6:24 PM

Input from Gemini 3 Pro:

✦ I have refactored afterSetId to ensureStableIds in:

src/form/field/CheckBox.mjs

src/form/field/FileUpload.mjs

src/form/field/Text.mjs

Changes:

Replaced afterSetId with ensureStableIds.

ID synchronization logic for internal elements (inputs, labels, icons) is now handled during VDOM preparation.

This eliminates the need for manual update() calls in ID setters and further reduces prototype pollution risks.

Verification:

Added test/playwright/unit/form/field/IdSync.spec.mjs.

Verified that all internal node IDs (e.g. __input, __label) and attributes (for) are correctly synchronized with the component ID for all three field types.

Commit: 91085ea4f (#8478)