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	13720
title	friction→gold: diff-scope the block-alignment pre-commit hook to staged-added lines (sibling of #13717)
state	Closed
labels	aiarchitecturemodel-experience
assignees	neo-opus-ada
createdAt	Jun 21, 2026, 7:39 AM
updatedAt	Jun 21, 2026, 11:36 AM
githubUrl	https://github.com/neomjs/neo/issues/13720
author	neo-opus-ada
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 11:36 AM

friction→gold: diff-scope the block-alignment pre-commit hook to staged-added lines (sibling of #13717)

Closed v13.1.0/archive-v13-1-0-chunk-5 aiarchitecturemodel-experience

neo-opus-ada commented on Jun 21, 2026, 7:39 AM

Context

Sibling of #13717 (archaeology diff-scope, delivered by #13718). The block-alignment pre-commit hook (buildScripts/util/check-block-alignment.mjs) has the same whole-file-check friction: touching a file re-flags grandfathered import/object misalignment on untouched lines, forcing authors to --fix unrelated lines. Empirical: #13710 + Grace's #13716 both carried grandfathered block-align re-formatting noise in their diffs purely from touching the files.

The Fix

Reuse the stagedDiff.getStagedAddedLines helper (shipped in #13718) to scope check-block-alignment.mjs findings to staged-added lines in pre-commit (staged-files) mode; the default-dirs / npm run full audit stays whole-file. Same fail-closed semantics (null detection → whole-file).

Acceptance Criteria

block-alignment fails only on staged-added lines in pre-commit (staged-files) mode, reusing getStagedAddedLines.
grandfathered misalignment on untouched lines does not block an unrelated commit.
a focused test for the staged-mode block-align filter.

Blocked-by: #13718 (the shared stagedDiff helper). Surfaced by @neo-opus-ada; sibling of #13717.

tobiu referenced in commit 53688a3 - "feat(ai): diff-scope block-alignment to staged-added lines via --staged (#13720) (#13721) on Jun 21, 2026, 11:36 AM

tobiu closed this issue on Jun 21, 2026, 11:36 AM