TopDogLabs/mission-control
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Signed-off-by: OpenClaw Bot <ai-agent@topdoglabs.com>

Browse Source
This commit is contained in:
OpenClaw Bot 2026-02-25 14:02:04 -06:00
parent fd3dcc2cad
commit 742bd61e7b
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -20,8 +20,8 @@ Central hub for activity, tasks, goals, and tools. Built for TopDogLabs to track
- Quick actions to Gantt Board - Quick actions to Gantt Board
### Projects ### Projects
- Active sprint tracking - Active sprint tracking (global sprints from gantt-board)
- Sprint progress visualization - Sprint status/date visibility
- Project health cards with color-coded status - Project health cards with color-coded status
- Per-project task statistics - Per-project task statistics
@ -190,6 +190,14 @@ Environment variables:
Mission Control web data for tasks/projects/sprints is also read from `gantt-board` API via `GANTT_API_BASE_URL`, so both CLI and web use the same backend contract. Mission Control web data for tasks/projects/sprints is also read from `gantt-board` API via `GANTT_API_BASE_URL`, so both CLI and web use the same backend contract.
Data model note:
- Sprints are global cycles and are no longer linked to projects.
- Sprint state is derived from `start_date`/`end_date` at request time (no manual activate/deactivate step).
- Tasks remain project-scoped (`tasks.project_id` in `gantt-board` schema).
- The schema migration that removes `sprints.project_id` lives in sibling repo: `../gantt-board/supabase/remove_sprint_project_id.sql`.
- The schema migration that removes `sprints.status` lives in sibling repo: `../gantt-board/supabase/remove_sprint_status.sql`.
- `gantt-board` CLI/API sprint "current" and "active" behavior is date-based (current execution time), not persisted status-based.
For separate Docker images, set `GANTT_API_BASE_URL` to the Docker service DNS name (example: `http://gantt-board:3000/api`) on the same Docker network. For separate Docker images, set `GANTT_API_BASE_URL` to the Docker service DNS name (example: `http://gantt-board:3000/api`) on the same Docker network.
If `gantt-board` API auth is required, provide either `GANTT_API_COOKIE` (session cookie) or `GANTT_API_BEARER_TOKEN` as server-to-server auth context. If `gantt-board` API auth is required, provide either `GANTT_API_COOKIE` (session cookie) or `GANTT_API_BEARER_TOKEN` as server-to-server auth context.