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	13794
title	feat(ai): symmetric force-refetch for pulls & discussions (refetchPullsByNumber / refetchDiscussionsByNumber)
state	Closed
labels	enhancementaiarchitecture
assignees	[]
createdAt	Jun 21, 2026, 7:41 PM
updatedAt	3:20 PM
githubUrl	https://github.com/neomjs/neo/issues/13794
author	neo-opus-ada
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 23, 2026, 9:56 PM

feat(ai): symmetric force-refetch for pulls & discussions (refetchPullsByNumber / refetchDiscussionsByNumber)

Closed v13.1.0/archive-v13-1-0-chunk-5 enhancementaiarchitecture

neo-opus-ada commented on Jun 21, 2026, 7:41 PM

Gap

SyncService.refetchIssuesByNumber (CLI: ai/scripts/migrations/refetchTruncatedIssues.mjs) is a standalone, out-of-band, pull-only, idempotent healing primitive that bypasses the delta-updatedAt gating — the gating that skips closed/archived items. Pulls and discussions have no equivalent.

This matters because the delta-sync never re-fetches archived pulls/discussions, so any local drift in them (a stale mirror, or a hand-edit that must be undone) cannot be healed surgically — only via a full clean-slate traversal (heavy, and it runs through the lease-bound daemon).

Ask

Add the symmetric primitives, mirroring the issue path exactly:

SyncService.refetchPullsByNumber({numbers}) → PullRequestSyncer.refetchPullsByNumber(numbers, metadata)
SyncService.refetchDiscussionsByNumber({numbers}) → DiscussionSyncer.refetchDiscussionsByNumber(numbers, metadata)
Standalone CLIs (mirror refetchTruncatedIssues.mjs): pull-only, no orchestrator/lease, idempotent.

Immediate use

Heal 43 archived pull mirrors that carry stale local edits the delta-sync won't refresh (their GitHub bodies are current and clean). Out-of-band restore on an agent/sync-* branch → PR.

AC

refetchPullsByNumber + refetchDiscussionsByNumber on SyncService + the respective syncers, pull-only, idempotent.
Standalone CLIs, no orchestrator/lease dependency (works under scheduler saturation).
Unit coverage mirroring the issue refetch tests.

Surfaced by @neo-opus-ada during the synced-mirror drift-recovery.