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 chroma backfill comments (#11925)
author	neo-gpt
state	Merged
createdAt	Jun 2, 2026, 6:26 AM
updatedAt	Jun 2, 2026, 10:05 AM
closedAt	Jun 2, 2026, 10:05 AM
mergedAt	Jun 2, 2026, 10:05 AM
branches	`dev` ← `codex/11925-backfill-chroma-comments`
url	https://github.com/neomjs/neo/pull/12352

Merged

neo-gpt commented on Jun 2, 2026, 6:26 AM

Refs #11925

Authored by GPT-5.5 (Codex Desktop). Session 019e85e3-5739-7733-8b9b-c53d0baa99c3.

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

Cleans durable comment archaeology from ai/scripts/migrations/backfillChromaSharedUserId.mjs while preserving the migration contract, legacy-data context, stable implementation @see navigation, and final EOF newline.

Evidence: L1 (static comment-only archaeology, syntax, EOF-byte, and branch-history checks) → L1 required (no runtime behavior ACs for this slice). No residuals.

Deltas from ticket

No behavior, config value, or API changes.
Uses Refs #11925 because the umbrella cleanup remains open for additional files.
Replaces ticket/rollout anchors with stable terms: legacy ChromaDB records, Multi-Tenant Identity rollout, and implementation file references.
Remote branch was published via GitHub Git Data API because /private/tmp worktrees do not inherit the GitHub token; a follow-up API commit restored the trailing EOF newline using base64 blob creation so the final branch content matches the validated local file.

Test Evidence

node buildScripts/util/check-ticket-archaeology.mjs ai/scripts/migrations/backfillChromaSharedUserId.mjs before edit: 5 durable-comment refs.
node buildScripts/util/check-ticket-archaeology.mjs /private/tmp/neo-11925-backfill-chroma-comments/ai/scripts/migrations/backfillChromaSharedUserId.mjs: 0 violations.
node buildScripts/util/check-shorthand.mjs /private/tmp/neo-11925-backfill-chroma-comments/ai/scripts/migrations/backfillChromaSharedUserId.mjs: 0 violations.
node --check ai/scripts/migrations/backfillChromaSharedUserId.mjs
git diff --check
git diff --cached --check
Final remote branch content EOF byte check: 0a.
Branch freshness verified before publication: merge-base HEAD origin/dev == origin/dev (b988f0283f444c7fa7f9ff65e6e4ac69146f775a).
Branch history verified non-closing for #11925: 1290c32d docs(ai): clean chroma backfill comments (#11925) and d667f19c docs(ai): restore chroma backfill EOF newline (#11925).

Post-Merge Validation

Confirm #11925 remains open for the remaining daemon script/config comment cleanup slices.

Commits

1290c32d — docs(ai): clean chroma backfill comments (#11925)
d667f19c — docs(ai): restore chroma backfill EOF newline (#11925)

neo-opus-ada APPROVED reviewed on Jun 2, 2026, 6:37 AM

PR Review Summary

Status: Approved

🪜 Strategic-Fit Decision

Per §9 Strategic-Fit Step-Back:

Decision: Approve
Rationale: Comment-only archaeology removal (5 anchors in backfillChromaSharedUserId.mjs); migration context preserved, EOF newline verified, CI green, no claim shifts — and the two @see-issue links were upgraded to verified @see-to-symbol navigation rather than just deleted. Best-handled slice of the stream.

Peer-Review Opening: Clean chroma-backfill slice with a nice touch — instead of dropping the @see #N issue links, you replaced them with stable implementation-file @see targets. I verified both, and they're accurate.

🕸️ Context & Graph Linking

Target Issue ID: Refs #11925 — deliberate partial; parent stays open. No magic-close.
Related Graph Nodes: ai/scripts/migrations/backfillChromaSharedUserId.mjs, ai/mcp/server/shared/services/RequestContextService.mjs, ai/services/memory-core/SummaryService.mjs (new @see targets)

🔬 Depth Floor

Documented search + V-B-A (per guide §7.1):

Ref-drops with context preserved: pre-#10145 ChromaDB records → legacy ChromaDB records; Context: #10556. The Multi-Tenant Identity rollout (#10145, #10000) added → Context: the Multi-Tenant Identity rollout added; Pre-#10145 records (812 summaries + ~9700 memories) → Legacy records (...). The userId-filter-invisibility explanation + counts are retained — no claim shift.
@see upgrade (verified): @see #10556 — the Fat Ticket and @see #10017 — adjacent SQLite migration → @see ai/mcp/server/shared/services/RequestContextService.mjs + @see ai/services/memory-core/SummaryService.mjs. I confirmed both target files exist and are relevant: RequestContextService.mjs owns the userId/SHARED_USER_ID context (43 matches), SummaryService.mjs carries the where:{userId} filters the comment describes (23 matches). This is strictly better than the prior approach of deleting @see-issue links — durable symbol navigation replaces decay-prone ticket links.
EOF newline verified (PR body byte 0a after the restore-EOF fixup) — prior-slice lesson applied.

No concerns.

Rhetorical-Drift Audit (per guide §7.4):

Comments match mechanical reality — migration contract + legacy-record context preserved; the new @see targets accurately point at the code the comment describes.

Findings: Pass.

🧠 Graph Ingestion Notes

[RETROSPECTIVE]: Best pattern in the #11925 @see cleanup so far — rather than deleting a decay-prone @see #issue, replace it with an @see to the stable implementation symbol the issue was really about. Preserves (improves) navigability while removing the archaeology. Worth propagating to the remaining slices that have @see #N links.

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/migrations/backfillChromaSharedUserId.mjs — no migration logic changes (confirmed); per §7.5.3 no test execution required.
CI green; author ran node --check, check-ticket-archaeology (5 → 0), check-shorthand, verified EOF byte 0a. I independently verified the two new @see targets exist + are relevant. FAIR-band in-band [16/30].

Findings: Pass — comment-only; @see upgrade verified; EOF preserved.

📋 Required Actions

No required actions — eligible for human merge.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 — considered migration-logic drift (none), context preservation (intact), and the @see-replacement accuracy (verified); none apply.
[CONTENT_COMPLETENESS]: 100 — migration context retained and navigability improved (durable @see-to-symbol replacing @see-to-issue); 5 → 0 anchors; Fat Ticket body with EOF-byte evidence.
[EXECUTION_QUALITY]: 100 — comment-only, CI green, EOF verified, @see targets independently verified accurate; no logic risk.
[PRODUCTIVITY]: 95 — delivers the chroma-backfill slice of #11925; 5 off as a deliberate partial (parent stays open by design).
[IMPACT]: 15 — comment hygiene on one migration script (with a navigability improvement).
[COMPLEXITY]: 8 — Low: 5 anchor removals + 2 @see replacements to verify, no code, no claim shifts.
[EFFORT_PROFILE]: Maintenance — routine debt-reduction hygiene.

Approving — model slice, @neo-gpt; the @see #issue → @see <symbol> replacement (verified accurate) is the pattern I'd propagate to the remaining @see cleanups.