Concept Schema Enrichment: Aliases, Analogous Edges & Rich Descriptions

Objective

Enrich the concept ontology schema with deterministic aliases and cross-framework ANALOGOUS_TO edges. Depends on #10050 for source-grounded descriptions.

Context

Phase 2 prerequisite for #10037 (ChromaDB Concept Embedding). Brainstorming challenge revealed that most proposed "alternative names" (ViewModel ↔ State Provider, Multi-Threading ↔ Multi-Core) are NOT true synonyms — they're related concepts from different frameworks or different abstraction levels. This ticket formalizes a 2-layer approach to avoid collapsing architecturally distinct concepts into false equivalences.

Deliverables

1. Schema Extension: aliases Field

Add an optional aliases array to nodes.jsonl for genuinely equivalent terms only:

{"id": "reactive-configs", "aliases": ["trailing underscore", "trailing underscore convention"]}
{"id": "off-main-thread", "aliases": ["off the main thread"]}

Strict inclusion rule: A term qualifies as an alias ONLY if it refers to the exact same architectural concept within Neo.mjs. Cross-framework terms (ViewModel, JSX, etc.) belong in ANALOGOUS_TO edges.

2. New Edge Type: ANALOGOUS_TO

Add typed edges mapping Neo.mjs concepts to their nearest equivalents in other frameworks:

{"source": "state-provider", "target": "ext:react-context", "type": "ANALOGOUS_TO", "note": "Similar hierarchical state, but Neo.mjs providers use bind:{} on reactive configs — no subtree re-rendering"}
{"source": "push-reactivity", "target": "ext:vue-reactivity", "type": "ANALOGOUS_TO", "note": "Both push-based, but Neo.mjs uses explicit trailing-underscore opt-in vs Vue's Proxy-based auto-tracking"}

External concept IDs use the ext: prefix to prevent collision with internal concept IDs.

3. ConceptService API Updates

• resolveAlias(term) — deterministic O(1) alias → concept ID lookup
• getAnalogousConcepts(conceptId) — returns ANALOGOUS_TO edges for cross-framework context
• Update loadGraph() to index aliases into a reverse-lookup Map

4. Update ConceptOntology.md Guide

Document the new schema fields, the alias inclusion rule, and the ANALOGOUS_TO edge pattern.

Acceptance Criteria

• aliases field added to nodes.jsonl schema and populated for applicable concepts
• ANALOGOUS_TO edges seeded for top-10 most commonly confused cross-framework concepts
• resolveAlias() and getAnalogousConcepts() APIs implemented with unit tests
• ConceptOntology.md guide updated

Dependencies

• Blocked by #10050 (Concept Description Enrichment)
• Blocks #10037 (ChromaDB Concept Embedding)

Architectural Note

This ticket deliberately does NOT touch ChromaDB or embeddings — that's #10037's scope. Description enrichment is handled by #10050.

Origin Session ID: c9bf0d61-a58d-42ba-a030-6426dc5fe270