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	12210
title	Portal index generators for Pull Requests + Discussions (chunked output)
state	Closed
labels	enhancementaibuild
assignees	neo-gpt
createdAt	May 30, 2026, 7:26 PM
updatedAt	May 31, 2026, 10:26 PM
githubUrl	https://github.com/neomjs/neo/issues/12210
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 12213 Portal Pull Request view — Portal.view.news.pulls (two-section parser), [x] 12211 Portal Discussion view — Portal.view.news.discussions (thin subclass)
closedAt	May 31, 2026, 10:26 PM

Portal index generators for Pull Requests + Discussions (chunked output)

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaibuild

neo-opus-ada commented on May 30, 2026, 7:26 PM

Context

Part of epic #12207. The portal needs per-type tree-index data for PRs/Discussions; the per-issue markdown is already synced under resources/content/{pulls,discussions}/ (+ archives). buildScripts/docs/index/tickets.mjs is the canonical pattern.

The Fix

Two sibling generators buildScripts/docs/index/pulls.mjs + discussions.mjs — near-copies of tickets.mjs (reject a generalized generator; sibling-duplication is the established repo pattern, the divergence surface is the whole non-boilerplate logic). Confirmed corrections from the corpus:

leaf.id = String(frontmatter.number) — pulls/discussions have no id key.
pulls group Merged / Open / Closed (corpus ~3006 / 2 / 128 — a Merged/Open binary would drop the 128 closed-unmerged dependabot PRs).
discussions group by category (Ideas / General / Q&A).
derive the group from frontmatter for active AND archive files (ignore the version-dir); drop the label filter (no labels).
emit the chunked shape from the start (root group-index + per-chunk leaf files), so the new views are lazy-by-construction.

Wire into both buildScripts/release/prepare.mjs and .github/workflows/data-sync-pipeline.yml (publish.mjs re-runs tickets.mjs only).

Acceptance Criteria

pulls.json + discussions.json generated in the chunked shape and wired into both production sites.
leaf id = frontmatter.number; pulls 3-group, discussions category-group; archive group from frontmatter.

Epic #12207. Realizes #10056's data prerequisite. Shares the emitted chunked shape with the perf emitter-refactor (Track B) — decide that shape once.

tobiu closed this issue on May 31, 2026, 10:26 PM

tobiu referenced in commit 32806e6 - "feat(portal): add PR and discussion indexes (#12210) (#12268) on May 31, 2026, 10:26 PM

Portal index generators for Pull Requests + Discussions (chunked output)

Context

The Fix

Acceptance Criteria

Related