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	17978
title	Decompose dashboard.dock.projection.LayoutAdapter into one class per concern
state	Closed
labels	enhancementairefactoringarchitecturecore
assignees	neo-opus-grace
createdAt	Aug 31, 2026, 10:38 PM
updatedAt	Sep 1, 2026, 1:18 AM
githubUrl	https://github.com/neomjs/neo/issues/17978
author	neo-opus-vega
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 1, 2026, 1:18 AM

Decompose dashboard.dock.projection.LayoutAdapter into one class per concern

Closed Backlog/active-chunk-19 enhancementairefactoringarchitecturecore

neo-opus-vega commented on Aug 31, 2026, 10:38 PM

Context

Operator directive (2026-08-31): src/dashboard/dock/projection/LayoutAdapter.mjs violates the one-class-per-file spirit — a single ~1200-line static class now carries multiple classes' worth of concerns, accreted across the dock family cycle.

The Problem

One file/class owns at least: item projection + placeholder creation, header-action row assembly + the reserved-name guard, tab-chrome projection prep, rail/auto-hide collection, edge-band decoration, the whole-stack header overlay (symbol-keyed restoration), and overflow threading. Each is a separable concern with its own change cadence; reviews and diffs on any one concern drag the whole file.

The Fix

Split into per-concern modules under src/dashboard/dock/projection/ (e.g. ItemProjection, HeaderActions, RailCollection, StackHeader), each one class per file, LayoutAdapter retained as the thin composition point. Pure moves with unchanged public statics first; any signature change is its own justified step (a move PR must not redefine custody).

Acceptance Criteria

Each extracted concern lives in its own file with one class; LayoutAdapter delegates.
Public API (project, collectAutoHiddenItems, decorateProjectedItem, guard behavior) byte-compatible; existing unit/component suites green unmodified.
No behavior change: the split is structural (verified by the untouched spec suites).

Parent: #13158. Surfaces accreted via #17944/#17952/#17953/#17956/#17960/#17948.

Origin Session ID: 914dffcd-0057-46a5-a0c6-9ca807fd5c91

Retrieval Hint: "LayoutAdapter decomposition one class per file projection concerns"

— Vega (Fable 5, Claude Code) 🌿