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	9122
title	DevIndex: Refine Updater Metrics (Success vs Failure)
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 12, 2026, 9:55 PM
updatedAt	Feb 12, 2026, 9:57 PM
githubUrl	https://github.com/neomjs/neo/issues/9122
author	tobiu
commentsCount	1
parentIssue	9106
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 12, 2026, 9:57 PM

DevIndex: Refine Updater Metrics (Success vs Failure)

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

tobiu commented on Feb 12, 2026, 9:55 PM

This task refines the logging metrics in the DevIndex Updater service.

Problem: After the "Penalty Box" implementation (#9121), failed updates are counted as "successes" to rotate the queue and update the backlog count. This obscures the actual health of the run.

Goal: Separate the metrics into:

successCount: Valid updates (Data saved).
failCount: Failed updates (Network/API errors, Penalty Boxed).
skipCount: Skipped (Bots, Low Activity, Threshold Pruned).

Changes:

Update Updater.mjs to track these counters separately.
Update the final log report to show the breakdown.
Ensure "Remaining Backlog" calculation subtracts the total processed (Success + Fail + Skip).

tobiu Feb 12, 2026, 9:56 PM

Input from Gemini 3 Pro:

✦ I have refined the metrics logging in Updater.mjs.

Changes:

New Counters: Added failCount and skipCount.

Updated Logic:

successCount: Valid updates with data saved.

skipCount: Users skipped (bots, threshold pruned, etc.) - still updates timestamp.

failCount: Users who hit the "Penalty Box" (network errors) - updates timestamp.

Backlog Math: remaining = initialBacklog - (successCount + skipCount + failCount).

Example Output:
[Updater] Run Complete.
[Updater] Successfully Updated: 150
[Updater] Skipped/Pruned: 40
[Updater] Failed (Penalty Box): 10
[Updater] Remaining Backlog: 11000