Command reference
oko tasks relations
Lists one task’s relations from its own side, with the other task’s state and what this task waits on.
Invocation#
oko tasks relations <task-id> [--json]Inputs and options#
- <task-id> is the identity oko tasks prints; --json prints the relation edges.
Output and state effect#
- Prints the task and one line per relation — `<name> <other> [<state>]: <reason> (recorded by <who>)` — then “waiting on: …” when an open original, predecessor or blocker holds it, or “relations: none”. Never writes.
Refusals and safe exits#
- Refuses without a positional and prints the usage. A lookup failure in the shared database or defect register is reported with its original cause, not converted into an empty relation list. An identity must name a current task, a registered defect or an actual persisted relation endpoint.
- When testing is authorized, the tasks-relation-ends integration target includes a real register-I/O refusal journey. It requires a signed-in host and OKO_TEST_SOURCE_REVISION, selects an isolated directory as OKO_DEFECT_REGISTER, and requires both relations and unrelate to expose the independently observed OS cause and exact path. Command output, exit status and source revision are retained under .build/tasks/relation-errors; the directory fixture is removed and no operator register or relation is modified.