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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	fix(ai): dedupe liveness readiness success logs (#13954)
author	neo-gpt
state	Merged
createdAt	Jun 24, 2026, 4:44 PM
updatedAt	Jun 24, 2026, 4:54 PM
closedAt	Jun 24, 2026, 4:54 PM
mergedAt	Jun 24, 2026, 4:54 PM
branches	`dev` ← `codex/13954-process-supervisor-readiness-log-dedupe`
url	https://github.com/neomjs/neo/pull/13955
contentTrust
projected
quarantined	0
signals	[]

Merged

neo-gpt commented on Jun 24, 2026, 4:44 PM

Resolves #13954

Suppresses duplicate parent ProcessSupervisor INFO logs for repeated successful liveness-confirmed readiness checks. The first success remains visible, degraded/failed/down/start states reset the guard, and every readiness check still records a task health outcome.

Evidence: L2 (focused supervisor unit coverage + staged hook gates) -> L2 required (the close target is deterministic supervisor-service log behavior). Residual: none.

Deltas from ticket

Kept the fix inside ProcessSupervisorService; the orchestrator scheduler remains untouched.
Added a task/phase readiness-success guard instead of suppressing child logs or health telemetry.

Test Evidence

npm run test-unit -- test/playwright/unit/ai/daemons/orchestrator/services/ProcessSupervisorService.spec.mjs -> 36 passed
node ./buildScripts/util/check-block-alignment.mjs --staged -> passed
git diff --check --cached -> passed
Pre-commit hook passed: whitespace, shorthand, AiConfig test-mutation, JSDoc types, ticket archaeology, block alignment

Post-Merge Validation

Restart the orchestrator and confirm repeated healthy LM Studio liveness-readiness polls no longer flood the parent supervisor log.

Commit

8fc88eaeed — fix(ai): dedupe liveness readiness success logs (#13954)

Authored by Euclid (GPT-5, Codex Desktop). Session 019ef378-527d-7393-bc74-ec3a1d3f2ddf.