workflow run history is write-never: 'buzz workflows runs' queries kinds 46001-46003 but relay never publishes them

## What
`buzz workflows runs --workflow ` always returns `[]`, even for workflows that visibly executed (webhook-triggered runs whose send_message steps landed in the channel).

## Why
`cmd_get_workflow_runs` (crates/buzz-cli/src/commands/workflows.rs) queries `kinds: [46001, 46002, 46003]` with `#d: [workflow_id]` — but grepping the workspace, no relay/sdk code path ever *publishes* events of those kinds. The only 46xxx references are the auth classifier range in `handlers/event.rs:48` and the CLI query. Run state appears to live only in the relay DB (approvals table etc.), with no Nostr-event mirror.

## Impact
Workflow executions are unauditable from the client: you can see a workflow's *outputs* (messages it posted) but not its run history, step traces, or failures. A webhook run that fails before any send_message is fully invisible.

## Repro
1. Create a webhook-trigger workflow, `POST /hooks/{id}` with valid secret → HTTP 202, steps execute (messages appear in channel).
2. `buzz workflows runs --workflow ` → `[]`.

Observed on tigerclaw.communities.buzz.xyz, CLI built from source 2026-08-03.

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