v1.2.0

Highlights

• Added first-class OAuth support for HubSpot, Intercom, and Slack template servers, covering authorization-code exchange, persisted provider metadata, and runtime credential injection for downstream launches.
• Added owner-side OAuth reauthorization for existing template servers, so Peta Console and related control-plane clients can refresh stored connector credentials without recreating the server configuration.

Fixes and Improvements

• Hardened Intercom OAuth handling by validating stored access tokens against Intercom's /me endpoint, persisting the provider region needed at runtime, and clearing stale OAuth state when Intercom later rejects the token.
• Tightened redirect URI persistence for browser-based OAuth flows by keeping redirect metadata only after compliance checks, which improves reauthorization safety for Peta Desk and other browser-driven clients.
• Expanded regression coverage around server creation, configuration, and OAuth lifecycle handling for HubSpot, Intercom, Slack, and reauthorization flows.

Operational Notes

• Slack OAuth requires Token Rotation to be enabled in the Slack OAuth application settings.
• Intercom does not issue refresh tokens; Peta Core now treats it as a validated long-lived token flow and will disable or unconfigure affected servers if the provider reports that the token is no longer valid.
• Reauthorization uses the server's persisted configTemplate.oAuthConfig and encrypted OAuth state instead of pulling fresh cloud template metadata during the exchange.