Task Wait Qualifiers rule 6: owner-return waits use blocked_on: message-from:<agent>

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

canon/standards/task-wait-qualifiers_v0.1.md

@@ -85,10 +85,12 @@ hub decision or a change request; it is optional and never a substitute for
    wait task is a human gate, else `blocked-external` when any is an external
    commitment, else `none`. "Everything waiting on a person" is therefore one
    query, not a reading exercise.
-6. A wait on a repo that has no workplan id yet is an external commitment
-   with the repo named in `blocking_reason` and in the workplan-level
-   `blocked_on:` field (watched by C-25). Upgrade to a `depends_on` id as
-   soon as the owner returns one.
+6. A wait on another owner's reply, with no workplan id yet, is an external
+   commitment qualified by `blocked_on: message-from:<agent>` on the task
+   block — the vocabulary C-25 already watches for unread replies. The
+   consistency check accepts it in place of `depends_on`; the hub read model
+   reports such a task as `unqualified` until an id exists, so upgrade to a
+   `depends_on` id as soon as the owner returns one.
 7. A human-gate task is never leased to a worker. Coordination tooling treats
    `needs_human: true` as a stop, not a wake condition.