Naming is hard. I would rather not go through another round of API changes.

I would recommend to create interface that accept message objects directly, e.g. Html::element( 'div', [], $messageObj ) to reduce the need for developers to make a choice which output format to use.

I also support updating the documentation to say Message text that can contain unescaped HTML.

In T200907#4469340, @Nikerabbit wrote:

[...]
I would recommend to create interface that accept message objects directly, e.g. Html::element( 'div', [], $messageObj ) to reduce the need for developers to make a choice which output format to use.

This is one of the largest annoyances when dealing with messages that should go in an Html element.

In T200907#4469340, @Nikerabbit wrote:

I also support updating the documentation to say Message text that can contain unescaped HTML.

Seems like a no-brainer. I dare say that this is an absolute must, considering that there have been issues with unescaped HTML causing all kinds of problems, let's not make things more difficult for the developers.

There is also a plain() function to make the confusion even worse, with the difference between text() and plain() is that text() transforms {{..}} constructs, according to Message.php.