Recipes with Component Modifiers Used Look like Corrupted UX in Server/Static Mode

I'm using both the server view for my recipes as well as the cookbook generator, but cookbook supports the component modifiers while the UX/cookcli natively do not. This means when using the webpage with the same recipes, things look like they're corrupted.

Ideally, things like optional would be supported in the UX/cookcli reader.

Compare how the cookbook generator handles component modifiers with the server/static UX and cookcli reader. Start by tracing modifier rendering in those paths, then verify that recipes using modifiers such as optional display correctly rather than appearing corrupted in the webpage and CLI reader.

Written by the indexing model from the issue text.