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	14575
title	Portal pull-request index unit tolerates empty post-release active chunks
state	Closed
labels	bugaitesting
assignees	neo-gpt
createdAt	3:30 AM
updatedAt	4:10 AM
githubUrl	https://github.com/neomjs/neo/issues/14575
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	4:10 AM

Portal pull-request index unit tolerates empty post-release active chunks

Closed Backlog/active-chunk-2 bugaitesting

neo-gpt commented on 3:30 AM

Context

PR #14571 failed the full unit CI job after the v13.1 release archive moved active pull-request content out of the Latest group. The failure reproduces on the current branch and the same committed index shape exists on origin/dev: apps/portal/resources/data/pulls/index.json has zero Latest/*active-chunk-* children.

Problem

test/playwright/unit/ai/buildScripts/docs/index/PortalContentIndexes.spec.mjs currently asserts chunkNumbers.length > 1 for the committed pull-request index. That was a useful ordering guard while the repo had multiple unreleased PR chunks, but it becomes false immediately after a release archive leaves no active PR chunks. The test is now asserting release timing, not the generator contract.

Fix

Adjust the committed-index assertion so it verifies descending chunk-number order when active chunks are present without requiring the repository to always have multiple unreleased active chunks. Keep the synthetic generator tests that create multiple chunks as the strong ordering proof.

Acceptance Criteria

The committed pull-request index test passes when the Latest group has zero or one active chunk.
The synthetic multi-chunk test still proves descending active chunk order.
npm run test-unit -- test/playwright/unit/ai/buildScripts/docs/index/PortalContentIndexes.spec.mjs passes.
PR #14571 unit CI can be rerun without this unrelated release-archive failure.

Evidence

gh pr checks 14571 showed unit failing while Fleet-focused local checks had passed.
CI failure: PortalContentIndexes.spec.mjs:183 expected active chunk count > 1, received 0.
Local reproduction of the exact spec produced the same single failure.
origin/dev:apps/portal/resources/data/pulls/index.json also has zero Latest children, so this is not introduced by #14562.

#14571 · #14562

Live duplicate sweep: gh search issues "PortalContentIndexes", "pull-request index active chunk", and "committed pull-request index keeps active chunk folders" returned no open matching issue before creation. Origin Session ID: 019f2a7a-94c2-7de1-901a-966c21a5d604 Retrieval Hint: "PortalContentIndexes committed pull-request index Latest active chunk post-release v13.1"

tobiu referenced in commit b1068b2 - "feat(fleet): add cockpit status DTO (#14562) (#14571) on 4:10 AM

tobiu closed this issue on 4:10 AM