test(connections): follow Asana onto the direct-OAuth path

Left red by the step-4 commit and pushed that way: once live discovery began
outranking Asana's pinned customer-only ownership mode it became a direct
OAuth connect slug, but this assertion still said otherwise.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
scotttongandClaude Opus 5 committed 2026-09-30 11:10:57 -07:00
1 parent b7e0da33c9
commit bf237e424f
1 file changed
+7 -1
+7 -1
View File
@@ -15,7 +15,13 @@ describe("app connect policy", () => {
expect(MCP_DIRECT_OAUTH_CONNECT_SLUGS).toEqual(expect.arrayContaining(["jira", "notion", "sentry"]));
expect(isMcpDirectOAuthConnectSlug("notion")).toBe(true);
expect(isMcpDirectOAuthConnectSlug("jira")).toBe(true);
expect(isMcpDirectOAuthConnectSlug("asana")).toBe(false);
// PAP-659 step 4: Asana's own OAuth metadata advertises registration, and
// live discovery now outranks its pinned customer-only ownership mode, so
// it reaches the provider directly instead of the client-ID form.
expect(isMcpDirectOAuthConnectSlug("asana")).toBe(true);
// Still false, and for two different reasons worth keeping apart: GitHub's
// one-click path is Paperclip-managed rather than direct, and Slack really
// does require a customer-registered OAuth client.
expect(isMcpDirectOAuthConnectSlug("github")).toBe(false);
expect(isMcpDirectOAuthConnectSlug("slack")).toBe(false);
expect(isMcpDirectOAuthConnectSlug(null)).toBe(false);