- 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
- Add load_hermes_web_cli function to fix ImportError
- Update data_url paths to use /hermes-web-cli/... instead of /api/...
- Add missing renew.dspy file with complete business logic
- Update all .ui files with correct endpoint references
- Ensure module is fully functional for Sage integration
- Implement all required business functions with proper error handling
- Add database operations placeholders (to be implemented with sqlor-database-module)
- Add HTTP client for remote Hermes service communication
- Provide complete API for Sage system to implement web endpoints
- Export all public functions via __all__
- Remove plugin/router assumptions
- Implement core business functions for service management
- Follow correct module development specification
- Provide functions for Sage system integration
- Update init.py to only expose variables/functions for web scripts (no routing)
- Remove api.py (routing is automatic for wwwroot files)
- Add MODULE_DEVELOPMENT_SPEC_UPDATE.md with clarified rules
- Follow proper module development specification
- Add pyproject.toml with proper package configuration
- Rename hermes-web-cli directory to hermes_web_cli for Python compatibility
- Follow module development specification for installable packages
- Add comprehensive examples for Popup.ui and PopupWindow.ui components
- Update chat.ui to use PopupWindow for better desktop-like experience
- PopupWindow provides draggable, resizable application windows with title bar
- Popup provides modal/non-modal popup layers with auto-dismiss support
- Both components support proper event handling and lifecycle management
- Examples demonstrate real-world usage patterns for hermes-web-cli module
- 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
