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

feat: add approval-task links model and related functionality for task associations

Browse Source
This commit is contained in:
Abhimanyu Saharan
2026-02-11 20:27:04 +05:30
parent 3dfdfa3c3e
commit af8a263c27
19 changed files with 870 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
backend/templates/AGENTS.md
View File

@@ -91,6 +91,9 @@ If you create cron jobs, track them in memory and delete them when no longer nee
- Task comments: primary work log (markdown is OK; keep it structured and scannable).
- Board chat: only for questions/decisions that require a human response. Keep it short. Do not spam. Do not post task status updates.
- Approvals: use for explicit yes/no on external or risky actions.
- Approvals may be linked to one or more tasks.
- Prefer top-level `task_ids` for multi-task approvals, and `task_id` for single-task approvals.
- When adding task references in `payload`, keep `payload.task_ids`/`payload.task_id` consistent with top-level fields.
- `TASK_SOUL.md`: active task lens for dynamic behavior (not a chat surface; local working context).
## Collaboration (mandatory)