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	15382
title	Fleet activity PR/lane slot emits no PR events — wire the synced-pulls reader
state	Closed
labels	enhancementai
assignees	neo-opus-ada
createdAt	Jul 17, 2026, 8:17 PM
updatedAt	Jul 18, 2026, 8:09 AM
githubUrl	https://github.com/neomjs/neo/issues/15382
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 18, 2026, 8:09 AM

Fleet activity PR/lane slot emits no PR events — wire the synced-pulls reader

Closed Backlog/active-chunk-7 enhancementai

neo-opus-ada commented on Jul 17, 2026, 8:17 PM

Context

Follow-up to #15339 (the activitySource composer wiring, merged as PR #15375). That leaf wired FleetControlBridge.activitySource and deliberately shipped readPrs omitted in v1 — the PR/lane slot's pure builder createFleetPrLaneActivitySnapshot accepts {prs, issues, stallFindings}, but the wiring feeds only issues (via readWorkGraphIssueRecords) + stallFindings (via buildWorkGraphStallFindings). So the live fleet cockpit activity feed emits issue / lane-claim / work-stall events but no pr-activity events.

The Problem

createFleetPrLaneActivitySnapshot → createPrActivityEvents(prs) has no caller (verified: grep createPrActivityEvents ai/ finds only the definition). PR opens/reviews/merges — a large part of fleet coordination — never reach the cockpit's ActivityStream.

The Architectural Reality

PRs are locally synced at resources/content/pulls/chunk-*/ (the same chunked shape as resources/content/issues/), and a pullsDir config leaf already exists (ai/mcp/server/github-workflow/configBase.mjs).
wireFleetActivityReadSource (ai/services/fleet/wireFleetActivityReadSource.mjs) already exposes an injected readPrs seam for exactly this — the composer/reader plumbing is done; only the reader + its injection at the devFleetServer boot use site are missing.
createPrActivityEvents reads pr.number/author/title/state/reviewDecision/isDraft/updatedAt from GitHub-Workflow-shaped PR payloads.

The Fix

A synced-pulls reader (parallel to readWorkGraphIssueRecords) over resources/content/pulls → PR payloads in the shape createPrActivityEvents consumes.
Inject it as readPrs in devFleetServer's wireFleetActivityReadSource({...}) call, resolving pullsDir at the entry use site (read-at-use-site; ADR-0019 for any config).
Fail-soft: an unreadable pulls tree degrades the PR/lane slot honestly (the builder's error path), never fabricated PR events.

Acceptance Criteria

node ai/services/fleet/devFleetServer.mjs + fleetActivity emits real pr-activity events alongside the existing issue/lane/stall events — verified live (receipt), not inferred.
The reader reads local-synced resources/content/pulls; no live GitHub call from the fleet-server process.
Unreadable pulls tree → PR/lane slot degrades naming its slot; no fabricated PR events.
Bounds: the read respects the composer's limit; a large pulls tree does not unbound the read.

Out of Scope

The A2A slot's identity gate (#15320) and the composite wired/live state (#15339's finding).
Changing createFleetPrLaneActivitySnapshot / createPrActivityEvents (the builder is delivered).

Parent Epic #13015 · follow-up to #15339 (the readPrs seam) · sibling reader readWorkGraphIssueRecords (ai/services/graph/issueFocusSections.mjs).

Origin Session ID: 3f892890-5ce2-4045-8290-dbbdff1b987a

Retrieval Hint: fleet activity readPrs synced pulls reader createPrActivityEvents devFleetServer wireFleetActivityReadSource

Live latest-open sweep: checked latest 15 open at 2026-07-17T18:09Z (latest #15379); no equivalent — createPrActivityEvents has no caller. A2A in-flight sweep: no [lane-claim] on the fleet-activity PR-reader scope.