feat(voice): add call-flow step traces to call records - #44
Merged
Conversation
Carries the step-by-step story of a flow run — which prompt played, what the caller pressed, where the call went — from the daemon up to the platform, where the call-detail page pins them on the recording waveform as clickable markers. Middle of the three-repo train: wavekat-platform already accepts and stores the field. Two shape decisions worth stating, both about surviving version skew: - Structural, not prose. The daemon renders an English sentence per step locally; shipping that instead of the parts would make these permanently untranslatable on a platform serving nine locales. - `kind` is a String, not an enum. Step kinds grow every time the flow engine gains a node type, and a consumer pinned to an older version of this crate must still deserialize a newer daemon's trace. Rejecting an unknown kind would fail the whole call record over one marker. Additive per the crate's field-evolution policy: optional with a serde default, skipped on serialize when absent, so a human-answered call puts nothing on the wire. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K9XwWFb2NB6pHaWzXBj3iH
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Middle of the three-repo train.
wavekat-platformaccepts and stores the field in wavekat/wavekat-platform#182; the daemon consumes it in wavekat/wavekat-voice#295.Carries the step-by-step story of a flow run — which prompt played, what the caller pressed, where the call went — from the daemon up to the platform, where the call-detail page pins them on the recording waveform as clickable markers.
Two shape decisions, both about surviving version skew
kindis aString, not an enum. Step kinds grow every time the flow engine gains a node type, and a consumer pinned to an older version of this crate must still deserialize a newer daemon's trace. Rejecting an unknown kind would fail the whole call record over one marker.Additive per this repo's field-evolution policy: optional with a serde default, skipped on serialize when absent, so a human-answered call puts nothing on the wire.
Per
CLAUDE.md: merging this without publishing leaves wavekat-voice#295 unable to build — itsCargo.tomlalready asks for0.0.22, and CI there will reportfailed to select a versionuntil the release exists. That's the guard rail, not a broken build.Verification
cargo test82 pass (3 new: trace round-trip pinning the per-step wire names, an unknown kind deserializing, and a human-answered call keepingflowStepsoff the wire entirely).cargo clippy --all-targets -D warningsandcargo fmt --checkclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01K9XwWFb2NB6pHaWzXBj3iH