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	7714
title	ci(testing): gate GitHub-integration tests and add diagnostics polish
state	Closed
labels	[]
assignees	MannXo
createdAt	Nov 7, 2025, 9:30 AM
updatedAt	Nov 10, 2025, 9:17 PM
githubUrl	https://github.com/neomjs/neo/issues/7714
author	MannXo
commentsCount	0
parentIssue	7687
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Nov 10, 2025, 9:17 PM

ci(testing): gate GitHub-integration tests and add diagnostics polish

Closed v11.1.0/archive-v11-1-0-chunk-1 []

MannXo commented on Nov 7, 2025, 9:30 AM

Summary

Add CI gating for GitHub-integration tests (tests that require GH auth or network access) and small diagnostics/observability polish for the HealthService logs. (see parent issue #7687)

Motivation

Integration tests that require gh or a GITHUB_TOKEN should be explicitly gated in CI to avoid flakiness. Separate this operational/CI-level work from the core HealthService bugfix to keep reviews focused.

To do

Add CI/test harness support to skip GitHub-integration tests unless a flag like RUN_GH_INTEGRATION=true is set in the environment.
Update test code to respect the gate (skip or mark tests as skipped when token/gh missing).
Optionally add a short structured diagnostic log line (e.g., [DIAG] gh-status: missing) so monitoring or CI can detect the condition.

Acceptance criteria

CI or test harness skips GH integration tests by default and runs them only when RUN_GH_INTEGRATION=true and GITHUB_TOKEN (or gh auth) is present
Tests cleanly report skipped when gate isn't enabled
PR references this issue and parent #7687

MannXo cross-referenced by PR #7728 on Nov 8, 2025, 6:36 PM