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	15110
title	CI: per-PR matrix omits e2e — dashboard/app PRs merge with zero e2e coverage (nightly runner boot-failing)
state	Closed
labels	testingbuild
assignees	[]
createdAt	Jul 12, 2026, 11:47 PM
updatedAt	Jul 12, 2026, 11:52 PM
githubUrl	https://github.com/neomjs/neo/issues/15110
author	neo-opus-grace
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 12, 2026, 11:52 PM

CI: per-PR matrix omits e2e — dashboard/app PRs merge with zero e2e coverage (nightly runner boot-failing)

Closed Backlog/active-chunk-5 testingbuild

neo-opus-grace commented on Jul 12, 2026, 11:47 PM

Problem

The per-PR CI test matrix runs only unit + integration-unified — .github/workflows/test.yml:132: suite: [integration-unified, unit]. The e2e config (test/playwright/playwright.config.e2e.mjs), which owns the dashboard/app-layer browser specs, is not in that matrix. It runs solely via the nightly e2e runner.

On PR #15062's CI (run 29191224427) that nightly runner was observed boot-failing: [nightlyE2eRunner] Running e2e.config.mjs … boot failed.

Net effect

Dashboard / app-layer PRs merge with zero per-PR e2e coverage. A DockTabOverflowNL.spec.mjs that passes locally is never executed by per-PR CI, so a regression in a floating-mount / render / align path is not caught pre-merge. This is live right now: the tab-overflow successor #15108 (dashboard projectTabsNode wiring) and the dense-workstation demo #15099 both rely on e2e journeys per-PR CI never runs.

(Also outside the per-PR matrix: the component + visual configs. The visual gap is relevant to #14618's FM-cockpit visual-regression baseline.)

Evidence

.github/workflows/test.yml:132 — suite: [integration-unified, unit] (the complete per-PR matrix).
.github/workflows/test.yml:95-108 — the isIntegrationRelevantPath whitelist + runIntegration/runUnit gates; no e2e branch exists.
test/playwright/playwright.config.e2e.mjs exists but is referenced by no per-PR workflow (grep of .github/workflows/).
PR #15062 run 29191224427 — nightly e2e runner boot-failure.

Fix direction (either / both)

Add a scoped e2e job to the per-PR matrix, gated by the existing "Classify test scope" step so it runs only when dashboard/app files change (bounded cost — most PRs skip it). Mirror isIntegrationRelevantPath with an isE2eRelevantPath (e.g. src/dashboard/, apps/, test/playwright/e2e/).
Fix the nightly e2e runner boot failure so nightly at least covers it as a backstop.

Acceptance

A dashboard/app-file change triggers an e2e job in per-PR CI (verified on a probe PR touching src/dashboard/).
A docs-only / unrelated PR does not trigger the e2e job (cost stays bounded — verified via the classify output).
The nightly e2e runner boots and runs e2e.config.mjs green (or the per-PR job supersedes it).

Homes under CI / test-infra (not app-layer). Related: #14781 (the e2e integration-journeys epic these journeys feed), #14618 (visual-regression baseline — the parallel visual-config gap), #15108 / #15099 (dashboard PRs currently merging without per-PR e2e).

Verified via gh run view on #15062 + .github/workflows/test.yml (this session). Authored by Grace (Claude Opus 4.8).