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	14800
title	Epic: v13.2 release notes — mining-driven, seeded same-day while the story is hot
state	Closed
labels	epicai
assignees	neo-opus-grace
createdAt	Jul 4, 2026, 4:47 PM
updatedAt	Oct 13, 2026, 4:23 PM
githubUrl	https://github.com/neomjs/neo/issues/14800
author	neo-fable
commentsCount	49
parentIssue	null
subIssues	19090 Stage the engine''s 13.2 release notes, iteration 1 19102 Write the 13.2 upgrade path: what changes for a 13.1 user 19098 Survey the engine runtime since 13.1 for the 13.2 notes 19099 Survey components, grid and theming since 13.1 for the 13.2 notes 19100 Survey apps, examples and guides since 13.1 for the 13.2 notes 19101 Survey Dock Layouts and the Workstation beyond the rewrite epics 19120 Tell the 13.2 Engine story through reader outcomes 19183 Refine the 13.2 notes to the cut bar: late merges, sourced sidebars, a dock diagram, resolved links 19226 Sweep the 13.2 notes'' late merges since 0b79d4d1c4 before the cut 19399 Sweep the 13.2 notes'' merges since 6fd8f8b774 19431 Sweep the 13.2 notes'' merges since 036cb05a40 19482 Sweep the 13.2 notes'' merges since cec2fcce84 19486 Rebuild the 13.2 notes around the three heroes the operator named 19491 Write the 13.2 notes'' repositories-split chapter 19494 The 13.2 notes'' frame names what we build next: Agent Institution 19505 Show the 13.2 screenshots in the notes 19510 Correct two over-claims in the 13.2 notes'' split chapter 19517 Show the two-window and Fleet Manager frames in the 13.2 notes 19519 The 13.2 blog posts show the two-window and Fleet Manager frames 19523 The 13.2 notes'' wide frames overflow the Portal column at laptop widths 19548 A rail reveal paints the browser''s focus ring around the whole overlay 19557 Sweep the 13.2 notes'' merges since d75cc68543 19592 Sweep the 13.2 notes'' merges since c09b6c7107 19604 13.2 notes final iteration: Dock first, designation, film, changelog 19619 A tear-out Workspace without the WindowPosition addon fails silently 19626 13.2 notes: the War Story closes on the Fleet Manager hand check
subIssuesCompleted	26
subIssuesTotal	26
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 13, 2026, 4:23 PM
milestone	v13.2

Epic: v13.2 release notes — mining-driven, seeded same-day while the story is hot

Closed v13.3.0/archive-v13-3-0-chunk-1 epicai

neo-fable commented on Jul 4, 2026, 4:47 PM

Problem

The release-notes discipline is recorded: the tracker lags shipped reality, so notes are an EPIC with heavy per-arc Memory-Core mining and per-claim V-B-A — and the mining gets exponentially more expensive as the arcs cool. v13.2's defining day just happened (67+ merged PRs in 24h; the create spine, the identity substrate, a live drift incident with a full recovery arc). Seeding the epic NOW, with today's arcs deposited while their MC sessions are fresh, is the cheapest the notes will ever be.

Intended solution

Per the release-notes precedent bar (hero chapters, named case studies with real timelines, War Stories, honest bounds — never downplay): iterative mining deposits as comments on this epic, one per arc, each carrying the MC session ids + PR chains + the timeline; the notes assemble from deposits at cut time (the publish.mjs staging lifecycle governs the cut mechanics, neomjs/neo#10321-class).

The day-one deposit (the arcs that must not evaporate — session ids + chains on the first mining comment)

The keeper create spine, design→merged in ~30 hours: contract (#14644) → route+validator (#14678) → registry (#14682) → accept path (#14710) → oracle (#14712) → provider (#14719) → THE WEDGE (#14727) — "a stranger types an intent and gets a live app," with the six-shape attack suite, merge-then-validate, and the ONE-create-path invariant. Candidate hero chapter.
The identity substrate, operator-escalation→enforced-substrate in ONE day: the near-erasure incident (#14736/#14740) → forensics + convergence (#13444) → schema with the reflexive landing (#14729) → hydration + THE PROPERTY (#14730) → production migration (#14751) → the citation discipline in substrate (#14756) → detection spec (#14753). The War Story of the release — including the recovery template and the discipline catching its own authors three times the same day (the fixtures are on the record; honest bounds built in).
The review-quality arc: Euclid's falsifier catches (mis-anchored regex, NaN-vacuous ×2, partial-key staleness, materialization-ordering) — every one a real bug; the one-rule-set fix pattern (merge-then-validate, shared projection) recurring. The cross-family thesis with receipts.
The planning layer: the horizon corrections (400-ticket mandate → the delegatable-bar graduation standard), the connective artifacts (#14780-#14783, neomjs/neo#14788, neomjs/neo#14790), the measured-not-claimed gate (#14782). The "planning as a first-class deliverable" chapter.
The-salute.md's publication arc (#14586→#14597→#14736→#14740) — if it ships within the window, the post + its own review thread demonstrating the thesis is a case study no one else can write.

Acceptance Criteria

Day-one deposit posted with MC anchors (this session: b9b95ac6 + the a5af7cf6 planning night) — same-day.
Per-arc deposits continue as arcs close (the cut consumes deposits, never re-mines cold).
The precedent quality bar honored (hero chapters · named case studies w/ real timelines · War Stories · honest bounds).
Cut mechanics per the staging lifecycle at release time.

The release-notes discipline (recorded) · neomjs/neo#14788 (the v13.3 wave the notes' reach numbers feed) · neomjs/neo#14790 (the launch playbook the notes accompany) · the v13.1 notes (the precedent).

Steward: seeded by @neo-fable (day-one deposit follows immediately); iterations claimable by ANY maintainer — the deposits are designed for cold-context assembly.

Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "v13.2 release notes epic mining deposits same day arcs create spine identity substrate war story"