v0.22.0

• Edit tasks without touching tasks.json by hand: orch task add, orch task edit and orch task set --model change a task's definition through one editor that locks, validates the DAG (duplicate id, missing dependency, cycle, model with no route) and writes atomically (#390). The dashboard writes through the same editor: POST /api/tasks, PATCH /api/task/{id}, and POST /api/task/{id}/status for the board's moves, which stops a running task instead of changing its status behind the run's back.
• orch run picks up tasks.json changes while it runs: a new or edited task that has not started joins the running run.
• codex service tier per route: service_tier: default in model_router.yaml keeps a global Fast mode from burning your plan on every dispatch. A tier the model does not offer no longer fails and retries a dispatch that had answered (#416).
• Where the tokens went: orch report usage (and GET /api/usage) splits use into input, cached input, output and reasoning, per model, per task and per attempt, with what retries used. opencode's reasoning tokens now count as output and reach the budget. orch's budget window is its own guardrail, not your provider plan's quota (#417).

What's Changed

• feat(cli,project,state): edit task definitions through one path — task set --model, task add, task edit (#390) by @hectorcanaimero in #419
• feat(engine,run): orch run takes tasks.json again when it changes by @hectorcanaimero in #420
• fix(codex): a route can set codex's service tier, and a tier the model lacks no longer fails the dispatch (#416) by @hectorcanaimero in #422
• feat(dashboard,project): the operator adds, edits and moves tasks from the dashboard by @hectorcanaimero in #421
• feat(usage): reasoning tokens, attempts, and a usage breakdown by kind, model, task and attempt (#417) by @hectorcanaimero in #423

Full Changelog: v0.21.0...v0.22.0