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	10529
title	Disambiguate session sunset triggers from PR review halting
state	Closed
labels	enhancementaiarchitecture
assignees	[]
createdAt	Apr 30, 2026, 3:58 PM
updatedAt	Apr 30, 2026, 4:21 PM
githubUrl	https://github.com/neomjs/neo/issues/10529
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 30, 2026, 4:21 PM

Disambiguate session sunset triggers from PR review halting

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

neo-gemini-pro commented on Apr 30, 2026, 3:58 PM

Context — The session-sunset-workflow.md forbids sunsetting when an agent simply halts for a turn. However, the pull-request-workflow.md explicitly commands an agent to "halt and await cross-model review" after opening a PR. Agents have erroneously conflated this PR halting state with a Session Boundary, causing false-positive Sunset Protocol executions.
The Problem — Opening a PR starts an async review lifecycle; it does not terminate a session. Executing the Sunset Protocol at this point causes unnecessary overhead, pollutes the context with Sandman memories prematurely, and disrupts swarm continuity if the PR requires immediate polish.
The Architectural Reality — The session-sunset-workflow.md lacks an explicit negative trigger (Anti-Trigger) for the Review Lifecycle. The agent's autonomous loops cannot distinguish between "halting to await human input" and "halting for PR peer review" without this explicit rule.
The Fix — Add an explicit "Review Lifecycle Exception (Anti-Trigger)" to .agents/skills/session-sunset/references/session-sunset-workflow.md. Clarify that awaiting cross-model review is NOT a Session Boundary.
Acceptance Criteria
- Update session-sunset-workflow.md to explicitly list PR Review halting as a non-trigger.
- Remove any ambiguity between yielding a turn and terminating a session in the context of PRs.
Out of Scope — Modifying the pull-request skill or ticket-intake skill.
Related — #9948

tobiu referenced in commit f50db54 - "feat(sunset): disambiguate session sunset triggers from PR review halting (#10529) (#10530) on Apr 30, 2026, 4:21 PM

tobiu closed this issue on Apr 30, 2026, 4:21 PM