Release v0.37.0 - a plugin credential provider can serve a built-in platform (#944, #946) · logly/mureo

Added

A plugin credential provider can stand in for a built-in platform (#944, #946). A provider registered via mureo.providers may declare serves_platform (google_ads / meta_ads / search_console). The Setup tab's "mureo integrations" row then reads configured when the provider's own section is complete, and the Setup wizard offers the provider as a third connection choice next to "official MCP" and "mureo standard" (Search Console gets its own choice), running the provider's credentials card on the auth step. /api/status carries plugin_platforms; /api/credentials/plugins carries serves_platform and configured per provider. A malformed declaration is logged and leaves only that provider out of the configure UI.

GA4 is back in the Setup wizard under a multi-account backend (#442 follow-up). GA4 is offered under every backend; the path/project inputs are skipped when the store already holds a complete ga4 section, and the write lands in the backend-resolved credentials path like every other env var. credentials_present.ga4 is true only when both service_account_path and project_id are set.

Shipped text no longer records how a change came about. A new CI step, scripts/check_comment_provenance.py, fails when a comment, docstring, doc or CHANGELOG line names who asked for or decided a change, a review pass, a workflow phase or an internal document instead of the reason the code has its shape. Existing occurrences are rewritten; the file walk shared with scripts/check_english_only.py now lives in scripts/shipped_text.py.
ga4-official documents what it actually accepts (#937): any ADC credential file works, and the provider also emits GOOGLE_CLOUD_PROJECT from the stored project id.