hotato 1.9.0

Full detail: CHANGELOG 1.9.0

Highlights

• start --demo act two: the say-do check. The guided first run now catches both failure classes on the same bundled evidence: the timing act (agent runs through the caller), then one say-do conversation check evaluated end to end, offline — the agent says the refund was sent, the trace carries no issue_refund span, the post-call state stays "none", so the check fails by design. The narrated catch is verified against the evaluated results before it prints. start --demo itself exits 0; each printed replay command is the CI gate that exits 1.
• Telephony lifecycle plane (hotato telephony): provider-agnostic call-lifecycle controller with declared per-provider capabilities and a redacted lifecycle receipt that states lifecycle facts only.
• Caller plane (hotato caller run/verify): scripted, hybrid, or generative caller programs packaged into content-addressed caller packages; verify reproduces the package and hash-compares every bound artifact. Speech from a pinned local Piper TTS.
• Load plane (hotato load ...): closed-concurrency staircase and open-arrival workloads with per-child evidence packages; queue delay, dropped starts, blocked/error rate, completion, and endpoint-match rate reported separately, never blended.
• Production evidence plane (hotato production): loopback evidence gateway over local SQLite with a verifiable audit chain, plus offline-verifiable regression export/verify.

All four planes are offline-verified: the shipped suite exercises them hermetically against recorded provider shapes and local processes; live carrier, provider, sustained-load, and production-durability behavior is qualified only by the external acceptance gates.

Docs

• Quickstart now narrates the demo's exit contract exactly: start --demo exits 0; hotato contract verify contracts/ is the CI gate that exits 1. A new test suite binds the documented exit codes to the runtime's, and the version-lockstep suite now requires the README Action pin to name an existing tag.