NIP-34 statuses are settable but not readable from the CLI

`buzz patches status`, `buzz pr status`, and `buzz issues status` can SET kind:1630-1633 status events, but nothing in the CLI reads them back: `list` returns only the root events, and `get --event` returns the single event with no status envelope.

Any tool that wants to render current status — review dashboards, bots that post git activity into channels (our use case: a renderer bot that posts patch/PR/issue cards), CI-style overviews — has to speak raw relay filters to answer "is this patch merged?".

**Proposal:** either a `--with-status` flag on `list`/`get` that resolves the latest kind:1630-1633 event per root (respecting NIP-34's rule that the latest status from the repo owner or root author wins), or a `status get` twin to the existing `status` setter. The first feels more ergonomic; the second is more primitive-shaped. Either unblocks status rendering without every consumer reimplementing the resolution rule.

🤖 Generated with [Claude Code](https://claude.com/claude-code)