- Add orgid field (str32, not nullable) to hermes_services table
- Replace user_id with orgid in all service CRUD operations (SQL + functions)
- Update function signatures: get_all_services, create_service, delete_service,
get_service_by_id, test_service_connection, create_session,
send_message_to_service, get_session_messages all use orgid
- Add orgid indexes: idx_hermes_services_orgid, idx_hermes_services_orgid_status
- Add logined_userorgid filtering to CRUD definition for automatic framework-level isolation
- Update all .dspy files to use get_userorgid() for org-scoped service queries
- Update init/data.json and db_tables.py to reflect orgid field
- Change service_id field uitype from 'select' to 'code' (bricks has no select type)
- Create hermes_services/list/index.dspy endpoint to provide service list data for code component
- Use Form's built-in submit/cancel buttons instead of manual Button widgets
- Add sessions.json CRUD definition for session management
- Ensure proper data format for code component: {"value": "id", "text": "name"}
- 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
