2.2.0

Added

• Optional bearer-token authentication for the converter service. A new plugin setting (converterApiToken, blank by default) accepts an opaque token; when set, the plugin attaches it as an Authorization: Bearer <token> header on every request to the converter. When blank, the header is omitted entirely and existing unauthenticated deployments continue to work unchanged. The token field is rendered as a masked input on the settings page, and the form shows an inline warning when the configured converter URL uses plain http:// while a token is present (submission is not blocked — the warning is advisory).