matevip e0ce5e2ea7 fix(sso): gate SSO runtime beans on mateclaw.sso.enabled ... SsoService / SsoStateService / SsoController / SsoProviderRegistry were unconditional component-scanned beans, but their configuration (SsoProperties) is only registered by the conditional auto-configuration. With SSO disabled (the default) the services were still instantiated and startup failed: "required a bean of type SsoProperties that could not be found". Gate the four beans on the same mateclaw.sso.enabled=true condition so the SSO stack loads as a unit — disabled = no beans and no exposed endpoints; enabled = the auto-configuration provides SsoProperties and everything wires. Verified: backend starts clean with SSO disabled (default).		2026-06-26 10:27:16 +08:00
..
vip/mate	fix(sso): gate SSO runtime beans on mateclaw.sso.enabled	2026-06-26 10:27:16 +08:00