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	12319
title	fix(portal): correct news tab order (inverted-layout footgun)
state	Closed
labels	bugai
assignees	neo-opus-ada
createdAt	Jun 1, 2026, 7:58 PM
updatedAt	Jun 7, 2026, 7:17 PM
githubUrl	https://github.com/neomjs/neo/issues/12319
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 1, 2026, 8:42 PM

fix(portal): correct news tab order (inverted-layout footgun)

Closed Backlog/active-chunk-17 bugai

neo-opus-ada commented on Jun 1, 2026, 7:58 PM

Context

Operator-reported (2026-06-01): the Portal news tab order is wrong — the two newest views (Pull Requests, Discussions) appear first.

Root cause is a footgun: the news tab header renders the items list inverted (the LAST array entry displays as the FIRST / leftmost tab — "not easy to spot"). New views (#12211 discussions, #12304/#12305 pulls) were appended to the bottom of the array, so they surfaced at the top.

The Fix

Reorder apps/portal/view/news/TabContainer.mjs items so the inverted display matches the operator's intended left-to-right order, and add a comment documenting the inversion so future tabs land in the right place.

Desired display order (operator, by content value):

Release Notes (engineering war stories — strongest showcase + default landing)
Tickets (volume + roadmap)
Discussions (high-value architecture/ideation)
Blog (neo blog)
Medium
Pull Requests (rawest, least-curated; last)

Because the layout inverts, the items array is the reverse: pulls, medium, blog, discussions, tickets, release.

Acceptance Criteria

AC1 — The news tabs display left-to-right as: Release Notes, Tickets, Discussions, Blog, Medium, Pull Requests.
AC2 — A comment on the items array documents the inverted-render footgun (last entry = first tab) so future additions order correctly.

Out of Scope

Removing/changing the inverted-layout mechanism itself (separate, larger change; documenting suffices for now).

Epic #12204 (Portal news views). Surfaced alongside #12305 (pulls) / #12308 (discussions) tab additions.

tobiu referenced in commit efa0d51 - "fix(portal): correct news tab order + document inverted layout (#12319) (#12320) on Jun 1, 2026, 8:42 PM

tobiu closed this issue on Jun 1, 2026, 8:42 PM