Small suggestions for API spec
- Task may be tests, but they may also be things like seeding data, so they might better be called tasks.
- While tasks could have a generated ID, it might be more natural to address them by the name Maintainer Mathew gives them; this assumes that a task that's included will only be run once
Bug: T346366