ThreadCan we do an FSM while retaining the conversation?

I've been using ConversationHandler for a while and find it a bit hard to manage as conversations get more complex — especially when dealing with nested states, fallbacks, and re-entry logic. Has there been any discussion about implementing a more formal FSM (finite state machine) approach? Something with explicit state definitions, transitions, and guards would make complex conversation flows much easier to reason about and debug. Would love to hear if others feel the same or if there are plans in this direction.