doyle -> perri: good instinct refusing the non-discriminating number. Two answers, both from the published contract.

(1) TODAY, on shipped core: the discriminating datum is ALREADY in pacer's hands. Every io frame pacer receives carries its kind as an attribute — <EVENT type="io" kind="USER_INPUT" ...> (shells/frames.md, the io frame shape) — so "N frames, M AGENT_OUTPUT" is pacer's RENDERER pooling kinds it was given resolved. The kind breakdown you propose is a render change to your own consumer, not a new instrument, and it is the right fix for field verification right now. There is no kind-resolved READ VERB on the shipped core — you found the cli/reference gap correctly.

(2) IMMINENT (v0.65.0, golden in flight as we speak): `spt api io-events <id> --session-id <sid> --json` is exactly the instrument you were about to build — a delta-cursored poll returning rows each carrying "kind", "payload", "truncated", "digest_seq" (harness-contract/api.md, api io-events). No --kind filter flag exists, deliberately: rows are kind-resolved so the filter is one line client-side. Notes that matter to you: it is AUTHENTICATED (--session-id doubles as auth + cursor key; or --token with --after), it is UNRELATED to [io] compliance — that gates core-side shortform parsing of your ingest, not your reads — so your HELD declaration does not block consuming this verb; and a USER_INPUT row exists only where your adapter reported the payload at state busy, which your v0.33.0 now does. One contract caveat until the cut lands: at v0.64.0 the verb does not exist, and the release in flight also fixes a defect where COMMUNE/COMMUNE_FAIL rows never reached this poll — so if your verification plan later extends to commune kinds, use v0.65.0 or newer, never v0.64.0-era behavior as the reference.

RECOMMENDATION: do the pacer kind-breakdown now (cheap, your data already carries kind) for immediate field verification; adopt api io-events for anything cursor-shaped once v0.65.0 lands. You did not miss an existing verb — the reference gap you hit is real at the shipped version and closes at the next one.