refactor(copilot): read the chat capability off its operation declaration

The raw chat handler restated copilot.use in both the assertion and the
refusal, so changing chatOperations.send's policy would leave the route
over- or under-gated and answering the wrong refusal code. Read the
declaration once instead, including its 'none' case, where a declarative
surface asserts nothing and so does this.

Author: waleedlatif1

apps/sim/lib/copilot/chat/post.test.ts

@@ -141,6 +141,7 @@ vi.mock('@/lib/copilot/chat-status', () => ({
   },
 }))
 
+import { chatOperations } from '@/lib/copilot/application/operations'
 import { DEFAULT_PERMISSION_GROUP_CONFIG } from '@/lib/permission-groups/fields'
 import { handleUnifiedChatPost } from './post'
 
@@ -978,6 +979,15 @@ describe('handleUnifiedChatPost copilot.use capability gate', () => {
    * taken first and released by the handler's `finally`, so a retry is free to
    * start a turn.
    */
+  /**
+   * The capability this raw handler asserts is the one `chatOperations.send`
+   * declares, not a literal restated beside it — a declarative surface would
+   * enforce the declaration, and this one must agree with it.
+   */
+  it('enforces the capability the chat operation declares', () => {
+    expect(chatOperations.send.capability).toBe('copilot.use')
+  })
+
   it('refuses the send when the group withholds copilot.use', async () => {
     resolvePermissionGroupConfig.mockResolvedValue({
       ...DEFAULT_PERMISSION_GROUP_CONFIG,

apps/sim/lib/copilot/chat/post.ts

@@ -10,6 +10,7 @@ import { z } from 'zod'
 import { isZodError, validationErrorResponse } from '@/lib/api/server'
 import { getSession } from '@/lib/auth'
 import { resolveBillingAttribution } from '@/lib/billing/core/billing-attribution'
+import { chatOperations } from '@/lib/copilot/application/operations'
 import {
   DESKTOP_TERMINAL_HINT_ID_MAX_LENGTH,
   DESKTOP_TERMINAL_HINT_TEXT_MAX_LENGTH,
@@ -1125,6 +1126,10 @@ export async function handleUnifiedChatPost(req: NextRequest) {
       /**
        * permission-group-enforced: copilot.use — Chat is a raw handler rather
        * than a workspace operation, so the authorization funnel never sees it.
+       * The capability is read off `chatOperations.send` rather than restated,
+       * so the assertion and the refusal cannot drift from the declaration a
+       * declarative surface would enforce — including the `'none'` case, where
+       * a declarative surface asserts nothing and so does this.
        *
        * Gated on the workspace the turn actually lands in, which is the one
        * `resolveBranch` just resolved rather than the one the request asked
@@ -1140,17 +1145,19 @@ export async function handleUnifiedChatPost(req: NextRequest) {
        * taken above is released by the `finally`, so a refused send leaves a
        * later retry free to start a turn.
        */
+      const chatCapability = chatOperations.send.capability
       if (
         branch.workspaceId &&
+        chatCapability !== 'none' &&
         (await isWorkspaceCapabilityWithheld(
           authenticatedUserId,
           branch.workspaceId,
-          'copilot.use'
+          chatCapability
         ))
       ) {
         activeOtelRoot.span.setAttribute(TraceAttr.HttpStatusCode, 403)
         activeOtelRoot.finish('error')
-        return capabilityRefusalResponse('copilot.use')
+        return capabilityRefusalResponse(chatCapability)
       }
 
       let currentChat: ChatLoadResult['chat'] = null