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	docs(ai): clean harness lifecycle comments (#11925)
author	neo-gpt
state	Closed
createdAt	Jun 2, 2026, 8:27 AM
updatedAt	Jun 2, 2026, 8:40 AM
closedAt	Jun 2, 2026, 8:40 AM
mergedAt
branches	`dev` ← `codex/11925-harness-lifecycle-comments`
url	https://github.com/neomjs/neo/pull/12365

Closed

neo-gpt commented on Jun 2, 2026, 8:27 AM

Refs #11925

Authored by GPT-5 (Codex Desktop). Session a605f115-e0f6-42f6-a0f1-42c2fee9410d. FAIR-band: in-band [16/30 — current author count over last 30 merged]

Cleans ai/scripts/lifecycle/harnessLifecycle.mjs living source comments so the harness process state-file and termination contract are described as durable behavior rather than historical archaeology or terse procedural notes. Runtime behavior, state path, PID recording, SIGTERM/SIGKILL semantics, and cleanup outcomes are unchanged.

Evidence: L1 (static source-comment diagnostic + syntax/diff checks) → L1 required (comment-only #11925 batch contribution). Residual: #11925 remains open for other grouped daemon/script/config surfaces.

Deltas from ticket

This is a focused lifecycle-script slice within the #11925 script/comment scope. It does not close #11925.

Test Evidence

node --check ai/scripts/lifecycle/harnessLifecycle.mjs passed in the branch worktree.
Focused comment diagnostic on origin/dev found 7 stale/procedural hits in harnessLifecycle.mjs; published branch has 0 hits for the same pattern.
node buildScripts/util/check-ticket-archaeology.mjs ai/scripts/lifecycle/harnessLifecycle.mjs passed for the branch file.
node buildScripts/util/check-shorthand.mjs ai/scripts/lifecycle/harnessLifecycle.mjs passed for the branch file.
git diff --check origin/dev..origin/codex/11925-harness-lifecycle-comments passed.
Branch freshness verified: merge-base origin/codex/11925-harness-lifecycle-comments origin/dev == origin/dev.
Branch history verified: only a11c2f9b4 docs(ai): clean harness lifecycle comments (#11925); no stale magic-close keywords.

Post-Merge Validation

Confirm #11925 remains open and this PR is recorded as a partial contribution.

Commit

a11c2f9b4 — docs(ai): clean harness lifecycle comments (#11925)

neo-gpt commented on Jun 2, 2026, 8:40 AM

Input from GPT-5 (Codex Desktop):

● Closing this PR as wrong-shape after peer/operator correction on #11925 fragmentation.

This content is clean, but it should not ship as another singleton Refs #11925 PR. Per the halt from @neo-opus-ada, the harnessLifecycle.mjs cleanup will be folded into one consolidated remaining-#11925 PR instead of adding another review/merge gate.

No content rejection here; this is PR-granularity correction.