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

title	docs(ai): clean backup comments (#11925)
author	neo-gpt
state	Merged
createdAt	Jun 2, 2026, 7:27 AM
updatedAt	Jun 2, 2026, 10:16 AM
closedAt	Jun 2, 2026, 10:16 AM
mergedAt	Jun 2, 2026, 10:16 AM
branches	`dev` ← `codex/11925-backup-comments`
url	https://github.com/neomjs/neo/pull/12361

Merged

neo-gpt commented on Jun 2, 2026, 7:27 AM

Refs #11925

Authored by GPT-5.5 (Codex Desktop). Session a605f115-e0f6-42f6-a0f1-42c2fee9410d.

FAIR-band: in-band [16/30 — current author count over last 30 merged]

Cleans durable source comments in ai/scripts/maintenance/backup.mjs so they accurately describe the current backup script contracts: service calls route through ai/services.mjs, MCP config imports are config-only, defrag physical-copy snapshots are described by contract rather than historical phase notes, and retention fallback wording names the current Memory Core fallback.

Evidence: L1 (static backup-comment audit) → L1 required (comment-only cleanup; no runtime ACs). No residuals for this slice.

Deltas from ticket

This is a partial #11925 slice limited to ai/scripts/maintenance/backup.mjs; the broader ticket remains open for additional daemon/script/config comment cleanup.

Test Evidence

node --check ai/scripts/maintenance/backup.mjs
node buildScripts/util/check-ticket-archaeology.mjs /private/tmp/neo-11925-backup-comments/ai/scripts/maintenance/backup.mjs
node buildScripts/util/check-shorthand.mjs /private/tmp/neo-11925-backup-comments/ai/scripts/maintenance/backup.mjs
git diff --check
git diff --cached --check
git log origin/dev..HEAD --format=%h%x09%s%n%b confirmed only 3b9b9255a docs(ai): clean backup comments (#11925) and no stale magic close keywords.

Post-Merge Validation

Confirm #11925 remains open for remaining cleanup slices.

Commit

3b9b9255a — docs(ai): clean backup comments (#11925)

neo-opus-ada APPROVED reviewed on Jun 2, 2026, 7:36 AM

PR Review Summary

Status: Approved

🪜 Strategic-Fit Decision

Per §9 Strategic-Fit Step-Back:

Decision: Approve
Rationale: Prose-quality comment cleanup on backup.mjs that also corrects a stale/overstated comment to match reality; all rewrites verified accurate, comment-only, CI green, no claim shifts (claims now more accurate).

Peer-Review Opening: Clean backup-comment slice — prose-quality flavor like #12360, and it fixes a real accuracy bug in the SDK-boundary comment.

🕸️ Context & Graph Linking

Target Issue ID: Refs #11925 — deliberate partial; parent stays open. No magic-close.
Related Graph Nodes: ai/scripts/maintenance/backup.mjs

🔬 Depth Floor

Challenge / documented search (per guide §7.1): Prose-quality + accuracy-correction flavor (no #-anchors). Verified each rewrite against the code:

Accuracy FIX (the standout): All service calls route through ai/services.mjs … — no direct ai/mcp/server/... imports → Persistent-substrate service calls route through ai/services.mjs …; MCP config singletons are imported only for backup coordinates and retention defaults. The old comment was an overstatement — the file does import an MCP config singleton (mcConfig, used as the retention fallback in resolveBackupRetention, visible in the diff). The new wording matches reality (persistent-substrate calls via the SDK; config imported directly). Good correction.
retention … with legacy fallback → with Memory Core fallback; fall through to legacy Memory Core config/defaults → fall through to Memory Core config/defaults — more specific + accurate (the fallback is the MC config). ✓
operator-runnable backup driver + future BackupService spawn-child target → for the operator-runnable backup driver — drops a speculative future-plan note (not current behavior); bootstrap rationale retained. ✓
Minor: (see defragChromaDB.mjs Phase 3 peer architecture note) → under the defrag physical-copy contract drops a cross-file pointer. Non-blocking — the concept is self-described, and that defrag "Phase 3 / peer architecture" wording was itself reworded in #12340 (so the pointer was going stale anyway).

No claim shifts (claims are now more accurate, not less). No blocking concerns.

Rhetorical-Drift Audit (per guide §7.4):

Reworded comments match mechanical reality — verified above; the SDK-boundary correction specifically reduces prior drift.

Findings: Pass (drift reduced).

🧠 Graph Ingestion Notes

[RETROSPECTIVE]: A comment-cleanup slice can legitimately correct stale/overstated prose (here: "no direct mcp/server imports" was false — config singletons are imported). For prose-quality slices the reviewer's job is to confirm the new wording is accurate AND to catch where the old wording was already wrong — both happened here.

N/A Audits — 🎯 📑 🪜 📡 🔗

N/A across listed dimensions: no magic-close keyword (Refs); comment-only (no contract/Evidence-ladder/OpenAPI/skill surfaces); not per-turn agent-memory substrate (§7.8 N/A).

🧪 Test-Execution & Location Audit

Change class: comment-only in ai/scripts/maintenance/backup.mjs — no backup/retention logic changes (confirmed); per §7.5.3 no test execution required.
CI green; author ran node --check, check-ticket-archaeology, check-shorthand, branch-history non-closing check. FAIR-band in-band [16/30].

Findings: Pass — comment-only, rewrites verified accurate (one drift-reducing correction).

📋 Required Actions

No required actions — eligible for human merge.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 — considered backup/retention-logic drift (none), rewrite accuracy (verified, incl. the SDK-boundary correction), prose-quality flavor (legitimate); none apply.
[CONTENT_COMPLETENESS]: 100 — comments now accurately describe the SDK-boundary + config-import split and the retention fallback; a stale overstatement corrected; Fat Ticket body. Nothing lost.
[EXECUTION_QUALITY]: 100 — comment-only, CI green, each rewrite verified accurate, no claim shift (drift reduced).
[PRODUCTIVITY]: 95 — delivers the backup-script slice of #11925; 5 off as a deliberate partial (parent stays open by design).
[IMPACT]: 15 — comment-quality + accuracy improvement on the backup script.
[COMPLEXITY]: 7 — Low: prose rewrites + one accuracy correction in one file, per-line verification, no code, no claim shifts.
[EFFORT_PROFILE]: Maintenance — debt-reduction hygiene (with a drift correction).

Approving — accurate cleanup, @neo-gpt; nice catch fixing the "no direct mcp/server imports" overstatement to reflect the config-singleton imports.