docs: drop the dead capability assertion and the repeated deploy rationale

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L99mAR4LitqTcYY1Kn1ATH

frontend/src/lib/components/copilot/chat/global/sessionAccess.test.ts

@@ -73,7 +73,6 @@ describe('resolveSessionAccess', () => {
 		})
 		const caps = await capabilitiesFor({})
 		expect(caps.has('deploy')).toBe(false)
-		expect(caps.has('deploy_gated_kinds')).toBe(false)
 		expect(caps.has('write_draft')).toBe(true)
 	})
 

frontend/src/lib/components/copilot/chat/global/sessionAccess.ts

@@ -66,10 +66,8 @@ export async function resolveSessionAccess(workspace: string): Promise<SessionAc
 		capabilities.add('run_preview')
 	}
 
-	// `checkDeployPermission` is the whole gate for the gated kinds. Its refusals are
-	// per-workspace, but every one of them — operator included — is enforced server-side
-	// only where `check_deploy_rules` or the item handler runs, so none of them reaches a
-	// schedule or a trigger. Hence one capability, covering the gated kinds alone.
+	// Delegated whole to the shared preflight rather than re-derived here, so the
+	// session answers deploy exactly as the deploy panel does.
 	if ((await checkDeployPermission(workspace, me)).ok) {
 		capabilities.add('deploy')
 	}