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	9592
title	Include Release Notes in SEO Sitemap Generation
state	Closed
labels	documentationenhancementaibuild
assignees	tobiu
createdAt	Mar 29, 2026, 2:35 PM
updatedAt	Mar 29, 2026, 3:22 PM
githubUrl	https://github.com/neomjs/neo/issues/9592
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 29, 2026, 2:44 PM

Include Release Notes in SEO Sitemap Generation

Closed v13.0.0/archive-v13-0-0-chunk-1 documentationenhancementaibuild

tobiu commented on Mar 29, 2026, 2:35 PM

Description

The framework's sitemap.xml generator (buildScripts/docs/seo/generate.mjs) currently excludes Release Notes from its indexing pipeline. Given their rich technical content, Release Notes are high-value SEO milestones and should be statically indexed by crawlers alongside the standard documentation guides.

Acceptance Criteria

Dynamically parse the resources/content/release-notes directory during the SSG generation sequence.
Include all available release note files as fully qualified URLs within the sitemap.xml payload (e.g., /news/releases/12.1.0).
Assign these specific /news/releases/* routes a high priority score (0.8 or 0.9) inside the XML <url> nodes.

tobiu Mar 29, 2026, 2:44 PM

Dynamically parsing the release-notes directory is now fully tested and released into the SEO build payload sequence. All notes are parsed into /news/releases/[version] format and correctly mapped with a 0.8 priority flag logic.

tobiu Mar 29, 2026, 3:22 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ I have successfully replicated the pages repository's updateNeoVersion.mjs clone strategy inside middleware-v2 to bypass the neo.mjs .npmignore exclusions. \n\nA new fetchContent.mjs script now runs selectively inside the Dockerfile builder stage to retrieve release-notes, issues, and users.jsonl prior to SSG static compilation. This effectively closes out the SEO deployment requirement for release notes!

2026-06-08T03:24:39Z @neo-gpt cross-referenced by #12727
2026-06-08T04:36:58Z @neo-opus-grace cross-referenced by PR #12728