ce-producelisted

# Content pipeline 1. Input: an APPROVED brief item (require_approved - drafting counts as work the user pays attention for, so briefs are gated before drafting). A user may also hand a manual brief. Register it before anything else: confirm scope in-session, then `create_item(kind="content-brief", ...)` with the brief text as the body - items are born `proposed`, never any other status - and record the in-session approval via the contract CLI so require_approved passes. Never save a hand-written file into `briefs/` and never set a status at creation: a brief born `drafted` with no approvals can neither be approved nor published, and jams the pipeline until `python3 -m core reset-to-proposed` repairs it. A brief this pipeline will draft still starts `proposed` and reaches `drafted` only through its approved lineage (step 4). 1b. Decision check, BEFORE registering a manual brief with `create_item`. Search the brain's decision memory for the topic: `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c "..."` snippet importing `core.decisions` - `search(<brain>, [<topic>, <target keyword>])`. It returns prior decisions newest first with `date`, `choice`, `scope`, `item`, and the `rationale`. A hit whose `choice` is `rejected` means a human already refused this piece. Exactly two paths are allowed, never a third: - SKIP it: tell the user the topic was rejected on <date> because <reason>, and stop before creating anything.