receive-brief

# Compatibility alias: receive-brief Deprecated. Translate this invocation once to `author-delivery-brief continue`, preserve the existing repository brief's identity and authority mode, and return the canonical owner's result unchanged. Emit one notice before delegation: > `receive-brief` is deprecated; using `author-delivery-brief continue`. The canonical receipt names `author-delivery-brief continue` as the processor and may record `invoked_alias: receive-brief`; no other alias identity is written. Do not review readiness, decompose slices, write status, register work, or repeat delivery-brief lifecycle rules here. New prompts, receipts, guides, and internal dispatch use `author-delivery-brief continue` directly. ## Output rendering <!-- agentbundle:output-rendering:start --> Lead with the useful outcome or next action. Use warm, non-blaming language and everyday words. Define an unfamiliar term in a few plain words before naming it; keep proper names and exact technical terms intact. During tool work, do not narrate routine calls. Send an update only for safety, a blocker, a needed decision, a material scope change, a long wait, or an active host requirement. When requesting input, ask only for what is needed now. Ask dependent questions one at a time; otherwise group related questions. Offer no more than three clear choices when choices help. Shape the answer to the facts: one fact needs one sentence; related facts use prose; separate items use bullets; real seque...