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	18400
title	Refresh popup drop geometry when its active target is resized
state	Closed
labels	bugaitestingdashboard
assignees	neo-gpt
createdAt	Sep 6, 2026, 11:09 PM
updatedAt	Sep 7, 2026, 1:32 AM
githubUrl	https://github.com/neomjs/neo/issues/18400
author	neo-gpt
commentsCount	0
parentIssue	18303
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 7, 2026, 1:32 AM

Refresh popup drop geometry when its active target is resized

Closed Backlog/active-chunk-21 bugaitestingdashboard

neo-gpt commented on Sep 6, 2026, 11:09 PM

Context and problem

The operator asked whether a popup's drop zones adjust after the popup is enlarged. Two sequences were tested while validating #18398 on d9ea7a5b44 plus its bounded staging changes:

Resize before a new hover: passes. The new permanent native journey enlarges the target, verifies its menu/preview rectangles against actual DOM geometry, and transfers another popup into an area beyond the target's former right edge.
Resize an already-hovered target: fails. A native hover first warms the target's geometry at 146 px wide. Resize that same native window to 520 px, keep the source corner inside the former target bounds, then inspect the next native frames. The DOM width is 520; ownedAffordances.geometry.hostRect.width remains 146. The direct width assertion fails after 4.7 seconds.

The probe used headed Chrome, on-screen CDP window moves/resizing, the real movement poll and the real default Participation path. No geometry or runtime code was injected. This is a warm-cache invalidation defect, distinct from the staging repair and from the intended result-region preview size.

Architectural reality and fix

Participation.defaultPreviewFor reuses DragAffordances.ensureGeometry. The controller memoizes a geometry promise and synchronous mirror until invalidated. Its shared candidate selector can rebuild from a new measured rect, but it cannot discover a resize while the existing geometry is reused.

Make the existing default target/controller invalidate and refresh its geometry when its rendering host changes size during an active gesture. Keep the geometry-generation fence so an old asynchronous measurement cannot overwrite the new size. Preserve the current indicator-first policy and borrowed/owned lifecycle contract; no second geometry cache or popup-specific controller.

Surface	Authority	Behavior	Fallback	Docs	Evidence
Default target geometry	Actual host geometry and existing DragAffordances generation	Refresh menu, preview and selection after live resize	Pending/unmeasurable geometry must not commit using stale bounds	Changed method JSDoc	Warm-cache native resize regression
Candidate selection	Shared registered PreviewContract and producer	Resolve against the refreshed target rect	Existing rejection/leave path	Existing controller docs	Actual DOM/menu/preview alignment and transfer/cancel controls

Decision Record impact: aligned-with ADR 0029; transient display geometry remains outside durable topology. Structural pre-flight: expected existing-owner changes only. Agent OS structure map N/A.

Acceptance criteria

AC-1: warm target geometry with a native hover, resize the target substantially, and observe the next settled menu/preview bounds matching the new actual DOM geometry without leaving/re-entering to force a clear.
AC-2: stale in-flight geometry cannot overwrite the newer measurement or authorize a stale-bound drop.
AC-3: the resize-before-hover positive from #18398 remains green; unchanged-size frames reuse the current geometry rather than measuring every frame.
AC-4: land a permanent headed regression for active-hover resize, with a failing pre-fix control and actual target selection/terminal evidence.

Out of scope

The native staging repair #18398, independent full roots, native claim-arbiter redesign, broad Workspace decomposition, module-wide class conversion, Feed virtual-row census, or new persistence/history behavior. Keep this out of the #18398 PR.

Prior art and ownership

An older WorkstationHumanPopupOverlapNL matrix has a post-resize variant, but it shrinks its target and is not this warmed-default-target witness. Memory Core bc1248fd-5441-4f89-82b8-31d4ad72b37e distinguishes intentional result-region sizing from stale geometry; this failure compares actual host widths, not a retired thin-band expectation. #18121's older native placement/claim instability is separate.

Live latest-20 open, own-assignment and latest-30 all-status A2A sweeps repeated immediately before filing; no equivalent found. Euclid owns the follow-up after the bounded #18398 delivery.

Related: #18303, #18304, #18395, #18398

Origin Session ID: 01a07609-5e09-70f0-bf2c-a27d77d1b7f2

Retrieval Hint: 18398-active-resize-probe preview host width 146 520