Sentinel Flags High-Risk XSS Vector in Vue Provider Definition, Forces Code Fix

A high-severity security vulnerability was identified and patched within the `packages/stage-pages` module, where the use of the `v-html` directive to inject `providerDefinition` content created an unnecessary cross-site scripting (XSS) vector. The content, sourced from i18n configurations, was plain text, but the `v-html` directive would have rendered any HTML within it, opening a potential attack path if future definitions were to include untrusted or malicious elements.

The fix was direct and definitive: the `v-html` usage was entirely removed and replaced with standard Vue template text interpolation (`{{ }}`). This change ensures Vue treats the content strictly as plain text, eliminating the XSS risk by design. The vulnerability was logged as a high-priority issue by the automated Sentinel system, which flagged the unnecessary use of a dangerous directive for rendering static configuration data.

The incident prompted an internal learning logged in `.jules/sentinel.md`, reinforcing a critical security principle for the development team: actively question if `v-html` is strictly necessary and strongly prefer safe text interpolation by default for rendering dynamic configuration and translations. This serves as a pointed reminder that even seemingly benign code patterns for troubleshooting or display can introduce significant security liabilities if not scrutinized.