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	19480
title	Make popup history witness exercise verified free movement
state	Open
labels	bugaitesting
assignees	neo-gpt
createdAt	Oct 9, 2026, 6:51 AM
updatedAt	Oct 9, 2026, 6:51 AM
githubUrl	https://github.com/neomjs/neo/issues/19480
author	neo-gpt
commentsCount	0
parentIssue	17844
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Make popup history witness exercise verified free movement

Open v13.2.0/archive-v13-2-0-chunk-24 bugaitesting

neo-gpt commented on Oct 9, 2026, 6:51 AM

Context

Parent #17844 requires every failing Neural Link journey to have a truthful disposition or a linked repair. Its native pair now identifies a test-fixture defect in the popup-history arm of test/playwright/e2e/workstation/WorkstationTopologyGroupsNL.spec.mjs at Engine d75cc68543 / external Brain 03da5025.

The Problem

The arm expects native-popup-move after an arbitrary +120,+90 CDP offset. With a native viewport, that move admitted a native-docking candidate in all 32 polling observations and the unchanged 30s free-move assertion failed. A verified move outside the live target rectangles passed in 11.2s: no docking candidate, stable popup binding/generation, exactly one additional free-move row, correct committed offsets and complete ordered undo/redo. The emulated viewport also reported the popup's own dimensions as its available screen, making it unsuitable for native display placement.

The Architectural Reality

src/dashboard/dock/window/Placement.mjs#ingest intentionally refuses a free-move history row while DragCoordinator.nativeWindowDropCandidates contains the source. The existing DockPlacementNL.spec.mjs uses a native viewport and observed physical geometry for this evidence class. The failing arm owns selection of the physical scenario; the production writer already passes the verified free-move control.

Design authority: the owning Placement JSDoc says, "A free popup move appends after quiescence." Native-docking suppression remains unchanged. This correction restores the test's stated free-movement scenario and preserves Group history behavior.

The Fix

Keep the change in the existing Workstation topology test module. Give only this history arm a native viewport, choose physical placement outside the live docking targets with room for a second move, and verify the scenario before demanding a free-move row. Compare the exact new row and committed relative offsets, preserve binding/generation and retain the existing newest-first undo/full-redo checks. Other topology tests retain their established emulated viewport.

Acceptance Criteria

Only the popup-history arm uses the native viewport; other topology tests keep their existing fixture.
The full popup and its measured move fit the observed native display outside every live target hitbox.
Observed physical movement, no native-drop candidate, stable binding/generation, exactly one new native-popup-move row and matching committed offsets are asserted.
Existing ordered undo/redo assertions remain and the corrected headed arm passes.
The historical original-offset red control and current green evidence are linked on the PR and parent; the frozen parent census is not rewritten.

Out of Scope

Production placement/docking/history changes; other popup conversion mechanisms; native media/film acceptance; wider parent closure; runtime configuration or shared services.

Avoided Traps

No timeout widening, candidate clearing, manual geometry publication, synthetic transaction row, or count-only false green. No global viewport change that alters unrelated topology tests.

Decision Record impact

None: test-fixture correction preserving ADR 0029's existing semantic/presentation boundaries. No new .mjs module or runtime surface.

Parent: #17844. The open #16358 owns a separate intermittent large-over-small conversion/park mechanism and is not this fixture correction.

Creation Evidence

Live latest-open sweep: latest 20 open Engine issues read at 2026-10-09 04:51 UTC; no equivalent. Historical title/source searches found the existing evidence parent and closed Group/toolbar work, not an open repair. All-state A2A latest30 claim sweep found no overlapping claim. MC sweep: three framings surfaced current investigation efeab09b-9319-4935-8d42-6da3285741cc; broader hits were unrelated. Own-assignment sweep: three open Engine issues; #17844 is the evidence-only parent, the naming/onboarding outcomes are separate. Brain structure map ran with --files --loc; the owning edit remains the existing Engine E2E sibling module. Labels verified live.

Origin Session ID: 1690d62c-24ed-41e2-93e0-22159beeb56f Retrieval Hint: WorkstationTopologyGroupsNL native popup history free movement docking candidate