toki
217c17dfef
- 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
12 lines
845 B
Markdown
12 lines
845 B
Markdown
# Monorepo Layout
|
|
|
|
The workspace is organized by runtime boundary rather than by task.
|
|
|
|
- `services/core` owns orchestration, persistence, scheduling, and external model/service adapters.
|
|
- `apps/client` owns the Flutter-first product UI across mobile, desktop, and optional web targets.
|
|
- `apps/web` was the previous React/Vite console scaffold, which has been removed as part of the Flutter-first client consolidation.
|
|
- `packages/contracts` owns schemas shared across clients and services.
|
|
- `agent-ops` owns root agent routing, domain rules, and repeatable task workflows.
|
|
- `docs/test-environments.md` records 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.
|