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

friction→gold: diff-scope the ticket-archaeology pre-commit hook to staged-added lines

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

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

Premise

The pre-commit check-ticket-archaeology.mjs hook whole-file-scans staged files, so touching ANY file re-flags its grandfathered ticket-refs on untouched lines — forcing authors to clean another ticket's substrate just to commit.

Scope update (2026-06-21): originally scoped both the archaeology + block-alignment hooks; narrowed to the archaeology hook here (delivered by PR #13718). The block-alignment sibling is split to #13720 (reuses the same stagedDiff helper). This keeps the close-target honest — #13718 fully resolves this (now archaeology-only) ticket.

Empirical friction

#13710: adding a warn-block to check-branch-discipline.mjs triggered 4 commit-fails — the archaeology hook re-flagged #11133's grandfathered JSDoc refs on untouched lines.

The Fix

Scope the archaeology hook to STAGED-ADDED lines: a stagedDiff.getStagedAddedLines helper (git diff --cached --unified=0 via execFileSync — argv, no shell-interpolation; returns null on detection failure → caller falls back to whole-file). The staged-mode filter keeps only findings on added lines; the default-dirs full audit stays whole-file (block-comment state-carry preserved).

Acceptance Criteria

archaeology fails only on staged-ADDED lines in pre-commit (staged-files) mode.
grandfathered refs on untouched lines do not block an unrelated change.
fail-closed: a diff-read failure (e.g. an odd/quoted filename) must NOT suppress findings — null detection → whole-file.
real-git integration tests cover the above.

Surfaced by @neo-opus-ada (empirical: #13710). Sibling: #13720 (block-alignment).

tobiu referenced in commit 1493fc7 - "feat(ai): diff-scope the ticket-archaeology pre-commit hook to staged-added lines (#13717) (#13718) on Jun 21, 2026, 11:28 AM

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

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