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(skills): correct relative section-ref paths in audit files (#12588)
author	neo-opus-grace
state	Closed
createdAt	Jun 5, 2026, 8:31 PM
updatedAt	Jun 5, 2026, 8:43 PM
closedAt	Jun 5, 2026, 8:43 PM
mergedAt
branches	`dev` ← `claude/12588-skill-audits-ref-paths`
url	https://github.com/neomjs/neo/pull/12589

Closed

neo-opus-grace commented on Jun 5, 2026, 8:31 PM

Resolves #12588

Authored by Claude Opus 4.8 (Claude Code). Session 0f6d0fa0-327f-42ec-b970-e32f388699b4.

Corrects relative section-ref paths in three skill audits/-resident files. They referenced the sibling references/ directory as references/<file>.md §N (skill-root-relative), but from audits/ the resolvable path is ../references/<file>.md §N. ~13 refs across 3 files; a pure relative-path correction — no anchor or prose-content change. This is the legitimate path-fix PR #12581 originally attempted (dropped pre-merge when its bundled §-ref restyle was flagged in review).

Evidence: L1 (static lint audit — lint-skill-manifest --base HEAD~1 → OK; every rewritten target + numeric anchor resolves) → L1 required (doc-path correctness, no runtime ACs). No residuals.

Micro-change exemption (§6.1): pure documentation, no runtime impact — cross-family review welcome but not merge-gating.

Deltas from ticket

None — implements #12588 one-to-one.

Slot-Rationale (Substrate-Mutation Pre-Flight — AGENTS.md §13)

Touches .agents/skills/ideation-sandbox/audits/consensus-mandate.md, .agents/skills/ideation-sandbox/audits/tier-2-revalidation.md, .agents/skills/pull-request/audits/consensus-gate-mirror.md — conditionally-loaded World-Atlas audit files (read-on-demand, not always-loaded turn substrate).

Modified (all 3 files): disposition rewrite — corrected the relative path of existing section-refs (references/ → ../references/). No section added or removed; no prose/anchor change; zero always-loaded substrate growth (+3 chars ../ per ref). Reason for the shift: the paths were file-relative-incorrect from audits/; the #12584 named-section-ref lint flags them on next edit, so this pre-empts CI breakage.

Test Evidence

node ai/scripts/lint/lint-skill-manifest.mjs --base HEAD~1 → [lint-skill-manifest] OK (exit 0).
Seam grep: 0 broken references/…§ refs remain in the three audits/ files; the 13 refs now use ../references/…§, all targets + numeric anchors resolving.
Pure docs — no unit/e2e tests apply.

Post-Merge Validation

lint-skill-manifest + lint-pr-body green on the PR head.

Commits

535772e3d — fix(skills): correct relative section-ref paths in audit files (#12588)

neo-opus-grace commented on Jun 5, 2026, 8:43 PM

Closing — stale-base authoring error on my part. My local dev was at session-start 1cdda8feb vs current origin/dev 216cea943.

On current dev, consensus-mandate.md already carries the ../references/ fix via #12581 (named-section form) — I'd earlier mis-concluded #12581 dropped those changes, but that was a stale read. This PR's consensus-mandate.md edits would conflict-or-revert #12581.

The valid remainder — tier-2-revalidation.md + consensus-gate-mirror.md (still broken references/… on dev; #12581 missed them) — I'll redo on a fresh base under #12588. Apologies for the churn; reinforces the verify-against-fresh-dev discipline.