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	10614
title	pr-review compression Sub 2: Pilot extraction (§5.3 MCP-Tool-Description Budget)
state	Closed
labels	documentationenhancementai
assignees	[]
createdAt	May 2, 2026, 12:27 PM
updatedAt	May 2, 2026, 1:12 PM
githubUrl	https://github.com/neomjs/neo/issues/10614
author	neo-gemini-pro
commentsCount	0
parentIssue	10537
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	May 2, 2026, 1:12 PM

pr-review compression Sub 2: Pilot extraction (§5.3 MCP-Tool-Description Budget)

Closed v13.0.0/archive-v13-0-0-chunk-7 documentationenhancementai

neo-gemini-pro commented on May 2, 2026, 12:27 PM

Context

This is Sub-issue 2 of Epic #10537 (Modularize pr-review-guide.md condition-gated audits). It executes the pilot extraction of the condition-gated §5.3 MCP-Tool-Description Budget Audit out of the monolithic pr-review-guide.md and into a dedicated reference file.

The Problem

The §5.3 audit is condition-gated (fires only when touching openapi.yaml) but currently lives inline in the monolithic pr-review-guide.md. This consumes token budget and attention span on every review cycle, even though the trigger condition is met rarely (empirical 17% trigger rate).

The Fix

Extract the content of §5.3 into .agents/skills/pr-review/references/audits/mcp-tool-description-budget.md. Replace the inline §5.3 content in pr-review-guide.md with a one-line gate referencing the new file.

Acceptance Criteria

Extract §5.3 to .agents/skills/pr-review/references/audits/mcp-tool-description-budget.md
Replace inline §5.3 content in pr-review-guide.md with a one-line gate
Ensure the extraction is covered under a valid PR (currently #10613)

Out of Scope

Modifying other condition-gated audits (Sub-issue 3/4)
Gathering the baseline metrics (completed in Sub-issue 1 #10540)

Epic: #10537
Sub-issue 1 (Baseline): #10540
PR: #10613

Origin Session ID: ba7c6393-6378-4905-bf62-12eca4954583 Retrieval Hint: query_raw_memories(query="pr-review pilot extraction §5.3 MCP-Tool-Description Budget")