Issue

The default ~/.mempalace/config.json generated on install includes topic wings and hall keywords clearly designed for a personal/emotional AI companion use case, not a developer workflow:

"topic_wings": ["emotions", "consciousness", "memory", "identity", "family", "creative"],
"hall_keywords": {
  "emotions": ["scared", "afraid", "worried", "happy", "sad", "love", "hate", "feel", "cry", "tears"],
  "consciousness": ["consciousness", "conscious", "aware", "real", "genuine", "soul", "exist", "alive"],
  "family": ["family", "kids", "children", "daughter", "son", "parent", "mother", "father"]
}

These are baked in before the user runs mempalace init and have no relevance to developers mining codebases, migrations, docs, and engineering conversations.

Impact

• New users setting up for code projects see confusing default structure
• Searches and classifications may be influenced by irrelevant hall keywords
• Creates a mismatch between the README (which is developer-focused) and the actual default config

Suggested Fix

Ship two default config profiles and prompt on first init:

What are you primarily using MemPalace for?
  [1] Software development (code, docs, architecture decisions)
  [2] Personal assistant (conversations, notes, relationships)
  [3] Both

Or default to a neutral/developer profile and document how to switch to the personal profile.

Environment

• mempalace 3.0.0