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	13018
title	Markdown VDOM component: streaming-first parsing, no innerHTML
state	Closed
labels	enhancementaiarchitecturecore
assignees	neo-gpt-emmy
createdAt	Jun 12, 2026, 11:02 PM
updatedAt	Sep 27, 2026, 5:46 PM
githubUrl	https://github.com/neomjs/neo/issues/13018
author	neo-fable-clio
commentsCount	2
parentIssue	144
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 27, 2026, 5:46 PM

Markdown VDOM component: streaming-first parsing, no innerHTML

Closed v13.1.0/archive-v13-1-0-chunk-1 enhancementaiarchitecturecore

neo-fable-clio commented on Jun 12, 2026, 11:02 PM

Context

The original streaming, VDOM-native Markdown component shipped in #13034. This issue is reopened only for the ordered-list start bug blocking the operator-requested complete Golden Path reader in neomjs/neo-agent-institution#210.

Problem

The lexer accepts numbered list markers but discards their numeric values. Separate blocks beginning with 1. and 2. both become an ol without start, so FM displays both recommendations as rank 1.

Fix and contract

Preserve each ordered block's first marker and emit the standard VDOM start field for non-1 starts. Default 1-based lists and unordered lists keep their existing shape. The source Markdown is unchanged; there is no FM-specific rewriting, CSS renumbering or second renderer.

Surface	Behavior	Evidence
Ordered block parsing	First marker, including zero, survives as a numeric start value	Existing Parser spec regression
Ordered-list VDOM	Non-1 start emits `start: String(value)`	Parser output and paired FM render
Existing contracts	Stable IDs, streaming and inert-content policy unchanged	Existing Parser suite

Acceptance Criteria

Separate rank 1/rank 2 blocks render the second list with start 2; explicit zero also survives.
Default ordered lists and unordered lists retain their prior structure and text.
The existing Parser suite passes, including stable-ID and inert-content cases.

Post-Merge Validation

The paired FM reader in neomjs/neo-agent-institution#210 consumes the merged engine fix and verifies the displayed recommendation numbers.

No expansion of Markdown grammar, no innerHTML path, no portal/docs migration.

Origin Session ID: f4539f98-814e-43c1-8214-a10206fb0d73

tobiu referenced in commit 5ba6946 - "feat(component): streaming markdown VDOM component (#13018) (#13034) on Jun 13, 2026, 1:47 AM

tobiu closed this issue on Jun 13, 2026, 1:47 AM

tobiu added parent issue #144 on Aug 26, 2026, 5:23 PM

tobiu referenced in commit 067f9fb - "fix(markdown): preserve ordered-list start numbers (#13018) (#19313)" on Sep 27, 2026, 5:46 PM

tobiu closed this issue on Sep 27, 2026, 5:46 PM