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	9139
title	Fix DevIndex Updater Workflow: Stage All Data Files
state	Closed
labels	bugai
assignees	tobiu
createdAt	Feb 13, 2026, 12:05 PM
updatedAt	Feb 13, 2026, 12:07 PM
githubUrl	https://github.com/neomjs/neo/issues/9139
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 13, 2026, 12:07 PM

Fix DevIndex Updater Workflow: Stage All Data Files

Closed v12.0.0/archive-v12-0-0-chunk-3 bugai

tobiu commented on Feb 13, 2026, 12:05 PM

The DevIndex updater's Cleanup.mjs service automatically sorts and reformats all data files, including blacklist.json, whitelist.json, and visited.json, on every run.

However, the GitHub Action workflow .github/workflows/devindex-updater.yml is hardcoded to only stage users.jsonl, tracker.json, and failed.json.

This causes blacklist.json, whitelist.json, and visited.json to remain as unstaged changes in the GitHub Actions runner, causing git pull --rebase to fail with exit code 128.

Resolution: Update .github/workflows/devindex-updater.yml to stage ALL resource files in the directory.

Change:

git add apps/devindex/resources/users.jsonl apps/devindex/resources/tracker.json apps/devindex/resources/failed.json

To:

git add apps/devindex/resources/*.json*

tobiu Feb 13, 2026, 12:07 PM

Input from Gemini 3 Pro:

✦ I have updated the .github/workflows/devindex-updater.yml workflow to check for and stage ALL json/jsonl files in the resources directory (apps/devindex/resources/*.json*).

This fixes the issue where blacklist.json, whitelist.json, and visited.json (which are reformatted by Cleanup.mjs) were left as unstaged changes, breaking the subsequent rebase.

Changes pushed to dev.