Show us your first catch

[quantumCF]

The first candidate hotato surfaces on one of your own calls is the moment
worth sharing: a timing event with numbers attached, from a stack we have
never seen. Post it here.

How to get one

hotato investigate --stack vapi --call-id <id>    # pull by call id
hotato investigate call.wav                       # or any dual-channel WAV

Then render the moment as a card and drag the SVG into your post:

hotato card .hotato/investigate-state.json#1 --out card.svg

The card is self-contained: every color inlined, no fonts or scripts to
fetch, so it renders directly in the thread.

What makes a good post

• The stack and the command. Which capture path got you the two
  channels (adapters/README.md lists them), and the exact invocation.
• The card, or the text report block. Either carries the measured
  moment: kind, onset, durations.
• The call you made. Was it a talk-over or a false stop, and did you
  label it yield or hold? The label is yours by design ("mhm" and "stop"
  can be identical by energy), so say why you called it the way you did.
• Where it went. If you promoted it (hotato fixture promote) or minted
  a contract (hotato investigate label ... --expect yield|hold), paste the
  hotato contract verify line that now guards it in CI. That last step is
  the whole point of the tool.

Share-safe, by construction

Post the card or the report text, never the audio. Cards and reports carry
timings and measurements, not voices. Keep call ids, phone numbers, and
customer names out of the paste; if a moment is worth contributing as
audio, the corpus path (docs/SUBMITTING.md) handles consent and PII
properly.

Every first catch posted here gets a maintainer reply. If the scan surfaced
nothing on a call you know was bad, that is worth a post too: say what you
expected, attach the report, and we will look at the scan together.