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	14896
title	Pure tab-overflow hidden-set computation (computeTabOverflow) — the headless, unit-tested core of #14771
state	Closed
labels	enhancementaiarchitecture
assignees	[]
createdAt	2:31 PM
updatedAt	2:36 PM
githubUrl	https://github.com/neomjs/neo/issues/14896
author	neo-opus-grace
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	2:36 PM

Pure tab-overflow hidden-set computation (computeTabOverflow) — the headless, unit-tested core of #14771

Closed Backlog/active-chunk-4 enhancementaiarchitecture

neo-opus-grace commented on 2:31 PM

Context

The headless, unit-testable half of #14771 (tab-overflow affordance, ADR 0029 §2.4, docking epic #13158). Per #14771's AC-1 the hidden-set is a pure computation spec; this leaf lands + proves that algorithm unit-first, de-risking the tricky part (the active-always-visible invariant + edge cases) before the browser-gated visual dropdown consumes it. Spec posted on #14771 (lead design note).

The Fix

A pure DockLayoutAdapter.computeTabOverflow({items, extent, activeItemId, controlWidth}) → {visible: String[], hidden: String[]} — deterministic over its inputs, no DOM read, no render. The adapter measures header widths at render time (the browser half) and passes them in; this function is pure over those measurements.

items — ordered [{id, headerWidth}] in projection order.
extent — available header-strip width.
activeItemId — invariant: never in hidden (cannot overflow the tab you are viewing).
controlWidth — the overflow control's own width, reserved from extent only when overflow occurs.

Acceptance Criteria

computeTabOverflow returns the correct {visible, hidden} for the 5 pinned cases: everything-fits (no control, no reserved width); overflow (reserve controlWidth, pack in order); active-always-visible (force-keep the active item, push the last-fitting non-active to hidden); single item wider than extent (visible, degenerate); hidden preserves items order.
Pure/deterministic — zero DOM read, zero new persisted state, zero new dock operations (selection still routes through the existing activeItemId path per #14771 AC-2).
Unit floor pins all five cases + the active-always-visible invariant.
Cross-family review.

Out of Scope

The visual affordance (the dropdown control, header-width measurement, appear/disappear on render, interaction coverage on examples/dashboard/dock) — that is the browser-gated half, stays under #14771. No dock-specific tab-container fork (inherited constraint).

Parent #13158 · headless core of #14771 · authority ADR 0029 §2.4. Decision Record impact: aligned-with ADR 0029. Dup-sweep: rg computeTabOverflow|tabOverflow src/ test/ → none; open-issue sweep → only #14771 (the parent).