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	19489
title	Recover the stale-closed issues that still hold
state	Closed
labels	enhancementai
assignees	neo-opus-grace
createdAt	Oct 9, 2026, 2:46 PM
updatedAt	Oct 9, 2026, 11:04 PM
githubUrl	https://github.com/neomjs/neo/issues/19489
author	neo-opus-grace
commentsCount	30
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 9, 2026, 11:04 PM

Recover the stale-closed issues that still hold

Closed v13.2.0/archive-v13-2-0-chunk-24 enhancementai

neo-opus-grace commented on Oct 9, 2026, 2:46 PM

Context

The stale workflow has closed 456 neomjs/neo issues as not_planned, and nobody triaged any of them. The policy leaf filed beside this one stops further closes. This leaf recovers what still holds.

The Problem

Set	Count	Cost to triage
A: open and marked `stale` now	14	Low: closes in under 14 days unless the policy leaf merges first
B: closed by the bot in 2025–2026 (the team era)	66	Medium: one verdict per ticket
C: closed in one 2024 batch	390	High: predates the 13.x rewrites, so many are likely obsolete

The Knowledge Base still indexes all of them, but closed issues leave every planning view: milestones, the open queue, lane selection.

The Architectural Reality

The verdict model is #15000's: v13.2-relevant (milestone), valid-but-later (honest state), or close with the superseding artifact cited. The ledger is the same: a grep-able line per ticket.
Recovery means reopening with a one-line reason and, where it applies, a milestone or owner. Confirming a close means a comment citing what superseded it.

The Fix

Set A: a verdict for each of the 14 before the bot's next close window (around 2026-10-19).
Set B: a verdict for each of the 66, in tranches by domain (#15000's order: dock/demo first, then FM, onboarding, framework core). Peers claim tranches here.
Set C: first a random sample of 40. If more than about 10% still hold, run the full pass in tranches; if not, record the measured rate and leave C closed. The sample decides; nobody's guess does.

Acceptance Criteria

AC-1: Every ticket in set A has a verdict ledgered here.
AC-2: Every ticket in set B has a verdict ledgered here. Each reopen states why; each confirmed close cites its superseding artifact.
AC-3: Set C's 40-ticket sample is ledgered with its measured hold rate, plus the decision it implies (full pass or close the set).
AC-4: Set C full pass (the sample measured 25%): every remaining ticket (348, tranches T1–T7 in the plan comment) has a verdict ledgered here, with the same per-ticket action as the sample.

Out of Scope

The workflow change itself (the policy leaf).
#15000's 163 open aged tickets.

#15000 (verdict model and tranche process) · the policy leaf filed beside this one

Live latest-open sweep: checked the latest 20 open neomjs/neo issues at 2026-10-09T12:45:23Z; no equivalent. A2A sweep: the last 30 messages in all read-states; no claim. MC sweep: as for the policy leaf; no prior recovery decision. Own-assignment sweep: #15000 (open aged tickets) is related; this set is the closed one.

Origin Session ID: e76b2469-377c-4fec-85a7-4c47b10269b9 Retrieval Hint: "stale-closed issues recovery triage reopen sample hold rate 2024 batch"