rfc-statuslisted

# /rfc-status Surface the current RFC landscape in one pass. Useful at session start (with `workspace-status`) or any time you need to know what governance work is in flight before proposing or opening a new RFC. ## 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 sequences use numbered steps. For prose artifacts, use descriptive headings, short resumable sections, one fact per sentence, and no repeated summary. Emphasize at most one load-bearing point per section. Group long inventories instead of truncating them. Make the result stand alone. Do needed arithmetic, give real dates or times, and say what a file or link establishes instead of making the reader inspect it. For code and comments, prefer obvious structure and names. Comment on intent, constraints, or trade-offs tha