# Tasks

<!--
  Project: ${PROJECT}
  Milestone: ${MILESTONE}
  Created: ${CURRENT_DATETIME}

  IMPORTANT: This file is owned by the orchestrator. Workers NEVER modify it.
-->

<!--
## Column Reference

| Column | Type | Description |
|--------|------|-------------|
| id | string | Unique task ID (format: PREFIX-NNN, e.g., MS-SEC-001) |
| status | enum | not-started, in-progress, done, blocked |
| description | string | Brief task description with finding ID reference |
| issue | string | Gitea issue reference (e.g., #337) |
| repo | string | Target app/package (e.g., api, web, orchestrator) |
| branch | string | Feature branch for this phase |
| depends_on | string | Task IDs this depends on (comma-separated) |
| blocks | string | Task IDs blocked by this (comma-separated) |
| agent | string | Worker agent identifier (e.g., worker-1) |
| started_at | ISO8601 | When work began |
| completed_at | ISO8601 | When work finished |
| estimate | string | Token estimate (e.g., 15K) |
| used | string | Actual tokens used (e.g., 12.5K) |

## Status Workflow

  not-started → in-progress → done
                     ↓
                  blocked → in-progress (when unblocked)

## Task ID Convention

  {PROJECT_PREFIX}-{PHASE}-{NUMBER}

  Phase prefixes:
  - SEC: Security (Critical/High)
  - HIGH: High priority non-security
  - CQ: Code quality (Medium)
  - TEST: Test coverage (Low)
  - PERF: Performance
  - V01: Verification task

  Examples: MS-SEC-001, MS-HIGH-015, MS-CQ-V01
-->

| id | status | description | issue | repo | branch | depends_on | blocks | agent | started_at | completed_at | estimate | used |
|----|--------|-------------|-------|------|--------|------------|--------|-------|------------|--------------|----------|------|
| ${TASK_PREFIX}-001 | not-started | First task description | ${PHASE_ISSUE} | ${FIRST_REPO} | ${PHASE_BRANCH} | | ${TASK_PREFIX}-002 | | | | | |

<!--
  Add tasks above this line.

  Dependency rules:
  1. All Phase N tasks depend on Phase N-1 verification task
  2. Same-file tasks should be sequential (earlier blocks later)
  3. Each phase ends with a verification task (e.g., MS-SEC-V01)
-->
