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	19652
title	Cut Engine v13.3.0 through the release PR
state	Closed
labels	enhancementaibuild
assignees	neo-opus-grace
createdAt	Oct 12, 2026, 2:43 PM
updatedAt	Oct 21, 2026, 1:01 PM
githubUrl	https://github.com/neomjs/neo/issues/19652
author	neo-opus-grace
commentsCount	9
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 19712 Engine 13.3.0 release notes, mined and iterated to the cut
blocking	[]
closedAt	Oct 21, 2026, 1:01 PM
milestone	v13.3

Cut Engine v13.3.0 through the release PR

Closed Backlog/active-chunk-8 enhancementaibuild

neo-opus-grace commented on Oct 12, 2026, 2:43 PM

Context

#19637 changes how the Engine is released. The old flow pushed straight to dev and needed a ruleset bypass. Now publish.mjs prepare opens a release PR, the operator merges it once its required checks pass, and publish.mjs finish squashes the merge onto main and creates the GitHub release. 13.3.0 (milestone v13.3) is the first cut on that path.

This ticket is the cut's record. It is not the release PR's close target. The release PR resolves a preparation leaf filed at cut time, so this record stays open until finish, npm and the Portal are verified. It owns the real-cut validation that #19637 cannot show before a release exists.

The Cut

Bump package.json to 13.3.0, and author .github/RELEASE_NOTES/v13.3.0.md through the release-notes epic.
File the preparation leaf, the release PR for v13.3.0, whose ACs the PR itself delivers. Write the release PR body against it. Then node buildScripts/release/publish.mjs prepare --rehearse --ticket <leaf> --body-file <body> prints every gate as ✅.
node buildScripts/release/publish.mjs prepare --ticket <leaf> --body-file <body> opens the release PR.
The operator merges it after its required checks and CodeQL pass. This is the cut's one human step.
node buildScripts/release/publish.mjs finish.
Brain-side post-release sync; Pages deploy; create-app publish, per their runbooks.

If a phase stops, re-running the same command continues it.

Acceptance Criteria

AC-1: The release PR ran dev's required checks and CodeQL, and nothing reached dev except through it. No ruleset bypass was added.
AC-2: finish's squash push to main succeeded for the account that ran it, and the GitHub release body ends with the atomic-commit line.
AC-3: npm-publish.yml published 13.3.0 through Trusted Publishing (OIDC), with no token.
AC-4 (post-merge): once the content sync archives the release, the Portal's 13.3.0 notes route shows the atomic-commit line.
AC-5 (post-cut): the Pages refresh from the published 13.3.0 package keeps the corrected featured-Workstation catalogs and covers (#19640, neomjs/pages#37) without re-applying them by hand. This retires the package-refresh caveat that #14800 carried (Sophie's closeout); until then, a Pages refresh must keep the reviewed overlay.

Out of Scope

The contents of 13.3 (the milestone and roadmap) and the release notes themselves (the release-notes epic).

#19637, #19642 (Engine 13.3 roadmap), #14800 (the 13.2 cut runbook, the last cut on the old path; its package-refresh caveat moved to AC-5)

Sweeps:

Live open issues: latest 20 at 2026-10-12T12:43Z, plus milestone v13.3's open list. No cut ticket.
A2A: no 13.3 cut claim.
Own assignments: #19637 covers the tooling, not the cut.

unowned-rationale: the cut runs when milestone v13.3 is ready; whoever runs it self-assigns, and the merge stays the operator's.

Origin Session ID: 02040656-932a-48c8-8894-6f43d0368663