Split schema into modular components

[spacexbt]

To improve maintainability and prevent hitting size limits, we should split the schema into multiple component files:

1. base.json

   • Version (with semver validation)
   • Core identity fields

2. entity.json

   • Basic entity properties
   • Form and occupation
   • Extended attributes

3. emotional.json

   • Current emotional state
   • Emotional baseline
   • Triggers and responses

4. personality.json

   • Personality traits
   • Values and beliefs
   • Expression patterns

5. relationships.json

   • Relationship dynamics
   • Boundaries
   • Interaction patterns

The main schema will use $ref to combine these components while keeping each part manageable and focused.

This modular approach will:

• Make the schema easier to maintain
• Allow partial implementations
• Enable better version control
• Prevent size limit issues
• Improve readability