Maybe I don't get it yet, but why do you need a new model for this? Wouldn't this more be an issue of "harness"/chat UI engineering?
All the current-generation models can oneshot HTML/Javascript frontends of comparable complexity (though maybe not as polished). The only difference is that you have to specifically ask them, and the result is not embedded in the chat.
It feels like it should be easy to have a harness provide a "show HTML widget in the chat" tool and a skill and/or system prompt that instructs the model to generate such widgets on-the-fly if the response could benefit from interactivity.
What am I missing here?