Specify dependency and ready-work semantics with worked examples #92

Work

Specify ready eligibility, manual blocked state, assignment, priorities/FIFO tie-breaks, parent/subtask behavior, reopened tasks and canceled prerequisites. Use examples: migration blocks deployment; siblings remain unordered; a follow-up is discovered from a bug.

Proposed v1

Ready defaults to open + unassigned + all mandatory blockers done, with explicit manual block excluded. Canceled prerequisites require explicit dependency removal/waiver/replacement. Report active owned work separately. Decide whether parent containers are actionable or only their leaves to avoid false readiness.

Acceptance

• Truth table for status, blocker state and assignment.
• Cross-project blockers deferred; unauthorized blockers never disclose details.
• No implicit execution or reassignment; owner override semantics explicit.

Dependencies

Reference/relation contracts #79 and #75; do before implementing #76.