- Use proper root properties: tblname, title, params (not name/table/operations)
- Implement list view structure with browserfields, editexclouded, etc.
- Add status field dropdown options using uitype: code with data array
- Exclude system fields (id, timestamps) from browser and edit views
- Remove invalid operations structure that was previously used
- Follow exact JSON format specified in crud-definition-spec
- Fix hermes_services.json with proper four-section format (summary/fields/indexes/codes)
- Fix hermes_service_sessions.json with proper four-section format
- Update CRUD definitions to match actual table fields
- Remove non-existent fields (user_id, api_key) from service table
- Add proper indexes and field constraints
- Follow database-table-definition-spec exactly
- Complete module following all four development specifications
- Multi-Hermes Service instance management for enterprise deployments
- Database tables: hermes_services, hermes_service_sessions
- CRUD operations for service and session management
- bricks-framework UI components: index.ui, service-detail.ui, chat.ui, settings.ui
- Support for enterprises to deploy their own hermes-service instances
- Unified interface to manage multiple service endpoints
- Security features: API key storage, HTTPS enforcement, connection testing
