max / goingson

Tasks can block each other, and blocked work stops reading as available A task carries no dependency today, so "what can I work on" has no way to exclude work that is waiting on something else. /threads guessed at it from a `blocked` tag and from the words in a description, which was wrong in both directions: a stale tag hid work whose blocker closed months ago, and an untagged dependency surfaced work nobody could start. task_dependencies holds the edges and is the only stored truth. One relation, one direction: the blocker must reach Completed before the blocked task can start. Not built on subtasks.linked_task_id, which means containment, and overloading it would have made "is this available" unanswerable without knowing which meaning a row carried. Edge ids are deterministic in the pair, so two devices drawing the same edge offline converge on one row. Blocked-ness is never stored as a flag on a task. A flag would need transitive recomputation on every completion and would leave two devices contesting a column neither meaningfully edited. Four derived columns cache the position instead (block_depth, unblocks_count, in_cycle, graph_urgency), all local and absent from the sync manifest: every device derives identical values from synced inputs, so replicating them would be storing a regenerable. Blocked work sinks and blockers rise across every view, as a second urgency term rather than a change to `urgency`. That column stays a pure function of the task's own fields and stays synced; graph_urgency is the subgraph term and is local. Sorting and display both read the sum. Cycles are refused on write with the offending path named, and tolerated on read, since sync can merge one out of two individually legal edges. A task on a cycle reads as blocked, never appears in ready work, and is reported for repair rather than going invisible. go-mcp gains add_dependency, remove_dependency, list_ready_tasks and get_task_graph, a blocked filter on list_tasks, blocked_by/blocks on get_task, and depends_on in bulk_import_tasks, resolved after every item exists so a backlog can be declared in reading order. The desktop app gains blocker editing in the task drawer, row badges, and a Graph subview laid out on block_depth, which already is a longest-path layering. Edges are backed up; the cached columns are excluded and rebuilt on restore. Design: wiki go-task-dependencies. got follows separately (GO faf8cf6f).