Objective

Extend the SQLite schema to support complete type definitions and implement a migration utility to populate the database from context.json.

Part A: Schema Extensions

Add the following tables to support type definitions, services, and type links:

TypeDefinition

• type_id, name, description, type_category (Record/Enum/Union/Class/Error/Constant)
• package_id (foreign key)

RecordField

• field_id, type_id, name, description, field_type (JSON), default_value, optional

EnumMember

• member_id, type_id, name, description, ordinal

UnionMember

• union_member_id, type_id, member_type_name, ordinal

ClassMethod

• method_id, class_type_id, name, description, method_type, parameters (JSON), return_type (JSON)

TypeLink

• link_id, source_type_id, target_type_name, category (internal/external), package_org, package_name

ServiceDefinition

• service_id, package_id, service_type, instructions, listener_name, listener_parameters (JSON)

ClientDefinition

• client_id, package_id, name, description

Part B: Migration Utility

Implement DatabaseManager class to:

• Parse context.json file
• Migrate packages, types, clients, and services to SQLite
• Handle cross-package dependencies and type links
• Validate data integrity after migration