LearnNewsExamplesServices
Frontmatter
titledocs: remove commercial-partner reference from chromaUnified JSDoc
authortobiu
stateMerged
createdAtApr 20, 2026, 3:15 PM
updatedAtApr 20, 2026, 3:25 PM
closedAtApr 20, 2026, 3:25 PM
mergedAtApr 20, 2026, 3:25 PM
branchesdevagent/confidentiality-hygiene-source-scrub
urlhttps://github.com/neomjs/neo/pull/10124
Merged
tobiu
tobiu commented on Apr 20, 2026, 3:15 PM

Summary

Scrubs a commercial-partner mention from shipped source. The ChromaDB unified-topology flag's JSDoc (shipped via PR #10121, landed #10001) referenced a specific customer by name. This PR replaces the reference with capability-framed language so the public source tree stays customer-neutral.

Scope

Single-line JSDoc edit in ai/mcp/server/memory-core/config.template.mjs:

- * process (the client.com cloud pattern); \`false\` preserves the **federated** two-instance default.
+ * process — the pattern for centrally hosted multi-tenant Memory Core deployments. \`false\` preserves
+ * the **federated** two-instance default.

Behavior, defaults, env-var surface all unchanged. Zero code-path impact.

Local worktree parity

The gitignored ai/mcp/server/memory-core/config.mjs mirror in this worktree has been updated locally to match. Operators on the main checkout should mirror the one-line change into their local config.mjs — or re-run node ai/scripts/bootstrapWorktree.mjs from a fresh worktree after the template merges and main's copy is updated.

Follow-up

PR bodies and comments on #10121 + #10123 + related tickets are being scrubbed in parallel via gh pr edit / manage_issue_comment update. Same confidentiality hygiene applies there.

Resolves the confidentiality-hygiene concern flagged during the #10007 PR review. No ticket filed — the scrub is the fix.