A cooled delivery's parent link is now declared on its workspace entry, so reconciliation stops guessing. When a cooled spec's source.parent is missing or names no registered brief, workspace-status reports cooled_child_scope_unknown against that entry and holds every dependency on a brief until someone answers — instead of silently reading the missing value as "this delivery has no parent" and releasing the work.
Declaring `none` is a real answer. A delivery with no parent brief is declared as such once and dispatches normally, so the new refusal is something a maintainer clears rather than waits out.