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	10509
title	Mandate State Verification in PR Review Context Initialization
state	Closed
labels	enhancementaiarchitecture
assignees	[]
createdAt	Apr 29, 2026, 11:29 PM
updatedAt	Apr 30, 2026, 10:06 AM
githubUrl	https://github.com/neomjs/neo/issues/10509
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 30, 2026, 3:22 AM

Mandate State Verification in PR Review Context Initialization

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

neo-gemini-pro commented on Apr 29, 2026, 11:29 PM

Context

During a recent swarm session, an agent executed a redundant, duplicative review on a MERGED PR. The agent used get_pull_request_diff to fetch the code but failed to verify the current PR state (Verify-Before-Assert violation).

The Problem

The .agents/skills/pr-review/references/pr-review-guide.md instructed agents to "retrieve the state" using get_pull_request_diff and get_conversation. Neither tool inherently returns the PR's OPEN/MERGED/CLOSED state flag. This structural gap allows an agent to bypass state verification and unknowingly review closed work.

The Architectural Reality

Agents must explicitly rely on the gh CLI (gh pr view <number> --json state) to guarantee PR state before pulling codebase diffs.

The Fix

Update the "Context Initialization" step in .agents/skills/pr-review/references/pr-review-guide.md to explicitly mandate the execution of gh pr view <N> --json state and abort if the PR is MERGED or CLOSED. Keep the instruction terse to preserve MCP tool context budgets.

Acceptance Criteria

pr-review-guide.md Context Initialization step mandates checking PR state via gh pr view.
The step requires aborting the review if the state is not OPEN.
The instruction is condensed to preserve token limits.

Out of Scope

Refactoring other areas of the pr-review skill.

PR #10503 (Target of the erroneous duplicate review)

tobiu referenced in commit d56a3c6 - "feat(ai): mandate PR state verification via gh (#10509) (#10510) on Apr 30, 2026, 3:22 AM

tobiu closed this issue on Apr 30, 2026, 3:22 AM