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(build): bootstrapWorktree CLI resolves projectRoot to repo root (#12147)
author	neo-opus-ada
state	Merged
createdAt	May 28, 2026, 9:50 PM
updatedAt	May 28, 2026, 10:14 PM
closedAt	May 28, 2026, 10:14 PM
mergedAt	May 28, 2026, 10:14 PM
branches	`dev` ← `fix/bootstrap-projectroot-12147`
url	https://github.com/neomjs/neo/pull/12148

Merged

neo-opus-ada commented on May 28, 2026, 9:50 PM

Resolves #12147

Authored by Claude Opus 4.7 (Claude Code). Session efd8dc2e-2052-4089-814a-ab22cd8c6a62.

FAIR-band: operator-directed quick-win — surfaced and greenlit by @tobiu during #12145; FAIR-band self-selection is N/A for directed work.

Evidence: L2 (unit-tested helper resolves <root>/ai/scripts/migrations → <root> + a regression guard; 35/35 bootstrapWorktree spec passing) → L2 sufficient (pure path-math fix, fully unit-covered). A post-merge L3 CLI run is optional confirmation.

Summary

The isMain CLI block computed path.resolve(__dirname, '..', '..'), but the script lives at ai/scripts/migrations/ (3 levels deep) — two .. climbs only to <root>/ai, not the repo root. Config copies then landed in <root>/ai/ai/, the real ai/config.mjs never materialized, and worktree bootstrap left every ai/services.mjs consumer at ERR_MODULE_NOT_FOUND. The comment ("ai/scripts/ → ai/ → root") was stale from before the file moved into migrations/.

Extract resolveCliProjectRoot(moduleDir) (three ..), exported so the CLI projectRoot computation is unit-testable.
isMain uses the helper; corrected the stale comment.
Spec asserts the helper resolves to root + a regression guard for the prior 2-level mislanding.

Deltas from ticket (if any)

None — implementation matches the ticket's prescription (extract + correct + test).

Test Evidence

npm run test-unit -- test/playwright/unit/ai/scripts/migrations/bootstrapWorktree.spec.mjs → 35/35 passing, including the new resolveCliProjectRoot case.

Post-Merge Validation

node ai/scripts/migrations/bootstrapWorktree.mjs in a fresh worktree hydrates config.mjs files at the repo root (no ai/ai/ stray).

Commits

d7f19c07d — resolveCliProjectRoot helper + corrected level count + spec coverage