POML VS Code extension fixes `/>` bug

This is less a flashy release than proof that AI tooling often lives or dies on maintenance, not ideas. The update matters because a tiny syntax bug plus dependency drift can quietly break the whole editor-to-LLM loop.

• –The `/>` fix targets a real edge case for POML users embedding documents, where self-closing markup is common
• –Refreshing dependencies is necessary here, but it also introduced preview-panel regressions that only showed up in packaged VSIX builds
• –That packaging-only failure is a reminder that VS Code extensions can behave differently in debug vs distribution mode
• –The release keeps POML viable for prompt engineers who want modular templates, local model wiring, and editor-integrated execution
• –The likely upside is small but real: fewer copy-paste detours, less friction, and a better chance the format keeps a user base