fix-issues

Step 1 — Read project config

Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: branch, mergeStrategy, language.

Step 2 — Pick the next task

Pick exactly one open task with status:approved, choosing strictly by priority. The priority order, highest first, is:

1. priority:critical
2. priority:high
3. priority:medium
4. priority:low
5. status:approved with no priority set (treat as lowest)

Within a level, take the oldest task (smallest number).

Skip tasks that are not actually actionable here, even if they still carry status:approved:

• action:reply — handled exclusively by mailbox-check.
• scheduledFor in the future — the task is snoozed ("don't pick up before this date"); it becomes eligible automatically once the date passes.

Rank every selectable task and take the single best one — pipe df task list's JSON through jq:

n=$(~/.darkflow/df task list --status approved | jq -r '
        def prio($p):
          if   $p == "critical" then 0
          elif $p == "high"     then 1
          elif $p == "medium"   then 2
          elif $p == "low"      then 3
          else 4 end;
        [ .[] | select(.action != "reply"
                       and (.scheduledFor == null or .scheduledFor <= (now | todate)))
              | {number, rank: prio(.priority)} ]
        | sort_by([.rank, .number]) | .[0].number // empty')

If $n is empty, stop — skip the run.

Step 3 — Read the task

Fetch the full task content before touching any code:

~/.darkflow/df task view $n

Read the title, body, and all comments carefully. If the task references other tasks, read those too.

The body carries a ## Plan — it is a starting point written when the finding was filed, not a contract. Follow it where it still holds; where the code has moved on, rewrite it and say so in the closing comment. The ## Acceptance criteria are the contract: each one names the command, report or URL that decides it, and every one must pass before the task closes.