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	16356
title	Workstation Security pane has a zero-rect FLIP staging frame
state	Closed
labels	bugaitesting
assignees	neo-fable
createdAt	Aug 2, 2026, 3:37 PM
updatedAt	Aug 3, 2026, 11:09 PM
githubUrl	https://github.com/neomjs/neo/issues/16356
author	neo-gpt-emmy
commentsCount	5
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 3, 2026, 10:48 PM

Workstation Security pane has a zero-rect FLIP staging frame

Closed Backlog/active-chunk-12 bugaitesting

neo-gpt-emmy commented on Aug 2, 2026, 3:37 PM

Context

While repairing #16341, the headed Workstation tour advanced beyond its original edge-bottom failure and exposed a later, independent defect twice: the Security pane entered a fixed FLIP stage with one animation frame whose getBoundingClientRect() was entirely zero.

The same frame retained the expected Security component/body/header/overflow identity, but no sampled point painted. This is a reproducible observation; the owning sequencing defect is not yet known.

The Problem

A live pane can briefly become geometry-less during fixed-stage reconciliation. One blank frame is visible in a film and can invalidate geometry consumers even when final state recovers.

The Architectural Reality

DockProjectionReconciler / DockFlip owns fixed-stage geometry and restoration.
The current monitor observed two stage bursts and exactly one zero-rect frame.
Component identity survived, so replacing the pane or weakening the oracle would conceal the ordering defect.

The Fix

First enrich the failing sample with tour beat/caption, stage burst, source/destination, and ancestor rects. Determine whether fixed-stage ownership is applied before rect seeding or whether style/ownership is cleared for one frame, then repair that lifecycle seam.

Do not add a one-frame allowance or screenplay delay.

Acceptance Criteria

Both Security transitions paint pane content on every sampled animation frame.
The staged pane has positive geometry from its first fixed-stage frame.
Exact component, body, header, and overflow identity remains stable.
No fixed-stage class/style/ownership remains after settlement.
Relevant unit coverage and the Workstation headed row pass.

Out of Scope

#16341 tour settlement, drop-indicator reachability, and toolbar overflow
#16353 grid repaint after splitter drag
Popup-vessel preview witnesses

Decision Record impact

none — focused lifecycle defect.

Related: #16341 · #15252

Live latest-open sweep: checked the latest 20 open issues on 2026-08-02 at 13:35Z; no equivalent found. Exact GitHub/local searches and the semantic KB sweep found adjacent Workstation/FLIP work only. Recent all-state A2A showed no competing claim.

Retrieval Hint: Workstation Security pane zero rect fixed-stage DockFlip blank frame