🦋 New version release - #502
Merged
Merged
Conversation
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/smooth-operator-server@1.15.0
Minor Changes
d73ca95: Add the
identity_intakeRich Interaction kind to the TypeScript server (structured name/email/phone lead capture) — the port of the Rust referenceidentity_intake.rs, hosted by default alongsidechoices. On anidentity_form-capable channel therequest_identity_intaketool parks the turn on a form; on a text-only channel it degrades to validated conversational collection. Both paths run the shared validator (required-fields present, email shape, phone normalized to E.164, per-field errors) and resume with the same canonical payload.Also adds the framework's kind-agnostic host-effect seam: a valid
submit_interaction(both the rich WS path and the conversational-fallback tool) now routes to a kind-specific host effect. Foridentity_intakethis stamps the captured contacts onto the session metadata (userName/contactEmail/contactPhone) — the same keys the pre-chat create path stashes and the OTP contact seam reads, so a captured contact is immediately OTP-contactable. Kinds with no effect (e.g.choices) are unaffected.