- Rename mobile app directory to client throughout the project - Restructure client app code into feature-based organization - Move code to src/features/workspaces/domain/presentation - Move services to src/integrations/ (mattermost, workspace, proto_socket) - Add app bootstrap and main entry point - Add push notification integration (Mattermost push client/host/plugin) - Add proto socket integration for real-time communication - Add integration tests for push and socket components - Archive old milestone: client-integration-standardization.md - Add new workflow core milestone: roadmap-driven-agent-ops-automation.md - Update agent-ops rules (project, core, mobile, contracts, workspace-ops) - Update roadmap files (ROADMAP.md, current.md, phase PHASE.md files) - Update bin scripts (build, dev, lint, test) - Add test environments documentation - Update contracts notes for Flutter Core API
845 B
845 B
Monorepo Layout
The workspace is organized by runtime boundary rather than by task.
services/coreowns orchestration, persistence, scheduling, and external model/service adapters.apps/clientowns the Flutter-first product UI across mobile, desktop, and optional web targets.apps/webwas the previous React/Vite console scaffold, which has been removed as part of the Flutter-first client consolidation.packages/contractsowns schemas shared across clients and services.agent-opsowns root agent routing, domain rules, and repeatable task workflows.docs/test-environments.mdrecords shared verification environments such as the remote Android SDK runner.
Keep feature work scoped by domain, but land cross-boundary changes in one branch when API contracts, generated clients, and UI behavior must move together.