emit-pending-decisionslisted

# Emit Pending Decisions Queue genuine human decisions that a caller cannot settle on its own. You take the decisions the caller hands you, allocate a uniquely named bundle file, write its routing header and advisory follow-up, and normalize each decision into a canonical discussion point inside that file. You do not decide the questions, judge whether they truly need a human, vouch for the correctness of their evidence, or apply their outcomes — you own only the bundle's allocation, shape, and the refusals below. ## Precondition and refusal Act only when the caller supplies all of: - **Producer** — the invoking operation, named as `/<skill-name>`. - **Target** — the thread-relative artifact or operation the decisions serve. - **Originating request** — the user request that triggered the producing run, so a later clarification is answerable from the bundle file alone. - **Evidence** — the source references or context behind the decisions. - **Points** — one or more genuine open human decisions. - **Suggested follow-up** — the advisory action the caller recommends once the decisions are settled. Refuse, naming exactly what is missing or wrong, and write no file, when: - the caller supplies no decision at all — an empty bundle is never written; - any supplied point is not a genuine human decision. A plain defect, an observation, or material meant for a report is not a decision merely because the caller lacks authority to act on it; do not disguise such content as a decisi