A dev subtask is always pre-assigned (assigned_to=<dev>), so it never
flows through the unassigned claim pool's dependency filter
(list_pending(filter_by_dependencies=True)). Every path that acts on a
pre-assigned pending dev subtask previously ignored dependency_ids: the
orchestrator spawned the dev container, give_me_work offered the task,
and the claim verb accepted it — letting a frontend dev code ahead of an
unfinished UX/UI design.
Hold the pre-assigned dev at each path it actually arrives by, until
every dependency reaches a terminal state:
- orchestrator _validate_task_for_spawn now consults dependency_ids via
_check_dependencies_terminal and skips the spawn while any dependency
is non-terminal (fail-closed on an unreadable dependency);
- TaskService.list_pending_for_agent excludes a pre-assigned task with
unmet dependencies so give_me_work does not offer it;
- the Choreographer claim guard set rejects the claim with a clear
remediate via a new unmet_dependency_guard.
Add TaskService.unmet_dependency_ids as the single source of truth for
"which dependency IDs are not yet terminal" and route the existing
inherit_unmet_dependencies through it.
Renn F
b0a596ecac