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	12218
title	Opt-in load-on-folder-expand for the shared portal TreeList
state	Closed
labels	enhancementaiperformance
assignees	neo-gpt
createdAt	May 30, 2026, 7:27 PM
updatedAt	Jun 1, 2026, 6:37 AM
githubUrl	https://github.com/neomjs/neo/issues/12218
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12217 Refactor tickets index emitter → chunked-by-folder + path de-duplication
blocking	[x] 12219 Make tickets controller deep-link + default-route lazy-aware
closedAt	Jun 1, 2026, 6:37 AM

Opt-in load-on-folder-expand for the shared portal TreeList

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaiperformance

neo-opus-ada commented on May 30, 2026, 7:27 PM

Context

Part of epic #12207 (Track B; #11372 Phase 2). V-B-A confirmed Neo Store has no fetch-children-on-expand (autoInitRecords/initialChunkSize/streaming are in-memory/instantiation features); the tree loads the whole index up front.

The Fix

Add an opt-in lazyChildLoad config to the shared src/app/content/TreeList.mjs / src/tree/List.mjs: on first folder expand, the base tree awaits onFolderItemClick() before toggling the folder. Neo.app.content.TreeList uses that hook to fetch a node chunk once and store.add() its children; the flat parentId shape slots straight into createItemLevel recursion with no structural change. Per-node isChildrenLoaded / isChildrenLoading guards. Default OFF so blog, release, and medium trees keep full-load behavior.

Acceptance Criteria

Expanding a lazy-enabled folder fetches and appends only that chunk children.
Behavior is unchanged where lazyChildLoad is off.
Accordion tree overrides preserve click ordering when the base folder hook is async.

Contract Ledger

Target Surface	Source of Authority	Proposed Behavior	Fallback / Edge Case	Docs	Evidence
`src/tree/List.mjs` `onFolderItemClick(record, item, data)`	Shared tree interaction pipeline	Await the folder hook before toggling VDOM/open state so subclasses can prepare children lazily.	Hook default is a no-op; returning `false` cancels the folder toggle.	JSDoc on hook and async click path.	Focused tree unit coverage.
`src/tree/Accordion.mjs` `onItemClick()` override	Accordion selection/event semantics	Await the base tree click pipeline, then apply Accordion selection/event behavior without rewriting `record.collapsed`.	Base hook rejection propagates to awaited callers; base tree remains the collapsed-state owner.	JSDoc return contract.	New Accordion regression spec.
`src/app/content/TreeList.mjs` lazy configs	Portal content-tree specialization	`lazyChildLoad`, `lazyChildUrlPrefix`, and `lazyChildUrlField` opt in to one-shot child-chunk fetch on first expand.	Disabled by default; missing URL or already loaded/loading records skip fetch.	Config JSDoc and method summaries.	App content TreeList lazy-load spec.
`apps/portal/model/Ticket.mjs` chunk metadata fields	Portal ticket JSON chunk emitter contract	Preserve `childCount`, `childrenUrl`, `contentDir`, and `filePrefix` on ticket tree records.	Existing full-index records without chunk metadata remain valid.	Model field declarations.	Portal ticket tree fixture coverage through TreeList tests.
`apps/portal/view/news/tickets/MainContainer.mjs` `treeConfig`	Tickets tab is the first lazy-load consumer	Opt only the tickets tree into lazy loading and point chunk URLs at portal data resources.	Other portal content tabs retain current eager loading until separately opted in.	Config surface in MainContainer.	Build/lazy TreeList verification in PR.

Epic #12207; #11372 Phase 2. Depends on the chunked emitter (sub 12); unblocks the lazy-aware controller (sub 14).

tobiu referenced in commit e0abc90 - "feat(portal): lazily load content tree children (#12218) (#12279) on Jun 1, 2026, 6:37 AM

tobiu closed this issue on Jun 1, 2026, 6:37 AM