No problem!
Actually, I should have emphasize the danger of careless usage of f-strings with user inputs and say that if you want to use it, use it in very restricted ways with knowing what your code actually do at your own risk. I missed that point making readers who skim my snippet and words take wrong impressions that multiline(""") with f-strings is just okay (No!) and easy to use (Maybe). At least the code snippet and one line sentence explanation doesn’t match quite well. I think it is always better to explain in concise and completed ways, considering various situations and levels of readers. I’ll try to do that at next time!
Oh… I don’t know what LiteralStr is. If it is LiteralString (PEP 675 – Arbitrary Literal String Type | peps.python.org), it’s also new to me. Thank you I have learned something new. PEP 675 Motivation part actually talk about this situation…awesome 
(although I don’t use static type checkers because I have a few personal opinions mentioned in Reasons to avoid static type checking — typing documentation which can be changed at anytime and eventually use it…)
Your comments totally make sense.
Thanks a lot. I have learned some lessons from what you have said.