Yes, you are.
The issue comes down to the link onebox, which is not shown because the embed content always gets wrapped in HTML tags. 
I know this sounds like a small nit (which it is), but the quality of life downside of having to edit this manually for each article is significant and something I wanted to fix for a long time.
What I want it to look like (using an example Discourse blog post):
Currently, I would have to mess with hidden elements on the website to be able to specifically scrape the URL and summary, and even then, the problem is the onebox not being displayed. The only thing I can more or less fully customize is the “Read the full blog post…” part at the bottom.
I guess what I’m asking for is the ability to add something to the JS snippet like this:
DiscourseEmbed = {
discourseUrl: 'https://forum.example.com/',
discourseEmbedUrl: 'https://blog.discourse.org/2024/03/a-warm-welcome-to-spiceworks',
discourseRaw: 'https://blog.discourse.org/2024/03/a-warm-welcome-to-spiceworks\n\nWe are thrilled to share the move of the Spiceworks community to Discourse! The Spiceworks team has worked closely with our migration team\n\n<small>Read the full blog post on <a href="https://blog.discourse.org/2024/03/a-warm-welcome-to-spiceworks/">discourse.org</a>. This post has been created automatically and replies will be shown on the website.</small>'
};
discourseEmbedRaw being equivalent to the raw value in a regular API request to /posts.json.
But I understand this might be an edge case requirement and is not relevant for most users. I guess I will try to solve this by creating the topics via API before the JS snippet attempts to do so.