Lint

.agents/skills/add-block/SKILL.md

@@ -1,848 +0,0 @@
----
-name: add-block
-description: Create or update a Sim integration block with correct subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring. Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools.
----
-
-# Add Block Skill
-
-You are an expert at creating block configurations for Sim. You understand the serializer, subBlock types, conditions, dependsOn, modes, and all UI patterns.
-
-## Your Task
-
-When the user asks you to create a block:
-1. Create the block file in `apps/sim/blocks/blocks/{service}.ts`
-2. Configure all subBlocks with proper types, conditions, and dependencies
-3. Wire up tools correctly
-
-## Hard Rule: No Guessed Tool Outputs
-
-Blocks depend on tool outputs. If the underlying tool response schema is not documented or live-verified, you MUST tell the user instead of guessing block outputs.
-
-- Do NOT invent block outputs for undocumented tool responses
-- Do NOT describe unknown JSON shapes as if they were confirmed
-- Do NOT wire fields into the block just because they seem likely to exist
-
-If the tool outputs are not known, do one of these instead:
-1. Ask the user for sample tool responses
-2. Ask the user for test credentials so the tool responses can be verified
-3. Limit the block to operations whose outputs are documented
-4. Leave uncertain outputs out and explicitly tell the user what remains unknown
-
-## Block Configuration Structure
-
-```typescript
-import { {ServiceName}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {ServiceName}Block: BlockConfig = {
-  type: '{service}',                    // snake_case identifier
-  name: '{Service Name}',               // Human readable
-  description: 'Brief description',     // One sentence
-  longDescription: 'Detailed description for docs',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',                    // 'tools' | 'blocks' | 'triggers'
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
-  bgColor: '#HEXCOLOR',                 // Brand color
-  icon: {ServiceName}Icon,
-
-  // Auth mode
-  authMode: AuthMode.OAuth,             // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Define all UI fields here
-  ],
-
-  tools: {
-    access: ['tool_id_1', 'tool_id_2'], // Array of tool IDs this block can use
-    config: {
-      tool: (params) => `{service}_${params.operation}`,  // Tool selector function
-      params: (params) => ({
-        // Transform subBlock values to tool params
-      }),
-    },
-  },
-
-  inputs: {
-    // Optional: define expected inputs from other blocks
-  },
-
-  outputs: {
-    // Define outputs available to downstream blocks
-  },
-}
-```
-
-## SubBlock Types Reference
-
-**Critical:** Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions.
-
-### Text Inputs
-```typescript
-// Single-line input
-{ id: 'field', title: 'Label', type: 'short-input', placeholder: '...' }
-
-// Multi-line input
-{ id: 'field', title: 'Label', type: 'long-input', placeholder: '...', rows: 6 }
-
-// Password input
-{ id: 'apiKey', title: 'API Key', type: 'short-input', password: true }
-```
-
-### Selection Inputs
-```typescript
-// Dropdown (static options)
-{
-  id: 'operation',
-  title: 'Operation',
-  type: 'dropdown',
-  options: [
-    { label: 'Create', id: 'create' },
-    { label: 'Update', id: 'update' },
-  ],
-  value: () => 'create',  // Default value function
-}
-
-// Combobox (searchable dropdown)
-{
-  id: 'field',
-  title: 'Label',
-  type: 'combobox',
-  options: [...],
-  searchable: true,
-}
-```
-
-### Code/JSON Inputs
-```typescript
-{
-  id: 'code',
-  title: 'Code',
-  type: 'code',
-  language: 'javascript',  // 'javascript' | 'json' | 'python'
-  placeholder: '// Enter code...',
-}
-```
-
-### OAuth/Credentials
-```typescript
-{
-  id: 'credential',
-  title: 'Account',
-  type: 'oauth-input',
-  serviceId: '{service}',  // Must match OAuth provider service key
-  requiredScopes: getScopesForService('{service}'),  // Import from @/lib/oauth/utils
-  placeholder: 'Select account',
-  required: true,
-}
-```
-
-**Scopes:** Always use `getScopesForService(serviceId)` from `@/lib/oauth/utils` for `requiredScopes`. Never hardcode scope arrays — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-**Scope descriptions:** When adding a new OAuth provider, also add human-readable descriptions for all scopes in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`.
-
-### Selectors (with dynamic options)
-```typescript
-// Channel selector (Slack, Discord, etc.)
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  serviceId: '{service}',
-  placeholder: 'Select channel',
-  dependsOn: ['credential'],
-}
-
-// Project selector (Jira, etc.)
-{
-  id: 'project',
-  title: 'Project',
-  type: 'project-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-
-// File selector (Google Drive, etc.)
-{
-  id: 'file',
-  title: 'File',
-  type: 'file-selector',
-  serviceId: '{service}',
-  mimeType: 'application/pdf',
-  dependsOn: ['credential'],
-}
-
-// User selector
-{
-  id: 'user',
-  title: 'User',
-  type: 'user-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-```
-
-### Other Types
-```typescript
-// Switch/toggle
-{ id: 'enabled', type: 'switch' }
-
-// Slider
-{ id: 'temperature', title: 'Temperature', type: 'slider', min: 0, max: 2, step: 0.1 }
-
-// Table (key-value pairs)
-{ id: 'headers', title: 'Headers', type: 'table', columns: ['Key', 'Value'] }
-
-// File upload
-{
-  id: 'files',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,
-  acceptedTypes: 'image/*,application/pdf',
-}
-```
-
-## File Input Handling
-
-When your block accepts file uploads, use the basic/advanced mode pattern with `normalizeFileInput`.
-
-### Basic/Advanced File Pattern
-
-```typescript
-// Basic mode: Visual file upload
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from other blocks
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any subblock's `id` in the same block
-- Values are stored under subblock `id`, not `canonicalParamId`
-
-### Normalizing File Input in tools.config
-
-Use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  access: ['service_upload'],
-  config: {
-    tool: (params) => {
-      // Check all field IDs: uploadFile (basic), fileRef (advanced), fileContent (legacy)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `service_${params.operation}`
-    },
-  },
-}
-```
-
-**Why this pattern?**
-- Values come through as `params.uploadFile` or `params.fileRef` (the subblock IDs)
-- `canonicalParamId` only controls UI/schema mapping, not runtime values
-- `normalizeFileInput` handles JSON strings from advanced mode template resolution
-
-### File Input Types in `inputs`
-
-Use `type: 'json'` for file inputs:
-
-```typescript
-inputs: {
-  uploadFile: { type: 'json', description: 'Uploaded file (UserFile)' },
-  fileRef: { type: 'json', description: 'File reference from previous block' },
-  // Legacy field for backwards compatibility
-  fileContent: { type: 'string', description: 'Legacy: base64 encoded content' },
-}
-```
-
-### Multiple Files
-
-For multiple file uploads:
-
-```typescript
-{
-  id: 'attachments',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,  // Allow multiple files
-  maxSize: 25,     // Max size in MB per file
-  acceptedTypes: 'image/*,application/pdf,.doc,.docx',
-}
-
-// In tools.config:
-const normalizedFiles = normalizeFileInput(
-  params.attachments || params.attachmentRefs,
-  // No { single: true } - returns array
-)
-if (normalizedFiles) {
-  params.files = normalizedFiles
-}
-```
-
-## Condition Syntax
-
-Controls when a field is shown based on other field values.
-
-### Simple Condition
-```typescript
-condition: { field: 'operation', value: 'create' }
-// Shows when operation === 'create'
-```
-
-### Multiple Values (OR)
-```typescript
-condition: { field: 'operation', value: ['create', 'update'] }
-// Shows when operation is 'create' OR 'update'
-```
-
-### Negation
-```typescript
-condition: { field: 'operation', value: 'delete', not: true }
-// Shows when operation !== 'delete'
-```
-
-### Compound (AND)
-```typescript
-condition: {
-  field: 'operation',
-  value: 'send',
-  and: {
-    field: 'type',
-    value: 'dm',
-    not: true,
-  }
-}
-// Shows when operation === 'send' AND type !== 'dm'
-```
-
-### Complex Example
-```typescript
-condition: {
-  field: 'operation',
-  value: ['list', 'search'],
-  not: true,
-  and: {
-    field: 'authMethod',
-    value: 'oauth',
-  }
-}
-// Shows when operation NOT in ['list', 'search'] AND authMethod === 'oauth'
-```
-
-## DependsOn Pattern
-
-Controls when a field is enabled and when its options are refetched.
-
-### Simple Array (all must be set)
-```typescript
-dependsOn: ['credential']
-// Enabled only when credential has a value
-// Options refetch when credential changes
-
-dependsOn: ['credential', 'projectId']
-// Enabled only when BOTH have values
-```
-
-### Complex (all + any)
-```typescript
-dependsOn: {
-  all: ['authMethod'],           // All must be set
-  any: ['credential', 'apiKey']  // At least one must be set
-}
-// Enabled when authMethod is set AND (credential OR apiKey is set)
-```
-
-## Required Pattern
-
-Can be boolean or condition-based.
-
-### Simple Boolean
-```typescript
-required: true
-required: false
-```
-
-### Conditional Required
-```typescript
-required: { field: 'operation', value: 'create' }
-// Required only when operation === 'create'
-
-required: { field: 'operation', value: ['create', 'update'] }
-// Required when operation is 'create' OR 'update'
-```
-
-## Mode Pattern (Basic vs Advanced)
-
-Controls which UI view shows the field.
-
-### Mode Options
-- `'basic'` - Only in basic view (default UI)
-- `'advanced'` - Only in advanced view
-- `'both'` - Both views (default if not specified)
-- `'trigger'` - Only in trigger configuration
-
-### canonicalParamId Pattern
-
-Maps multiple UI fields to a single serialized parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  dependsOn: ['credential'],
-}
-
-// Advanced mode: Manual input
-{
-  id: 'channelId',
-  title: 'Channel ID',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  placeholder: 'Enter channel ID manually',
-}
-```
-
-**How it works:**
-- In basic mode: `channel` selector value → `params.channel`
-- In advanced mode: `channelId` input value → `params.channel`
-- The serializer consolidates based on current mode
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any other subblock's `id` in the same block (causes conflicts)
-- `canonicalParamId` must be unique per block (only one basic/advanced pair per canonicalParamId)
-- ONLY use `canonicalParamId` to link basic/advanced mode alternatives for the same logical parameter
-- Do NOT use it for any other purpose
-
-## WandConfig Pattern
-
-Enables AI-assisted field generation.
-
-```typescript
-{
-  id: 'query',
-  title: 'Query',
-  type: 'code',
-  language: 'json',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a query based on the user request. Return ONLY the JSON.',
-    placeholder: 'Describe what you want to query...',
-    generationType: 'json-object',  // Optional: affects AI behavior
-    maintainHistory: true,          // Optional: keeps conversation context
-  },
-}
-```
-
-### Generation Types
-- `'javascript-function-body'` - JS code generation
-- `'json-object'` - Raw JSON (adds "no markdown" instruction)
-- `'json-schema'` - JSON Schema definitions
-- `'sql-query'` - SQL statements
-- `'timestamp'` - Adds current date/time context
-
-## Tools Configuration
-
-**Important:** `tools.config.tool` runs during serialization before variable resolution. Put `Number()` and other type coercions in `tools.config.params` instead, which runs at execution time after variables are resolved.
-
-**Preferred:** Use tool names directly as dropdown option IDs to avoid switch cases:
-```typescript
-// Dropdown options use tool IDs directly
-options: [
-  { label: 'Create', id: 'service_create' },
-  { label: 'Read', id: 'service_read' },
-]
-
-// Tool selector just returns the operation value
-tool: (params) => params.operation,
-```
-
-### With Parameter Transformation
-```typescript
-tools: {
-  access: ['service_action'],
-  config: {
-    tool: (params) => 'service_action',
-    params: (params) => ({
-      id: params.resourceId,
-      data: typeof params.data === 'string' ? JSON.parse(params.data) : params.data,
-    }),
-  },
-}
-```
-
-### V2 Versioned Tool Selector
-```typescript
-import { createVersionedToolSelector } from '@/blocks/utils'
-
-tools: {
-  access: [
-    'service_create_v2',
-    'service_read_v2',
-    'service_update_v2',
-  ],
-  config: {
-    tool: createVersionedToolSelector({
-      baseToolSelector: (params) => `service_${params.operation}`,
-      suffix: '_v2',
-      fallbackToolId: 'service_create_v2',
-    }),
-  },
-}
-```
-
-## Outputs Definition
-
-**IMPORTANT:** Block outputs have a simpler schema than tool outputs. Block outputs do NOT support:
-- `optional: true` - This is only for tool outputs
-- `items` property - This is only for tool outputs with array types
-
-Block outputs only support:
-- `type` - The data type ('string', 'number', 'boolean', 'json', 'array')
-- `description` - Human readable description
-- Nested object structure (for complex types)
-
-```typescript
-outputs: {
-  // Simple outputs
-  id: { type: 'string', description: 'Resource ID' },
-  success: { type: 'boolean', description: 'Whether operation succeeded' },
-
-  // Use type: 'json' for complex objects or arrays (NOT type: 'array' with items)
-  items: { type: 'json', description: 'List of items' },
-  metadata: { type: 'json', description: 'Response metadata' },
-
-  // Nested outputs (for structured data)
-  user: {
-    id: { type: 'string', description: 'User ID' },
-    name: { type: 'string', description: 'User name' },
-    email: { type: 'string', description: 'User email' },
-  },
-}
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **describe the inner fields in the description** so downstream blocks know what properties are available. For well-known, stable objects, use nested output definitions instead:
-
-```typescript
-outputs: {
-  // BAD: Opaque json with no info about what's inside
-  plan: { type: 'json', description: 'Zone plan information' },
-
-  // GOOD: Describe the known fields in the description
-  plan: {
-    type: 'json',
-    description: 'Zone plan information (id, name, price, currency, frequency, is_subscribed)',
-  },
-
-  // BEST: Use nested output definition when the shape is stable and well-known
-  plan: {
-    id: { type: 'string', description: 'Plan identifier' },
-    name: { type: 'string', description: 'Plan name' },
-    price: { type: 'number', description: 'Plan price' },
-    currency: { type: 'string', description: 'Price currency' },
-  },
-}
-```
-
-Use the nested pattern when:
-- The object has a small, stable set of fields (< 10)
-- Downstream blocks will commonly access specific properties
-- The API response shape is well-documented and unlikely to change
-
-Use `type: 'json'` with a descriptive string when:
-- The object has many fields or a dynamic shape
-- It represents a list/array of items
-- The shape varies by operation
-
-If the output shape is unknown because the underlying tool response is undocumented, you MUST tell the user and stop. Unknown is not the same as variable. Never guess block outputs.
-
-## V2 Block Pattern
-
-When creating V2 blocks (alongside legacy V1):
-
-```typescript
-// V1 Block - mark as legacy
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service (Legacy)',
-  hideFromToolbar: true,  // Hide from toolbar
-  // ... rest of config
-}
-
-// V2 Block - visible, uses V2 tools
-export const ServiceV2Block: BlockConfig = {
-  type: 'service_v2',
-  name: 'Service',              // Clean name
-  hideFromToolbar: false,       // Visible
-  subBlocks: ServiceBlock.subBlocks,  // Reuse UI
-  tools: {
-    access: ServiceBlock.tools?.access?.map(id => `${id}_v2`) || [],
-    config: {
-      tool: createVersionedToolSelector({
-        baseToolSelector: (params) => (ServiceBlock.tools?.config as any)?.tool(params),
-        suffix: '_v2',
-        fallbackToolId: 'service_default_v2',
-      }),
-      params: ServiceBlock.tools?.config?.params,
-    },
-  },
-  outputs: {
-    // Flat, API-aligned outputs (not wrapped in content/metadata)
-  },
-}
-```
-
-## Registering Blocks
-
-After creating the block, remind the user to:
-1. Import in `apps/sim/blocks/registry.ts`
-2. Add to the `registry` object (alphabetically):
-
-```typescript
-import { ServiceBlock } from '@/blocks/blocks/service'
-
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  service: ServiceBlock,
-}
-```
-
-## Complete Example
-
-```typescript
-import { ServiceIcon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service',
-  description: 'Integrate with Service API',
-  longDescription: 'Full description for documentation...',
-  docsLink: 'https://docs.sim.ai/tools/service',
-  category: 'tools',
-  integrationType: IntegrationType.DeveloperTools,
-  tags: ['oauth', 'api'],
-  bgColor: '#FF6B6B',
-  icon: ServiceIcon,
-  authMode: AuthMode.OAuth,
-
-  subBlocks: [
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Create', id: 'create' },
-        { label: 'Read', id: 'read' },
-        { label: 'Update', id: 'update' },
-        { label: 'Delete', id: 'delete' },
-      ],
-      value: () => 'create',
-    },
-    {
-      id: 'credential',
-      title: 'Service Account',
-      type: 'oauth-input',
-      serviceId: 'service',
-      requiredScopes: getScopesForService('service'),
-      placeholder: 'Select account',
-      required: true,
-    },
-    {
-      id: 'resourceId',
-      title: 'Resource ID',
-      type: 'short-input',
-      placeholder: 'Enter resource ID',
-      condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-      required: { field: 'operation', value: ['read', 'update', 'delete'] },
-    },
-    {
-      id: 'name',
-      title: 'Name',
-      type: 'short-input',
-      placeholder: 'Resource name',
-      condition: { field: 'operation', value: ['create', 'update'] },
-      required: { field: 'operation', value: 'create' },
-    },
-  ],
-
-  tools: {
-    access: ['service_create', 'service_read', 'service_update', 'service_delete'],
-    config: {
-      tool: (params) => `service_${params.operation}`,
-    },
-  },
-
-  outputs: {
-    id: { type: 'string', description: 'Resource ID' },
-    name: { type: 'string', description: 'Resource name' },
-    createdAt: { type: 'string', description: 'Creation timestamp' },
-  },
-}
-```
-
-## Connecting Blocks with Triggers
-
-If the service supports webhooks, connect the block to its triggers.
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const ServiceBlock: BlockConfig = {
-  // ... basic config ...
-
-  triggers: {
-    enabled: true,
-    available: ['service_event_a', 'service_event_b', 'service_webhook'],
-  },
-
-  subBlocks: [
-    // Tool subBlocks first...
-    { id: 'operation', /* ... */ },
-
-    // Then spread trigger subBlocks
-    ...getTrigger('service_event_a').subBlocks,
-    ...getTrigger('service_event_b').subBlocks,
-    ...getTrigger('service_webhook').subBlocks,
-  ],
-}
-```
-
-See the `/add-trigger` skill for creating triggers.
-
-## Icon Requirement
-
-If the icon doesn't already exist in `@/components/icons.tsx`, **do NOT search for it yourself**. After completing the block, ask the user to provide the SVG:
-
-```
-The block is complete, but I need an icon for {Service}.
-Please provide the SVG and I'll convert it to a React component.
-
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-```
-
-## Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. This includes:
-- Pagination tokens
-- Time range filters (start/end time)
-- Sort order options
-- Reply settings
-- Rarely used IDs (e.g., reply-to tweet ID, quote tweet ID)
-- Max results / limits
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  placeholder: 'ISO 8601 timestamp',
-  condition: { field: 'operation', value: ['search', 'list'] },
-  mode: 'advanced',  // Rarely used, hide from basic view
-}
-```
-
-## WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually, such as timestamps, comma-separated lists, and complex query strings. This gives users an AI-assisted input experience.
-
-```typescript
-// Timestamps - use generationType: 'timestamp' to inject current date context
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp based on the user description. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-
-// Comma-separated lists - simple prompt without generationType
-{
-  id: 'mediaIds',
-  title: 'Media IDs',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a comma-separated list of media IDs. Return ONLY the comma-separated values.',
-  },
-}
-```
-
-## Naming Convention
-
-All tool IDs referenced in `tools.access` and returned by `tools.config.tool` MUST use `snake_case` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase.
-
-## Checklist Before Finishing
-
-- [ ] `integrationType` is set to the correct `IntegrationType` enum value
-- [ ] `tags` array includes all applicable `IntegrationTag` values
-- [ ] All subBlocks have `id`, `title` (except switch), and `type`
-- [ ] Conditions use correct syntax (field, value, not, and)
-- [ ] DependsOn set for fields that need other values
-- [ ] Required fields marked correctly (boolean or condition)
-- [ ] OAuth inputs have correct `serviceId` and `requiredScopes: getScopesForService(serviceId)`
-- [ ] Scope descriptions added to `SCOPE_DESCRIPTIONS` in `lib/oauth/utils.ts` for any new scopes
-- [ ] Tools.access lists all tool IDs (snake_case)
-- [ ] Tools.config.tool returns correct tool ID (snake_case)
-- [ ] Outputs match tool outputs
-- [ ] Block registered in registry.ts
-- [ ] If icon missing: asked user to provide SVG
-- [ ] If triggers exist: `triggers` config set, trigger subBlocks spread
-- [ ] Optional/rarely-used fields set to `mode: 'advanced'`
-- [ ] Timestamps and complex inputs have `wandConfig` enabled
-
-## Final Validation (Required)
-
-After creating the block, you MUST validate it against every tool it references:
-
-1. **Read every tool definition** that appears in `tools.access` — do not skip any
-2. **For each tool, verify the block has correct:**
-   - SubBlock inputs that cover all required tool params (with correct `condition` to show for that operation)
-   - SubBlock input types that match the tool param types (e.g., dropdown for enums, short-input for strings)
-   - `tools.config.params` correctly maps subBlock IDs to tool param names (if they differ)
-   - Type coercions in `tools.config.params` for any params that need conversion (Number(), Boolean(), JSON.parse())
-3. **Verify block outputs** cover the key fields returned by all tools
-4. **Verify conditions** — each subBlock should only show for the operations that actually use it
-5. **If any tool outputs are still unknown**, explicitly tell the user instead of guessing block outputs

.agents/skills/add-block/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Block"
-  short_description: "Build a Sim block definition"
-  brand_color: "#2563EB"
-  default_prompt: "Use $add-block to create or update the block for a Sim integration."

.agents/skills/add-connector/SKILL.md

@@ -1,545 +0,0 @@
----
-name: add-connector
-description: Add or update a Sim knowledge base connector for syncing documents from an external source, including auth mode, config fields, pagination, document mapping, tags, and registry wiring. Use when working in `apps/sim/connectors/{service}/` or adding a new external document source.
----
-
-# Add Connector Skill
-
-You are an expert at adding knowledge base connectors to Sim. A connector syncs documents from an external source (Confluence, Google Drive, Notion, etc.) into a knowledge base.
-
-## Your Task
-
-When the user asks you to create a connector:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Determine the auth mode: **OAuth** (if Sim already has an OAuth provider for the service) or **API key** (if the service uses API key / Bearer token auth)
-3. Create the connector directory and config
-4. Register it in the connector registry
-
-## Hard Rule: No Guessed Response Or Document Schemas
-
-If the service docs do not clearly show the document list response, document fetch response, pagination shape, or metadata fields, you MUST tell the user instead of guessing.
-
-- Do NOT invent document fields
-- Do NOT guess pagination cursors or next-page fields
-- Do NOT infer metadata/tag mappings from unrelated endpoints
-- Do NOT fabricate `ExternalDocument` content structure from partial docs
-
-If the source schema is unknown, do one of these instead:
-1. Ask the user for sample API responses
-2. Ask the user for test credentials so you can verify live payloads
-3. Implement only the documented parts of the connector
-4. Leave the connector incomplete and explicitly say which fields remain unknown
-
-## Directory Structure
-
-Create files in `apps/sim/connectors/{service}/`:
-```
-connectors/{service}/
-├── index.ts          # Barrel export
-└── {service}.ts      # ConnectorConfig definition
-```
-
-## Authentication
-
-Connectors use a discriminated union for auth config (`ConnectorAuthConfig` in `connectors/types.ts`):
-
-```typescript
-type ConnectorAuthConfig =
-  | { mode: 'oauth'; provider: OAuthService; requiredScopes?: string[] }
-  | { mode: 'apiKey'; label?: string; placeholder?: string }
-```
-
-### OAuth mode
-For services with existing OAuth providers in `apps/sim/lib/oauth/types.ts`. The `provider` must match an `OAuthService`. The modal shows a credential picker and handles token refresh automatically.
-
-### API key mode
-For services that use API key / Bearer token auth. The modal shows a password input with the configured `label` and `placeholder`. The API key is encrypted at rest using AES-256-GCM and stored in a dedicated `encryptedApiKey` column on the connector record. The sync engine decrypts it automatically — connectors receive the raw access token in `listDocuments`, `getDocument`, and `validateConfig`.
-
-## ConnectorConfig Structure
-
-### OAuth connector example
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { {Service}Icon } from '@/components/icons'
-import { fetchWithRetry } from '@/lib/knowledge/documents/utils'
-import type { ConnectorConfig, ExternalDocument, ExternalDocumentList } from '@/connectors/types'
-
-const logger = createLogger('{Service}Connector')
-
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'oauth',
-    provider: '{service}',          // Must match OAuthService in lib/oauth/types.ts
-    requiredScopes: ['read:...'],
-  },
-
-  configFields: [
-    // Rendered dynamically by the add-connector modal UI
-    // Supports 'short-input' and 'dropdown' types
-  ],
-
-  listDocuments: async (accessToken, sourceConfig, cursor) => {
-    // Return metadata stubs with contentDeferred: true (if per-doc content fetch needed)
-    // Or full documents with content (if list API returns content inline)
-    // Return { documents: ExternalDocument[], nextCursor?, hasMore }
-  },
-
-  getDocument: async (accessToken, sourceConfig, externalId) => {
-    // Fetch full content for a single document
-    // Return ExternalDocument with contentDeferred: false, or null
-  },
-
-  validateConfig: async (accessToken, sourceConfig) => {
-    // Return { valid: true } or { valid: false, error: 'message' }
-  },
-
-  // Optional: map source metadata to semantic tag keys (translated to slots by sync engine)
-  mapTags: (metadata) => {
-    // Return Record<string, unknown> with keys matching tagDefinitions[].id
-  },
-}
-```
-
-Only map fields in `listDocuments`, `getDocument`, `validateConfig`, and `mapTags` when the source payload shape is documented or live-verified. If not, tell the user and stop rather than guessing.
-
-### API key connector example
-
-```typescript
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'apiKey',
-    label: 'API Key',                       // Shown above the input field
-    placeholder: 'Enter your {Service} API key',  // Input placeholder
-  },
-
-  configFields: [ /* ... */ ],
-  listDocuments: async (accessToken, sourceConfig, cursor) => { /* ... */ },
-  getDocument: async (accessToken, sourceConfig, externalId) => { /* ... */ },
-  validateConfig: async (accessToken, sourceConfig) => { /* ... */ },
-}
-```
-
-## ConfigField Types
-
-The add-connector modal renders these automatically — no custom UI needed.
-
-Three field types are supported: `short-input`, `dropdown`, and `selector`.
-
-```typescript
-// Text input
-{
-  id: 'domain',
-  title: 'Domain',
-  type: 'short-input',
-  placeholder: 'yoursite.example.com',
-  required: true,
-}
-
-// Dropdown (static options)
-{
-  id: 'contentType',
-  title: 'Content Type',
-  type: 'dropdown',
-  required: false,
-  options: [
-    { label: 'Pages only', id: 'page' },
-    { label: 'Blog posts only', id: 'blogpost' },
-    { label: 'All content', id: 'all' },
-  ],
-}
-```
-
-## Dynamic Selectors (Canonical Pairs)
-
-Use `type: 'selector'` to fetch options dynamically from the existing selector registry (`hooks/selectors/registry.ts`). Selectors are always paired with a manual fallback input using the **canonical pair** pattern — a `selector` field (basic mode) and a `short-input` field (advanced mode) linked by `canonicalParamId`.
-
-The user sees a toggle button (ArrowLeftRight) to switch between the selector dropdown and manual text input. On submit, the modal resolves each canonical pair to the active mode's value, keyed by `canonicalParamId`.
-
-### Rules
-
-1. **Every selector field MUST have a canonical pair** — a corresponding `short-input` (or `dropdown`) field with the same `canonicalParamId` and `mode: 'advanced'`.
-2. **`required` must be set identically on both fields** in a pair. If the selector is required, the manual input must also be required.
-3. **`canonicalParamId` must match the key the connector expects in `sourceConfig`** (e.g. `baseId`, `channel`, `teamId`). The advanced field's `id` should typically match `canonicalParamId`.
-4. **`dependsOn` references the selector field's `id`**, not the `canonicalParamId`. The modal propagates dependency clearing across canonical siblings automatically — changing either field in a parent pair clears dependent children.
-
-### Selector canonical pair example (Airtable base → table cascade)
-
-```typescript
-configFields: [
-  // Base: selector (basic) + manual (advanced)
-  {
-    id: 'baseSelector',
-    title: 'Base',
-    type: 'selector',
-    selectorKey: 'airtable.bases',     // Must exist in hooks/selectors/registry.ts
-    canonicalParamId: 'baseId',
-    mode: 'basic',
-    placeholder: 'Select a base',
-    required: true,
-  },
-  {
-    id: 'baseId',
-    title: 'Base ID',
-    type: 'short-input',
-    canonicalParamId: 'baseId',
-    mode: 'advanced',
-    placeholder: 'e.g. appXXXXXXXXXXXXXX',
-    required: true,
-  },
-  // Table: selector depends on base (basic) + manual (advanced)
-  {
-    id: 'tableSelector',
-    title: 'Table',
-    type: 'selector',
-    selectorKey: 'airtable.tables',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'basic',
-    dependsOn: ['baseSelector'],       // References the selector field ID
-    placeholder: 'Select a table',
-    required: true,
-  },
-  {
-    id: 'tableIdOrName',
-    title: 'Table Name or ID',
-    type: 'short-input',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'advanced',
-    placeholder: 'e.g. Tasks',
-    required: true,
-  },
-  // Non-selector fields stay as-is
-  { id: 'maxRecords', title: 'Max Records', type: 'short-input', ... },
-]
-```
-
-### Selector with domain dependency (Jira/Confluence pattern)
-
-When a selector depends on a plain `short-input` field (no canonical pair), `dependsOn` references that field's `id` directly. The `domain` field's value maps to `SelectorContext.domain` automatically via `SELECTOR_CONTEXT_FIELDS`.
-
-```typescript
-configFields: [
-  {
-    id: 'domain',
-    title: 'Jira Domain',
-    type: 'short-input',
-    placeholder: 'yoursite.atlassian.net',
-    required: true,
-  },
-  {
-    id: 'projectSelector',
-    title: 'Project',
-    type: 'selector',
-    selectorKey: 'jira.projects',
-    canonicalParamId: 'projectKey',
-    mode: 'basic',
-    dependsOn: ['domain'],
-    placeholder: 'Select a project',
-    required: true,
-  },
-  {
-    id: 'projectKey',
-    title: 'Project Key',
-    type: 'short-input',
-    canonicalParamId: 'projectKey',
-    mode: 'advanced',
-    placeholder: 'e.g. ENG, PROJ',
-    required: true,
-  },
-]
-```
-
-### How `dependsOn` maps to `SelectorContext`
-
-The connector selector field builds a `SelectorContext` from dependency values. For the mapping to work, each dependency's `canonicalParamId` (or field `id` for non-canonical fields) must exist in `SELECTOR_CONTEXT_FIELDS` (`lib/workflows/subblocks/context.ts`):
-
-```
-oauthCredential, domain, teamId, projectId, knowledgeBaseId, planId,
-siteId, collectionId, spreadsheetId, fileId, baseId, datasetId, serviceDeskId
-```
-
-### Available selector keys
-
-Check `hooks/selectors/types.ts` for the full `SelectorKey` union. Common ones for connectors:
-
-| SelectorKey | Context Deps | Returns |
-|-------------|-------------|---------|
-| `airtable.bases` | credential | Base ID + name |
-| `airtable.tables` | credential, `baseId` | Table ID + name |
-| `slack.channels` | credential | Channel ID + name |
-| `gmail.labels` | credential | Label ID + name |
-| `google.calendar` | credential | Calendar ID + name |
-| `linear.teams` | credential | Team ID + name |
-| `linear.projects` | credential, `teamId` | Project ID + name |
-| `jira.projects` | credential, `domain` | Project key + name |
-| `confluence.spaces` | credential, `domain` | Space key + name |
-| `notion.databases` | credential | Database ID + name |
-| `asana.workspaces` | credential | Workspace GID + name |
-| `microsoft.teams` | credential | Team ID + name |
-| `microsoft.channels` | credential, `teamId` | Channel ID + name |
-| `webflow.sites` | credential | Site ID + name |
-| `outlook.folders` | credential | Folder ID + name |
-
-## ExternalDocument Shape
-
-Every document returned from `listDocuments`/`getDocument` must include:
-
-```typescript
-{
-  externalId: string          // Source-specific unique ID
-  title: string               // Document title
-  content: string             // Extracted plain text (or '' if contentDeferred)
-  contentDeferred?: boolean   // true = content will be fetched via getDocument
-  mimeType: 'text/plain'     // Always text/plain (content is extracted)
-  contentHash: string         // Metadata-based hash for change detection
-  sourceUrl?: string          // Link back to original (stored on document record)
-  metadata?: Record<string, unknown>  // Source-specific data (fed to mapTags)
-}
-```
-
-## Content Deferral (Required for file/content-download connectors)
-
-**All connectors that require per-document API calls to fetch content MUST use `contentDeferred: true`.** This is the standard pattern — `listDocuments` returns lightweight metadata stubs, and content is fetched lazily by the sync engine via `getDocument` only for new/changed documents.
-
-This pattern is critical for reliability: the sync engine processes documents in batches and enqueues each batch for processing immediately. If a sync times out, all previously-batched documents are already queued. Without deferral, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-### When to use `contentDeferred: true`
-
-- The service's list API does NOT return document content (only metadata)
-- Content requires a separate download/export API call per document
-- Examples: Google Drive, OneDrive, SharePoint, Dropbox, Notion, Confluence, Gmail, Obsidian, Evernote, GitHub
-
-### When NOT to use `contentDeferred`
-
-- The list API already returns the full content inline (e.g., Slack messages, Reddit posts, HubSpot notes)
-- No per-document API call is needed to get content
-
-### Content Hash Strategy
-
-Use a **metadata-based** `contentHash` — never a content-based hash. The hash must be derivable from the list response metadata alone, so the sync engine can detect changes without downloading content.
-
-Good metadata hash sources:
-- `modifiedTime` / `lastModifiedDateTime` — changes when file is edited
-- Git blob SHA — unique per content version
-- API-provided content hash (e.g., Dropbox `content_hash`)
-- Version number (e.g., Confluence page version)
-
-Format: `{service}:{id}:{changeIndicator}`
-
-```typescript
-// Google Drive: modifiedTime changes on edit
-contentHash: `gdrive:${file.id}:${file.modifiedTime ?? ''}`
-
-// GitHub: blob SHA is a content-addressable hash
-contentHash: `gitsha:${item.sha}`
-
-// Dropbox: API provides content_hash
-contentHash: `dropbox:${entry.id}:${entry.content_hash ?? entry.server_modified}`
-
-// Confluence: version number increments on edit
-contentHash: `confluence:${page.id}:${page.version.number}`
-```
-
-**Critical invariant:** The `contentHash` MUST be identical whether produced by `listDocuments` (stub) or `getDocument` (full doc). Both should use the same stub function to guarantee this.
-
-### Implementation Pattern
-
-```typescript
-// 1. Create a stub function (sync, no API calls)
-function fileToStub(file: ServiceFile): ExternalDocument {
-  return {
-    externalId: file.id,
-    title: file.name || 'Untitled',
-    content: '',
-    contentDeferred: true,
-    mimeType: 'text/plain',
-    sourceUrl: `https://service.com/file/${file.id}`,
-    contentHash: `service:${file.id}:${file.modifiedTime ?? ''}`,
-    metadata: { /* fields needed by mapTags */ },
-  }
-}
-
-// 2. listDocuments returns stubs (fast, metadata only)
-listDocuments: async (accessToken, sourceConfig, cursor) => {
-  const response = await fetchWithRetry(listUrl, { ... })
-  const files = (await response.json()).files
-  const documents = files.map(fileToStub)
-  return { documents, nextCursor, hasMore }
-}
-
-// 3. getDocument fetches content and returns full doc with SAME contentHash
-getDocument: async (accessToken, sourceConfig, externalId) => {
-  const metadata = await fetchWithRetry(metadataUrl, { ... })
-  const file = await metadata.json()
-  if (file.trashed) return null
-
-  try {
-    const content = await fetchContent(accessToken, file)
-    if (!content.trim()) return null
-    const stub = fileToStub(file)
-    return { ...stub, content, contentDeferred: false }
-  } catch (error) {
-    logger.warn(`Failed to fetch content for: ${file.name}`, { error })
-    return null
-  }
-}
-```
-
-### Reference Implementations
-
-- **Google Drive**: `connectors/google-drive/google-drive.ts` — file download/export with `modifiedTime` hash
-- **GitHub**: `connectors/github/github.ts` — git blob SHA hash
-- **Notion**: `connectors/notion/notion.ts` — blocks API with `last_edited_time` hash
-- **Confluence**: `connectors/confluence/confluence.ts` — version number hash
-
-## tagDefinitions — Declared Tag Definitions
-
-Declare which tags the connector populates using semantic IDs. Shown in the add-connector modal as opt-out checkboxes.
-On connector creation, slots are **dynamically assigned** via `getNextAvailableSlot` — connectors never hardcode slot names.
-
-```typescript
-tagDefinitions: [
-  { id: 'labels', displayName: 'Labels', fieldType: 'text' },
-  { id: 'version', displayName: 'Version', fieldType: 'number' },
-  { id: 'lastModified', displayName: 'Last Modified', fieldType: 'date' },
-],
-```
-
-Each entry has:
-- `id`: Semantic key matching a key returned by `mapTags` (e.g. `'labels'`, `'version'`)
-- `displayName`: Human-readable name shown in the UI (e.g. "Labels", "Last Modified")
-- `fieldType`: `'text'` | `'number'` | `'date'` | `'boolean'` — determines which slot pool to draw from
-
-Users can opt out of specific tags in the modal. Disabled IDs are stored in `sourceConfig.disabledTagIds`.
-The assigned mapping (`semantic id → slot`) is stored in `sourceConfig.tagSlotMapping`.
-
-## mapTags — Metadata to Semantic Keys
-
-Maps source metadata to semantic tag keys. Required if `tagDefinitions` is set.
-The sync engine calls this automatically and translates semantic keys to actual DB slots
-using the `tagSlotMapping` stored on the connector.
-
-Return keys must match the `id` values declared in `tagDefinitions`.
-
-```typescript
-mapTags: (metadata: Record<string, unknown>): Record<string, unknown> => {
-  const result: Record<string, unknown> = {}
-
-  // Validate arrays before casting — metadata may be malformed
-  const labels = Array.isArray(metadata.labels) ? (metadata.labels as string[]) : []
-  if (labels.length > 0) result.labels = labels.join(', ')
-
-  // Validate numbers — guard against NaN
-  if (metadata.version != null) {
-    const num = Number(metadata.version)
-    if (!Number.isNaN(num)) result.version = num
-  }
-
-  // Validate dates — guard against Invalid Date
-  if (typeof metadata.lastModified === 'string') {
-    const date = new Date(metadata.lastModified)
-    if (!Number.isNaN(date.getTime())) result.lastModified = date
-  }
-
-  return result
-}
-```
-
-## External API Calls — Use `fetchWithRetry`
-
-All external API calls must use `fetchWithRetry` from `@/lib/knowledge/documents/utils` instead of raw `fetch()`. This provides exponential backoff with retries on 429/502/503/504 errors. It returns a standard `Response` — all `.ok`, `.json()`, `.text()` checks work unchanged.
-
-For `validateConfig` (user-facing, called on save), pass `VALIDATE_RETRY_OPTIONS` to cap wait time at ~7s. Background operations (`listDocuments`, `getDocument`) use the built-in defaults (5 retries, ~31s max).
-
-```typescript
-import { VALIDATE_RETRY_OPTIONS, fetchWithRetry } from '@/lib/knowledge/documents/utils'
-
-// Background sync — use defaults
-const response = await fetchWithRetry(url, {
-  method: 'GET',
-  headers: { Authorization: `Bearer ${accessToken}` },
-})
-
-// validateConfig — tighter retry budget
-const response = await fetchWithRetry(url, { ... }, VALIDATE_RETRY_OPTIONS)
-```
-
-## sourceUrl
-
-If `ExternalDocument.sourceUrl` is set, the sync engine stores it on the document record. Always construct the full URL (not a relative path).
-
-## Sync Engine Behavior (Do Not Modify)
-
-The sync engine (`lib/knowledge/connectors/sync-engine.ts`) is connector-agnostic. It:
-1. Calls `listDocuments` with pagination until `hasMore` is false
-2. Compares `contentHash` to detect new/changed/unchanged documents
-3. Stores `sourceUrl` and calls `mapTags` on insert/update automatically
-4. Handles soft-delete of removed documents
-5. Resolves access tokens automatically — OAuth tokens are refreshed, API keys are decrypted from the `encryptedApiKey` column
-
-You never need to modify the sync engine when adding a connector.
-
-## Icon
-
-The `icon` field on `ConnectorConfig` is used throughout the UI — in the connector list, the add-connector modal, and as the document icon in the knowledge base table (replacing the generic file type icon for connector-sourced documents). The icon is read from `CONNECTOR_REGISTRY[connectorType].icon` at runtime — no separate icon map to maintain.
-
-If the service already has an icon in `apps/sim/components/icons.tsx` (from a tool integration), reuse it. Otherwise, ask the user to provide the SVG.
-
-## Registering
-
-Add one line to `apps/sim/connectors/registry.ts`:
-
-```typescript
-import { {service}Connector } from '@/connectors/{service}'
-
-export const CONNECTOR_REGISTRY: ConnectorRegistry = {
-  // ... existing connectors ...
-  {service}: {service}Connector,
-}
-```
-
-## Reference Implementations
-
-- **OAuth + contentDeferred**: `apps/sim/connectors/google-drive/google-drive.ts` — file download with metadata-based hash, `orderBy` for deterministic pagination
-- **OAuth + contentDeferred (blocks API)**: `apps/sim/connectors/notion/notion.ts` — complex block content extraction deferred to `getDocument`
-- **OAuth + contentDeferred (git)**: `apps/sim/connectors/github/github.ts` — blob SHA hash, tree listing
-- **OAuth + inline content**: `apps/sim/connectors/confluence/confluence.ts` — multiple config field types, `mapTags`, label fetching
-- **API key**: `apps/sim/connectors/fireflies/fireflies.ts` — GraphQL API with Bearer token auth
-
-## Checklist
-
-- [ ] Created `connectors/{service}/{service}.ts` with full ConnectorConfig
-- [ ] Created `connectors/{service}/index.ts` barrel export
-- [ ] **Auth configured correctly:**
-  - OAuth: `auth.provider` matches an existing `OAuthService` in `lib/oauth/types.ts`
-  - API key: `auth.label` and `auth.placeholder` set appropriately
-- [ ] **Selector fields configured correctly (if applicable):**
-  - Every `type: 'selector'` field has a canonical pair (`short-input` or `dropdown` with same `canonicalParamId` and `mode: 'advanced'`)
-  - `required` is identical on both fields in each canonical pair
-  - `selectorKey` exists in `hooks/selectors/registry.ts`
-  - `dependsOn` references selector field IDs (not `canonicalParamId`)
-  - Dependency `canonicalParamId` values exist in `SELECTOR_CONTEXT_FIELDS`
-- [ ] `listDocuments` handles pagination with metadata-based content hashes
-- [ ] `contentDeferred: true` used if content requires per-doc API calls (file download, export, blocks fetch)
-- [ ] `contentHash` is metadata-based (not content-based) and identical between stub and `getDocument`
-- [ ] `sourceUrl` set on each ExternalDocument (full URL, not relative)
-- [ ] `metadata` includes source-specific data for tag mapping
-- [ ] `tagDefinitions` declared for each semantic key returned by `mapTags`
-- [ ] `mapTags` implemented if source has useful metadata (labels, dates, versions)
-- [ ] `validateConfig` verifies the source is accessible
-- [ ] All external API calls use `fetchWithRetry` (not raw `fetch`)
-- [ ] All optional config fields validated in `validateConfig`
-- [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
-- [ ] Registered in `connectors/registry.ts`

.agents/skills/add-connector/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Connector"
-  short_description: "Build a Sim knowledge connector"
-  brand_color: "#0F766E"
-  default_prompt: "Use $add-connector to add or update a Sim knowledge connector for a service."

.agents/skills/add-integration/SKILL.md

@@ -1,778 +0,0 @@
----
-name: add-integration
-description: Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, and integration conventions. Use when introducing a new service under `apps/sim/tools`, `apps/sim/blocks`, and `apps/sim/triggers`.
----
-
-# Add Integration Skill
-
-You are an expert at adding complete integrations to Sim. This skill orchestrates the full process of adding a new service integration.
-
-## Overview
-
-Adding an integration involves these steps in order:
-1. **Research** - Read the service's API documentation
-2. **Create Tools** - Build tool configurations for each API operation
-3. **Create Block** - Build the block UI configuration
-4. **Add Icon** - Add the service's brand icon
-5. **Create Triggers** (optional) - If the service supports webhooks
-6. **Register** - Register tools, block, and triggers in their registries
-7. **Generate Docs** - Run the docs generation script
-
-## Step 1: Research the API
-
-Before writing any code:
-1. Use Context7 to find official documentation: `mcp__plugin_context7_context7__resolve-library-id`
-2. Or use WebFetch to read API docs directly
-3. Identify:
-   - Authentication method (OAuth, API Key, both)
-   - Available operations (CRUD, search, etc.)
-   - Required vs optional parameters
-   - Response structures
-
-### Hard Rule: No Guessed Response Schemas
-
-If the official docs do not clearly show the response JSON shape for an endpoint, you MUST stop and tell the user exactly which outputs are unknown.
-
-- Do NOT guess response field names
-- Do NOT infer nested JSON paths from related endpoints
-- Do NOT invent output properties just because they seem likely
-- Do NOT implement `transformResponse` against unverified payload shapes
-
-If response schemas are missing or incomplete, do one of the following before proceeding:
-1. Ask the user for sample responses
-2. Ask the user for test credentials so you can verify the live payload
-3. Reduce the scope to only endpoints whose response shapes are documented
-4. Leave the tool unimplemented and explicitly report why
-
-## Step 2: Create Tools
-
-### Directory Structure
-```
-apps/sim/tools/{service}/
-├── index.ts          # Barrel exports
-├── types.ts          # TypeScript interfaces
-├── {action1}.ts      # Tool for action 1
-├── {action2}.ts      # Tool for action 2
-└── ...
-```
-
-### Key Patterns
-
-**types.ts:**
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-export interface {Service}{Action}Params {
-  accessToken: string      // For OAuth services
-  // OR
-  apiKey: string          // For API key services
-
-  requiredParam: string
-  optionalParam?: string
-}
-
-export interface {Service}Response extends ToolResponse {
-  output: {
-    // Define output structure
-  }
-}
-```
-
-**Tool file pattern:**
-```typescript
-export const {service}{Action}Tool: ToolConfig<Params, Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: '...',
-  version: '1.0.0',
-
-  oauth: { required: true, provider: '{service}' },  // If OAuth
-
-  params: {
-    accessToken: { type: 'string', required: true, visibility: 'hidden', description: '...' },
-    // ... other params
-  },
-
-  request: { url, method, headers, body },
-
-  transformResponse: async (response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        field: data.field ?? null,  // Always handle nullables
-      },
-    }
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Critical Rules
-- `visibility: 'hidden'` for OAuth tokens
-- `visibility: 'user-only'` for API keys and user credentials
-- `visibility: 'user-or-llm'` for operation parameters
-- Always use `?? null` for nullable API response fields
-- Always use `?? []` for optional array fields
-- Set `optional: true` for outputs that may not exist
-- Never output raw JSON dumps - extract meaningful fields
-- When using `type: 'json'` and you know the object shape, define `properties` with the inner fields so downstream consumers know the structure. Only use bare `type: 'json'` when the shape is truly dynamic
-- If you do not know the response JSON shape from docs or verified examples, you MUST tell the user and stop. Never guess outputs or response mappings.
-
-## Step 3: Create Block
-
-### File Location
-`apps/sim/blocks/blocks/{service}.ts`
-
-### Block Structure
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {Service}Block: BlockConfig = {
-  type: '{service}',
-  name: '{Service}',
-  description: '...',
-  longDescription: '...',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',
-  bgColor: '#HEXCOLOR',
-  icon: {Service}Icon,
-  authMode: AuthMode.OAuth,  // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Operation dropdown
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Operation 1', id: 'action1' },
-        { label: 'Operation 2', id: 'action2' },
-      ],
-      value: () => 'action1',
-    },
-    // Credential field
-    {
-      id: 'credential',
-      title: '{Service} Account',
-      type: 'oauth-input',
-      serviceId: '{service}',
-      requiredScopes: getScopesForService('{service}'),
-      required: true,
-    },
-    // Conditional fields per operation
-    // ...
-  ],
-
-  tools: {
-    access: ['{service}_action1', '{service}_action2'],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-    },
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Key SubBlock Patterns
-
-**Condition-based visibility:**
-```typescript
-{
-  id: 'resourceId',
-  title: 'Resource ID',
-  type: 'short-input',
-  condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-  required: { field: 'operation', value: ['read', 'update', 'delete'] },
-}
-```
-
-**DependsOn for cascading selectors:**
-```typescript
-{
-  id: 'project',
-  type: 'project-selector',
-  dependsOn: ['credential'],
-},
-{
-  id: 'issue',
-  type: 'file-selector',
-  dependsOn: ['credential', 'project'],
-}
-```
-
-**Basic/Advanced mode for dual UX:**
-```typescript
-// Basic: Visual selector
-{
-  id: 'channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',
-  dependsOn: ['credential'],
-},
-// Advanced: Manual input
-{
-  id: 'channelId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',
-}
-```
-
-**Critical Canonical Param Rules:**
-- `canonicalParamId` must NOT match any subblock's `id` in the block
-- `canonicalParamId` must be unique per operation/condition context
-- Only use `canonicalParamId` to link basic/advanced alternatives for the same logical parameter
-- `mode` only controls UI visibility, NOT serialization. Without `canonicalParamId`, both basic and advanced field values would be sent
-- Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions
-- **Required consistency:** If one subblock in a canonical group has `required: true`, ALL subblocks in that group must have `required: true` (prevents bypassing validation by switching modes)
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs (e.g., `fileSelector`, `manualFileId`)
-- **Params function:** Must use canonical param IDs, NOT raw subblock IDs (raw IDs are deleted after canonical transformation)
-
-## Step 4: Add Icon
-
-### File Location
-`apps/sim/components/icons.tsx`
-
-### Pattern
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg
-      {...props}
-      viewBox="0 0 24 24"
-      fill="none"
-      xmlns="http://www.w3.org/2000/svg"
-    >
-      {/* SVG paths from user-provided SVG */}
-    </svg>
-  )
-}
-```
-
-### Getting Icons
-**Do NOT search for icons yourself.** At the end of implementation, ask the user to provide the SVG:
-
-```
-I've completed the integration. Before I can add the icon, please provide the SVG for {Service}.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-Once the user provides the SVG:
-1. Extract the SVG paths/content
-2. Create a React component that spreads props
-3. Ensure viewBox is preserved from the original SVG
-
-## Step 5: Create Triggers (Optional)
-
-If the service supports webhooks, create triggers using the generic `buildTriggerSubBlocks` helper.
-
-### Directory Structure
-```
-apps/sim/triggers/{service}/
-├── index.ts      # Barrel exports
-├── utils.ts      # Trigger options, setup instructions, extra fields
-├── {event_a}.ts  # Primary trigger (includes dropdown)
-├── {event_b}.ts  # Secondary triggers (no dropdown)
-└── webhook.ts    # Generic webhook (optional)
-```
-
-### Key Pattern
-
-```typescript
-import { buildTriggerSubBlocks } from '@/triggers'
-import { {service}TriggerOptions, {service}SetupInstructions, build{Service}ExtraFields } from './utils'
-
-// Primary trigger - includeDropdown: true
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,  // Only for primary trigger!
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  // ...
-}
-
-// Secondary triggers - no dropdown
-export const {service}EventBTrigger: TriggerConfig = {
-  id: '{service}_event_b',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_b',
-    triggerOptions: {service}TriggerOptions,
-    // No includeDropdown!
-    setupInstructions: {service}SetupInstructions('Event B'),
-    extraFields: build{Service}ExtraFields('{service}_event_b'),
-  }),
-  // ...
-}
-```
-
-### Connect to Block
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-  subBlocks: [
-    // Tool fields...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-}
-```
-
-See `/add-trigger` skill for complete documentation.
-
-## Step 6: Register Everything
-
-### Tools Registry (`apps/sim/tools/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}Action1Tool,
-  {service}Action2Tool,
-} from '@/tools/{service}'
-
-// Add to tools object (alphabetically)
-export const tools: Record<string, ToolConfig> = {
-  // ... existing tools ...
-  {service}_action1: {service}Action1Tool,
-  {service}_action2: {service}Action2Tool,
-}
-```
-
-### Block Registry (`apps/sim/blocks/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import { {Service}Block } from '@/blocks/blocks/{service}'
-
-// Add to registry (alphabetically)
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  {service}: {Service}Block,
-}
-```
-
-### Trigger Registry (`apps/sim/triggers/registry.ts`) - If triggers exist
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}EventATrigger,
-  {service}EventBTrigger,
-  {service}WebhookTrigger,
-} from '@/triggers/{service}'
-
-// Add to TRIGGER_REGISTRY (alphabetically)
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing triggers ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-  {service}_webhook: {service}WebhookTrigger,
-}
-```
-
-## Step 7: Generate Docs
-
-Run the documentation generator:
-```bash
-bun run scripts/generate-docs.ts
-```
-
-This creates `apps/docs/content/docs/en/tools/{service}.mdx`
-
-## V2 Integration Pattern
-
-If creating V2 versions (API-aligned outputs):
-
-1. **V2 Tools** - Add `_v2` suffix, version `2.0.0`, flat outputs
-2. **V2 Block** - Add `_v2` type, use `createVersionedToolSelector`
-3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`
-4. **Registry** - Register both versions
-
-```typescript
-// In registry
-{service}: {Service}Block,        // V1 (legacy, hidden)
-{service}_v2: {Service}V2Block,   // V2 (visible)
-```
-
-## Complete Checklist
-
-### Tools
-- [ ] Created `tools/{service}/` directory
-- [ ] Created `types.ts` with all interfaces
-- [ ] Created tool file for each operation
-- [ ] All params have correct visibility
-- [ ] All nullable fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all tools in `tools/registry.ts`
-
-### Block
-- [ ] Created `blocks/blocks/{service}.ts`
-- [ ] Defined operation dropdown with all operations
-- [ ] Added credential field with `requiredScopes: getScopesForService('{service}')`
-- [ ] Added conditional fields per operation
-- [ ] Set up dependsOn for cascading selectors
-- [ ] Configured tools.access with all tool IDs
-- [ ] Configured tools.config.tool selector
-- [ ] Defined outputs matching tool outputs
-- [ ] Registered block in `blocks/registry.ts`
-- [ ] If triggers: set `triggers.enabled` and `triggers.available`
-- [ ] If triggers: spread trigger subBlocks with `getTrigger()`
-
-### OAuth Scopes (if OAuth service)
-- [ ] Defined scopes in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS`
-- [ ] Added scope descriptions in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] Used `getCanonicalScopesForProvider()` in `auth.ts` (never hardcode)
-- [ ] Used `getScopesForService()` in block `requiredScopes` (never hardcode)
-
-### Icon
-- [ ] Asked user to provide SVG
-- [ ] Added icon to `components/icons.tsx`
-- [ ] Icon spreads props correctly
-
-### Triggers (if service supports webhooks)
-- [ ] Created `triggers/{service}/` directory
-- [ ] Created `utils.ts` with options, instructions, and extra fields helpers
-- [ ] Primary trigger uses `includeDropdown: true`
-- [ ] Secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all triggers in `triggers/registry.ts`
-
-### Docs
-- [ ] Ran `bun run scripts/generate-docs.ts`
-- [ ] Verified docs file created
-
-### Final Validation (Required)
-- [ ] Read every tool file and cross-referenced inputs/outputs against the API docs
-- [ ] Verified block subBlocks cover all required tool params with correct conditions
-- [ ] Verified block outputs match what the tools actually return
-- [ ] Verified `tools.config.params` correctly maps and coerces all param types
-- [ ] Verified every tool output and `transformResponse` path against documented or live-verified JSON responses
-- [ ] If any response schema remained unknown, explicitly told the user instead of guessing
-
-## Example Command
-
-When the user asks to add an integration:
-
-```
-User: Add a Stripe integration
-
-You: I'll add the Stripe integration. Let me:
-
-1. First, research the Stripe API using Context7
-2. Create the tools for key operations (payments, subscriptions, etc.)
-3. Create the block with operation dropdown
-4. Register everything
-5. Generate docs
-6. Ask you for the Stripe icon SVG
-
-[Proceed with implementation...]
-
-[After completing steps 1-5...]
-
-I've completed the Stripe integration. Before I can add the icon, please provide the SVG for Stripe.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-## File Handling
-
-When your integration handles file uploads or downloads, follow these patterns to work with `UserFile` objects consistently.
-
-### What is a UserFile?
-
-A `UserFile` is the standard file representation in Sim:
-
-```typescript
-interface UserFile {
-  id: string       // Unique identifier
-  name: string     // Original filename
-  url: string      // Presigned URL for download
-  size: number     // File size in bytes
-  type: string     // MIME type (e.g., 'application/pdf')
-  base64?: string  // Optional base64 content (if small file)
-  key?: string     // Internal storage key
-  context?: object // Storage context metadata
-}
-```
-
-### File Input Pattern (Uploads)
-
-For tools that accept file uploads, **always route through an internal API endpoint** rather than calling external APIs directly. This ensures proper file content retrieval.
-
-#### 1. Block SubBlocks for File Input
-
-Use the basic/advanced mode pattern:
-
-```typescript
-// Basic mode: File upload UI
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Maps to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from previous block
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Same canonical param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical:** `canonicalParamId` must NOT match any subblock `id`.
-
-#### 2. Normalize File Input in Block Config
-
-In `tools.config.tool`, use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  config: {
-    tool: (params) => {
-      // Normalize file from basic (uploadFile), advanced (fileRef), or legacy (fileContent)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `{service}_${params.operation}`
-    },
-  },
-}
-```
-
-#### 3. Create Internal API Route
-
-Create `apps/sim/app/api/tools/{service}/{action}/route.ts`:
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { NextResponse, type NextRequest } from 'next/server'
-import { z } from 'zod'
-import { checkInternalAuth } from '@/lib/auth/hybrid'
-import { generateRequestId } from '@/lib/core/utils/request'
-import { FileInputSchema, type RawFileInput } from '@/lib/uploads/utils/file-schemas'
-import { processFilesToUserFiles } from '@/lib/uploads/utils/file-utils'
-import { downloadFileFromStorage } from '@/lib/uploads/utils/file-utils.server'
-
-const logger = createLogger('{Service}UploadAPI')
-
-const RequestSchema = z.object({
-  accessToken: z.string(),
-  file: FileInputSchema.optional().nullable(),
-  // Legacy field for backwards compatibility
-  fileContent: z.string().optional().nullable(),
-  // ... other params
-})
-
-export async function POST(request: NextRequest) {
-  const requestId = generateRequestId()
-
-  const authResult = await checkInternalAuth(request, { requireWorkflowId: false })
-  if (!authResult.success) {
-    return NextResponse.json({ success: false, error: 'Unauthorized' }, { status: 401 })
-  }
-
-  const body = await request.json()
-  const data = RequestSchema.parse(body)
-
-  let fileBuffer: Buffer
-  let fileName: string
-
-  // Prefer UserFile input, fall back to legacy base64
-  if (data.file) {
-    const userFiles = processFilesToUserFiles([data.file as RawFileInput], requestId, logger)
-    if (userFiles.length === 0) {
-      return NextResponse.json({ success: false, error: 'Invalid file' }, { status: 400 })
-    }
-    const userFile = userFiles[0]
-    fileBuffer = await downloadFileFromStorage(userFile, requestId, logger)
-    fileName = userFile.name
-  } else if (data.fileContent) {
-    // Legacy: base64 string (backwards compatibility)
-    fileBuffer = Buffer.from(data.fileContent, 'base64')
-    fileName = 'file'
-  } else {
-    return NextResponse.json({ success: false, error: 'File required' }, { status: 400 })
-  }
-
-  // Now call external API with fileBuffer
-  const response = await fetch('https://api.{service}.com/upload', {
-    method: 'POST',
-    headers: { Authorization: `Bearer ${data.accessToken}` },
-    body: new Uint8Array(fileBuffer),  // Convert Buffer for fetch
-  })
-
-  // ... handle response
-}
-```
-
-#### 4. Update Tool to Use Internal Route
-
-```typescript
-export const {service}UploadTool: ToolConfig<Params, Response> = {
-  id: '{service}_upload',
-  // ...
-  params: {
-    file: { type: 'file', required: false, visibility: 'user-or-llm' },
-    fileContent: { type: 'string', required: false, visibility: 'hidden' }, // Legacy
-  },
-  request: {
-    url: '/api/tools/{service}/upload',  // Internal route
-    method: 'POST',
-    body: (params) => ({
-      accessToken: params.accessToken,
-      file: params.file,
-      fileContent: params.fileContent,
-    }),
-  },
-}
-```
-
-### File Output Pattern (Downloads)
-
-For tools that return files, use `FileToolProcessor` to store files and return `UserFile` objects.
-
-#### In Tool transformResponse
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-transformResponse: async (response, context) => {
-  const data = await response.json()
-
-  // Process file outputs to UserFile objects
-  const fileProcessor = new FileToolProcessor(context)
-  const file = await fileProcessor.processFileData({
-    data: data.content,      // base64 or buffer
-    mimeType: data.mimeType,
-    filename: data.filename,
-  })
-
-  return {
-    success: true,
-    output: { file },
-  }
-}
-```
-
-#### In API Route (for complex file handling)
-
-```typescript
-// Return file data that FileToolProcessor can handle
-return NextResponse.json({
-  success: true,
-  output: {
-    file: {
-      data: base64Content,
-      mimeType: 'application/pdf',
-      filename: 'document.pdf',
-    },
-  },
-})
-```
-
-### Key Helpers Reference
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get file Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-| `isUserFile` | `@/lib/core/utils/user-file` | Type guard for UserFile objects |
-| `FileInputSchema` | `@/lib/uploads/utils/file-schemas` | Zod schema for file validation |
-
-### Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. Examples: pagination tokens, time range filters, sort order, max results, reply settings.
-
-### WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually:
-- **Timestamps**: Use `generationType: 'timestamp'` to inject current date context into the AI prompt
-- **JSON arrays**: Use `generationType: 'json-object'` for structured data
-- **Complex queries**: Use a descriptive prompt explaining the expected format
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-```
-
-### OAuth Scopes (Centralized System)
-
-Scopes are maintained in a single source of truth and reused everywhere:
-
-1. **Define scopes** in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-2. **Add descriptions** in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for the OAuth modal UI
-3. **Reference in auth.ts** using `getCanonicalScopesForProvider(providerId)` from `@/lib/oauth/utils`
-4. **Reference in blocks** using `getScopesForService(serviceId)` from `@/lib/oauth/utils`
-
-**Never hardcode scope arrays** in `auth.ts` or block `requiredScopes`. Always import from the centralized source.
-
-```typescript
-// In auth.ts (Better Auth config)
-scopes: getCanonicalScopesForProvider('{service}'),
-
-// In block credential sub-block
-requiredScopes: getScopesForService('{service}'),
-```
-
-### Common Gotchas
-
-1. **OAuth serviceId must match** - The `serviceId` in oauth-input must match the OAuth provider configuration
-2. **All tool IDs MUST be snake_case** - `stripe_create_payment`, not `stripeCreatePayment`. This applies to tool `id` fields, registry keys, `tools.access` arrays, and `tools.config.tool` return values
-3. **Block type is snake_case** - `type: 'stripe'`, not `type: 'Stripe'`
-4. **Alphabetical ordering** - Keep imports and registry entries alphabetically sorted
-5. **Required can be conditional** - Use `required: { field: 'op', value: 'create' }` instead of always true
-6. **DependsOn clears options** - When a dependency changes, selector options are refetched
-7. **Never pass Buffer directly to fetch** - Convert to `new Uint8Array(buffer)` for TypeScript compatibility
-8. **Always handle legacy file params** - Keep hidden `fileContent` params for backwards compatibility
-9. **Optional fields use advanced mode** - Set `mode: 'advanced'` on rarely-used optional fields
-10. **Complex inputs need wandConfig** - Timestamps, JSON arrays, and other hard-to-type values should have `wandConfig` enabled
-11. **Never hardcode scopes** - Use `getScopesForService()` in blocks and `getCanonicalScopesForProvider()` in auth.ts
-12. **Always add scope descriptions** - New scopes must have entries in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`

.agents/skills/add-integration/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Integration"
-  short_description: "Build a full Sim integration"
-  brand_color: "#7C3AED"
-  default_prompt: "Use $add-integration to add a complete Sim integration for a service."

.agents/skills/add-tools/SKILL.md

@@ -1,466 +0,0 @@
----
-name: add-tools
-description: Create or update Sim tool configurations from service API docs, including typed params, request mapping, response transforms, outputs, and registry entries. Use when working in `apps/sim/tools/{service}/` or fixing tool definitions for an integration.
----
-
-# Add Tools Skill
-
-You are an expert at creating tool configurations for Sim integrations. Your job is to read API documentation and create properly structured tool files.
-
-## Your Task
-
-When the user asks you to create tools for a service:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Create the tools directory structure
-3. Generate properly typed tool configurations
-
-## Hard Rule: No Guessed Response Schemas
-
-If the docs do not clearly show the response JSON for a tool, you MUST tell the user exactly which outputs are unknown and stop short of guessing.
-
-- Do NOT invent response field names
-- Do NOT infer nested paths from nearby endpoints
-- Do NOT guess array item shapes
-- Do NOT write `transformResponse` against unverified payloads
-
-If the response shape is unknown, do one of these instead:
-1. Ask the user for sample responses
-2. Ask the user for test credentials so you can verify live responses
-3. Implement only the endpoints whose outputs are documented
-4. Leave the tool unimplemented and explicitly say why
-
-## Directory Structure
-
-Create files in `apps/sim/tools/{service}/`:
-```
-tools/{service}/
-├── index.ts      # Barrel export
-├── types.ts      # Parameter & response types
-└── {action}.ts   # Individual tool files (one per operation)
-```
-
-## Tool Configuration Structure
-
-Every tool MUST follow this exact structure:
-
-```typescript
-import type { {ServiceName}{Action}Params } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-interface {ServiceName}{Action}Response {
-  success: boolean
-  output: {
-    // Define output structure here
-  }
-}
-
-export const {serviceName}{Action}Tool: ToolConfig<
-  {ServiceName}{Action}Params,
-  {ServiceName}{Action}Response
-> = {
-  id: '{service}_{action}',           // snake_case, matches tool name
-  name: '{Service} {Action}',         // Human readable
-  description: 'Brief description',   // One sentence
-  version: '1.0.0',
-
-  // OAuth config (if service uses OAuth)
-  oauth: {
-    required: true,
-    provider: '{service}',            // Must match OAuth provider ID
-  },
-
-  params: {
-    // Hidden params (system-injected, only use hidden for oauth accessToken)
-    accessToken: {
-      type: 'string',
-      required: true,
-      visibility: 'hidden',
-      description: 'OAuth access token',
-    },
-    // User-only params (credentials, api key, IDs user must provide)
-    someId: {
-      type: 'string',
-      required: true,
-      visibility: 'user-only',
-      description: 'The ID of the resource',
-    },
-    // User-or-LLM params (everything else, can be provided by user OR computed by LLM)
-    query: {
-      type: 'string',
-      required: false,                // Use false for optional
-      visibility: 'user-or-llm',
-      description: 'Search query',
-    },
-  },
-
-  request: {
-    url: (params) => `https://api.service.com/v1/resource/${params.id}`,
-    method: 'POST',
-    headers: (params) => ({
-      Authorization: `Bearer ${params.accessToken}`,
-      'Content-Type': 'application/json',
-    }),
-    body: (params) => ({
-      // Request body - only for POST/PUT/PATCH
-      // Trim ID fields to prevent copy-paste whitespace errors:
-      // userId: params.userId?.trim(),
-    }),
-  },
-
-  transformResponse: async (response: Response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        // Map API response to output
-        // Use ?? null for nullable fields
-        // Use ?? [] for optional arrays
-      },
-    }
-  },
-
-  outputs: {
-    // Define each output field
-  },
-}
-```
-
-## Critical Rules for Parameters
-
-### Visibility Options
-- `'hidden'` - System-injected (OAuth tokens, internal params). User never sees.
-- `'user-only'` - User must provide (credentials, api keys, account-specific IDs)
-- `'user-or-llm'` - User provides OR LLM can compute (search queries, content, filters, most fall into this category)
-
-### Parameter Types
-- `'string'` - Text values
-- `'number'` - Numeric values
-- `'boolean'` - True/false
-- `'json'` - Complex objects (NOT 'object', use 'json')
-- `'file'` - Single file
-- `'file[]'` - Multiple files
-
-### Required vs Optional
-- Always explicitly set `required: true` or `required: false`
-- Optional params should have `required: false`
-
-## Critical Rules for Outputs
-
-### Output Types
-- `'string'`, `'number'`, `'boolean'` - Primitives
-- `'json'` - Complex objects (use this, NOT 'object')
-- `'array'` - Arrays with `items` property
-- `'object'` - Objects with `properties` property
-
-### Optional Outputs
-Add `optional: true` for fields that may not exist in the response:
-```typescript
-closedAt: {
-  type: 'string',
-  description: 'When the issue was closed',
-  optional: true,
-},
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **always define the inner structure** using `properties` so downstream consumers know what fields are available:
-
-```typescript
-// BAD: Opaque json with no info about what's inside
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-},
-
-// GOOD: Define the known properties
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-  properties: {
-    id: { type: 'string', description: 'Unique ID' },
-    status: { type: 'string', description: 'Current status' },
-    count: { type: 'number', description: 'Total count' },
-  },
-},
-```
-
-For arrays of objects, define the item structure:
-```typescript
-items: {
-  type: 'array',
-  description: 'List of items',
-  items: {
-    type: 'object',
-    properties: {
-      id: { type: 'string', description: 'Item ID' },
-      name: { type: 'string', description: 'Item name' },
-    },
-  },
-},
-```
-
-Only use bare `type: 'json'` without `properties` when the shape is truly dynamic or unknown.
-
-If the response shape is unknown because the docs do not provide it, you MUST tell the user and stop. Unknown is not the same as dynamic. Never guess outputs.
-
-## Critical Rules for transformResponse
-
-### Handle Nullable Fields
-ALWAYS use `?? null` for fields that may be undefined:
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      id: data.id,
-      title: data.title,
-      body: data.body ?? null,           // May be undefined
-      assignee: data.assignee ?? null,   // May be undefined
-      labels: data.labels ?? [],         // Default to empty array
-      closedAt: data.closed_at ?? null,  // May be undefined
-    },
-  }
-}
-```
-
-### Never Output Raw JSON Dumps
-DON'T do this:
-```typescript
-output: {
-  data: data,  // BAD - raw JSON dump
-}
-```
-
-DO this instead - extract meaningful fields:
-```typescript
-output: {
-  id: data.id,
-  name: data.name,
-  status: data.status,
-  metadata: {
-    createdAt: data.created_at,
-    updatedAt: data.updated_at,
-  },
-}
-```
-
-## Types File Pattern
-
-Create `types.ts` with interfaces for all params and responses:
-
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-// Parameter interfaces
-export interface {Service}{Action}Params {
-  accessToken: string
-  requiredField: string
-  optionalField?: string
-}
-
-// Response interfaces (extend ToolResponse)
-export interface {Service}{Action}Response extends ToolResponse {
-  output: {
-    field1: string
-    field2: number
-    optionalField?: string | null
-  }
-}
-```
-
-## Index.ts Barrel Export Pattern
-
-```typescript
-// Export all tools
-export { serviceTool1 } from './{action1}'
-export { serviceTool2 } from './{action2}'
-
-// Export types
-export * from './types'
-```
-
-## Registering Tools
-
-After creating tools:
-1. Import tools in `apps/sim/tools/registry.ts`
-2. Add to the `tools` object with snake_case keys (alphabetically):
-```typescript
-import { serviceActionTool } from '@/tools/{service}'
-
-export const tools = {
-  // ... existing tools ...
-  {service}_{action}: serviceActionTool,
-}
-```
-
-## Wiring Tools into the Block (Required)
-
-After registering in `tools/registry.ts`, you MUST also update the block definition at `apps/sim/blocks/blocks/{service}.ts`. This is not optional — tools are only usable from the UI if they are wired into the block.
-
-### 1. Add to `tools.access`
-
-```typescript
-tools: {
-  access: [
-    // existing tools...
-    'service_new_action',   // Add every new tool ID here
-  ],
-  config: { ... }
-}
-```
-
-### 2. Add operation dropdown options
-
-If the block uses an operation dropdown, add an option for each new tool:
-
-```typescript
-{
-  id: 'operation',
-  type: 'dropdown',
-  options: [
-    // existing options...
-    { label: 'New Action', id: 'new_action' },   // id maps to what tools.config.tool returns
-  ],
-}
-```
-
-### 3. Add subBlocks for new tool params
-
-For each new tool, add subBlocks covering all its required params (and optional ones where useful). Apply `condition` to show them only for the right operation, and mark required params with `required`:
-
-```typescript
-// Required param for new_action
-{
-  id: 'someParam',
-  title: 'Some Param',
-  type: 'short-input',
-  placeholder: 'e.g., value',
-  condition: { field: 'operation', value: 'new_action' },
-  required: { field: 'operation', value: 'new_action' },
-},
-// Optional param — put in advanced mode
-{
-  id: 'optionalParam',
-  title: 'Optional Param',
-  type: 'short-input',
-  condition: { field: 'operation', value: 'new_action' },
-  mode: 'advanced',
-},
-```
-
-### 4. Update `tools.config.tool`
-
-Ensure the tool selector returns the correct tool ID for every new operation. The simplest pattern:
-
-```typescript
-tool: (params) => `service_${params.operation}`,
-// If operation dropdown IDs already match tool IDs, this requires no change.
-```
-
-If the dropdown IDs differ from tool IDs, add explicit mappings:
-
-```typescript
-tool: (params) => {
-  const map: Record<string, string> = {
-    new_action: 'service_new_action',
-    // ...
-  }
-  return map[params.operation] ?? `service_${params.operation}`
-},
-```
-
-### 5. Update `tools.config.params`
-
-Add any type coercions needed for new params (runs at execution time, after variable resolution):
-
-```typescript
-params: (params) => {
-  const result: Record<string, unknown> = {}
-  if (params.limit != null && params.limit !== '') result.limit = Number(params.limit)
-  if (params.newParamName) result.toolParamName = params.newParamName  // rename if IDs differ
-  return result
-},
-```
-
-### 6. Add new outputs
-
-Add any new fields returned by the new tools to the block `outputs`:
-
-```typescript
-outputs: {
-  // existing outputs...
-  newField: { type: 'string', description: 'Description of new field' },
-}
-```
-
-### 7. Add new inputs
-
-Add new subBlock param IDs to the block `inputs` section:
-
-```typescript
-inputs: {
-  // existing inputs...
-  someParam: { type: 'string', description: 'Param description' },
-  optionalParam: { type: 'string', description: 'Optional param description' },
-}
-```
-
-### Block wiring checklist
-
-- [ ] New tool IDs added to `tools.access`
-- [ ] Operation dropdown has an option for each new tool
-- [ ] SubBlocks cover all required params for each new tool
-- [ ] SubBlocks have correct `condition` (only show for the right operation)
-- [ ] Optional/rarely-used params set to `mode: 'advanced'`
-- [ ] `tools.config.tool` returns correct ID for every new operation
-- [ ] `tools.config.params` handles any ID remapping or type coercions
-- [ ] New outputs added to block `outputs`
-- [ ] New params added to block `inputs`
-
-## V2 Tool Pattern
-
-If creating V2 tools (API-aligned outputs), use `_v2` suffix:
-- Tool ID: `{service}_{action}_v2`
-- Variable name: `{action}V2Tool`
-- Version: `'2.0.0'`
-- Outputs: Flat, API-aligned (no content/metadata wrapper)
-
-## Naming Convention
-
-All tool IDs MUST use `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase for tool IDs.
-
-## Checklist Before Finishing
-
-- [ ] All tool IDs use snake_case
-- [ ] All params have explicit `required: true` or `required: false`
-- [ ] All params have appropriate `visibility`
-- [ ] All nullable response fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] No raw JSON dumps in outputs
-- [ ] Types file has all interfaces
-- [ ] Index.ts exports all tools and re-exports types (`export * from './types'`)
-- [ ] Tools registered in `tools/registry.ts`
-- [ ] Block wired: `tools.access`, dropdown options, subBlocks, `tools.config`, outputs, inputs
-
-## Final Validation (Required)
-
-After creating all tools, you MUST validate every tool before finishing:
-
-1. **Read every tool file** you created — do not skip any
-2. **Cross-reference with the API docs** to verify:
-   - All required params are marked `required: true`
-   - All optional params are marked `required: false`
-   - Param types match the API (string, number, boolean, json)
-   - Request URL, method, headers, and body match the API spec
-   - `transformResponse` extracts the correct fields from the API response
-   - All output fields match what the API actually returns
-   - No fields are missing from outputs that the API provides
-   - No extra fields are defined in outputs that the API doesn't return
-   - Every output field and JSON path is backed by docs or live-verified sample responses
-3. **Verify consistency** across tools:
-   - Shared types in `types.ts` match all tools that use them
-   - Tool IDs in the barrel export match the tool file definitions
-   - Error handling is consistent (error checks, meaningful messages)
-4. **If any response schema is still unknown**, explicitly tell the user instead of guessing

.agents/skills/add-tools/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Tools"
-  short_description: "Build Sim tools from API docs"
-  brand_color: "#EA580C"
-  default_prompt: "Use $add-tools to create or update Sim tool definitions from service API docs."

.agents/skills/add-trigger/SKILL.md

@@ -1,373 +0,0 @@
----
-name: add-trigger
-description: Create or update Sim webhook triggers using the generic trigger builder, service-specific setup instructions, outputs, and registry wiring. Use when working in `apps/sim/triggers/{service}/` or adding webhook support to an integration.
----
-
-# Add Trigger
-
-You are an expert at creating webhook triggers for Sim. You understand the trigger system, the generic `buildTriggerSubBlocks` helper, and how triggers connect to blocks.
-
-## Your Task
-
-1. Research what webhook events the service supports
-2. Create the trigger files using the generic builder
-3. Create a provider handler if custom auth, formatting, or subscriptions are needed
-4. Register triggers and connect them to the block
-
-## Hard Rule: No Guessed Webhook Payload Schemas
-
-If the service docs do not clearly show the webhook payload JSON for an event, you MUST tell the user instead of guessing trigger outputs or `formatInput` mappings.
-
-- Do NOT invent payload field names
-- Do NOT guess nested event object paths
-- Do NOT infer output fields from the UI or marketing docs
-- Do NOT write `formatInput` against unverified webhook bodies
-
-If the payload shape is unknown, do one of these instead:
-1. Ask the user for sample webhook payloads
-2. Ask the user for a test webhook source so you can inspect a real event
-3. Implement only the event registration/setup portions whose payloads are documented
-4. Leave the trigger unimplemented and explicitly say which payload fields are unknown
-
-## Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel exports
-├── utils.ts              # Service-specific helpers (options, instructions, extra fields, outputs)
-├── {event_a}.ts          # Primary trigger (includes dropdown)
-├── {event_b}.ts          # Secondary trigger (no dropdown)
-└── webhook.ts            # Generic webhook trigger (optional, for "all events")
-
-apps/sim/lib/webhooks/
-├── provider-subscription-utils.ts  # Shared subscription helpers (getProviderConfig, getNotificationUrl)
-├── providers/
-│   ├── {service}.ts       # Provider handler (auth, formatInput, matchEvent, subscriptions)
-│   ├── types.ts           # WebhookProviderHandler interface
-│   ├── utils.ts           # Shared helpers (createHmacVerifier, verifyTokenAuth, skipByEventTypes)
-│   └── registry.ts        # Handler map + default handler
-```
-
-## Step 1: Create `utils.ts`
-
-This file contains all service-specific helpers used by triggers.
-
-```typescript
-import type { SubBlockConfig } from '@/blocks/types'
-import type { TriggerOutput } from '@/triggers/types'
-
-export const {service}TriggerOptions = [
-  { label: 'Event A', id: '{service}_event_a' },
-  { label: 'Event B', id: '{service}_event_b' },
-]
-
-export function {service}SetupInstructions(eventType: string): string {
-  const instructions = [
-    'Copy the <strong>Webhook URL</strong> above',
-    'Go to <strong>{Service} Settings > Webhooks</strong>',
-    `Select the <strong>${eventType}</strong> event type`,
-    'Paste the webhook URL and save',
-    'Click "Save" above to activate your trigger',
-  ]
-  return instructions
-    .map((instruction, index) =>
-      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
-    )
-    .join('')
-}
-
-export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
-  return [
-    {
-      id: 'projectId',
-      title: 'Project ID (Optional)',
-      type: 'short-input',
-      placeholder: 'Leave empty for all projects',
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-  ]
-}
-
-export function build{Service}Outputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'The type of event' },
-    resourceId: { type: 'string', description: 'ID of the affected resource' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Step 2: Create Trigger Files
-
-**Primary trigger** — MUST include `includeDropdown: true`:
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { buildTriggerSubBlocks } from '@/triggers'
-import { build{Service}ExtraFields, build{Service}Outputs, {service}SetupInstructions, {service}TriggerOptions } from '@/triggers/{service}/utils'
-import type { TriggerConfig } from '@/triggers/types'
-
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  name: '{Service} Event A',
-  provider: '{service}',
-  description: 'Trigger workflow when Event A occurs',
-  version: '1.0.0',
-  icon: {Service}Icon,
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  outputs: build{Service}Outputs(),
-  webhook: { method: 'POST', headers: { 'Content-Type': 'application/json' } },
-}
-```
-
-**Secondary triggers** — NO `includeDropdown` (it's already in the primary):
-
-```typescript
-export const {service}EventBTrigger: TriggerConfig = {
-  // Same as above but: id: '{service}_event_b', no includeDropdown
-}
-```
-
-## Step 3: Register and Wire
-
-### `apps/sim/triggers/{service}/index.ts`
-
-```typescript
-export { {service}EventATrigger } from './event_a'
-export { {service}EventBTrigger } from './event_b'
-```
-
-### `apps/sim/triggers/registry.ts`
-
-```typescript
-import { {service}EventATrigger, {service}EventBTrigger } from '@/triggers/{service}'
-
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-}
-```
-
-### Block file (`apps/sim/blocks/blocks/{service}.ts`)
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  // ...
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-  subBlocks: [
-    // Regular tool subBlocks first...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-}
-```
-
-## Provider Handler
-
-All provider-specific webhook logic lives in a single handler file: `apps/sim/lib/webhooks/providers/{service}.ts`.
-
-### When to Create a Handler
-
-| Behavior | Method | Examples |
-|---|---|---|
-| HMAC signature auth | `verifyAuth` via `createHmacVerifier` | Ashby, Jira, Linear, Typeform |
-| Custom token auth | `verifyAuth` via `verifyTokenAuth` | Generic, Google Forms |
-| Event filtering | `matchEvent` | GitHub, Jira, Attio, HubSpot |
-| Idempotency dedup | `extractIdempotencyId` | Slack, Stripe, Linear, Jira |
-| Custom input formatting | `formatInput` | Slack, Teams, Attio, Ashby |
-| Auto webhook creation | `createSubscription` | Ashby, Grain, Calendly, Airtable |
-| Auto webhook deletion | `deleteSubscription` | Ashby, Grain, Calendly, Airtable |
-| Challenge/verification | `handleChallenge` | Slack, WhatsApp, Teams |
-| Custom success response | `formatSuccessResponse` | Slack, Twilio Voice, Teams |
-
-If none apply, you don't need a handler. The default handler provides bearer token auth.
-
-### Example Handler
-
-```typescript
-import crypto from 'crypto'
-import { createLogger } from '@sim/logger'
-import { safeCompare } from '@/lib/core/security/encryption'
-import type { EventMatchContext, FormatInputContext, FormatInputResult, WebhookProviderHandler } from '@/lib/webhooks/providers/types'
-import { createHmacVerifier } from '@/lib/webhooks/providers/utils'
-
-const logger = createLogger('WebhookProvider:{Service}')
-
-function validate{Service}Signature(secret: string, signature: string, body: string): boolean {
-  if (!secret || !signature || !body) return false
-  const computed = crypto.createHmac('sha256', secret).update(body, 'utf8').digest('hex')
-  return safeCompare(computed, signature)
-}
-
-export const {service}Handler: WebhookProviderHandler = {
-  verifyAuth: createHmacVerifier({
-    configKey: 'webhookSecret',
-    headerName: 'X-{Service}-Signature',
-    validateFn: validate{Service}Signature,
-    providerLabel: '{Service}',
-  }),
-
-  async matchEvent({ body, requestId, providerConfig }: EventMatchContext) {
-    const triggerId = providerConfig.triggerId as string | undefined
-    if (triggerId && triggerId !== '{service}_webhook') {
-      const { is{Service}EventMatch } = await import('@/triggers/{service}/utils')
-      if (!is{Service}EventMatch(triggerId, body as Record<string, unknown>)) return false
-    }
-    return true
-  },
-
-  async formatInput({ body }: FormatInputContext): Promise<FormatInputResult> {
-    const b = body as Record<string, unknown>
-    return {
-      input: {
-        eventType: b.type,
-        resourceId: (b.data as Record<string, unknown>)?.id || '',
-        resource: b.data,
-      },
-    }
-  },
-
-  extractIdempotencyId(body: unknown) {
-    const obj = body as Record<string, unknown>
-    return obj.id && obj.type ? `${obj.type}:${obj.id}` : null
-  },
-}
-```
-
-### Register the Handler
-
-In `apps/sim/lib/webhooks/providers/registry.ts`:
-
-```typescript
-import { {service}Handler } from '@/lib/webhooks/providers/{service}'
-
-const PROVIDER_HANDLERS: Record<string, WebhookProviderHandler> = {
-  // ... existing (alphabetical) ...
-  {service}: {service}Handler,
-}
-```
-
-## Output Alignment (Critical)
-
-There are two sources of truth that **MUST be aligned**:
-
-1. **Trigger `outputs`** — schema defining what fields SHOULD be available (UI tag dropdown)
-2. **`formatInput` on the handler** — implementation that transforms raw payload into actual data
-
-If they differ: the tag dropdown shows fields that don't exist, or actual data has fields users can't discover.
-
-**Rules for `formatInput`:**
-- Return `{ input: { ... } }` where inner keys match trigger `outputs` exactly
-- Return `{ input: ..., skip: { message: '...' } }` to skip execution
-- No wrapper objects or duplication
-- Use `null` for missing optional data
-
-## Automatic Webhook Registration
-
-If the service API supports programmatic webhook creation, implement `createSubscription` and `deleteSubscription` on the handler. The orchestration layer calls these automatically — **no code touches `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`**.
-
-```typescript
-import { getNotificationUrl, getProviderConfig } from '@/lib/webhooks/provider-subscription-utils'
-import type { DeleteSubscriptionContext, SubscriptionContext, SubscriptionResult } from '@/lib/webhooks/providers/types'
-
-export const {service}Handler: WebhookProviderHandler = {
-  async createSubscription(ctx: SubscriptionContext): Promise<SubscriptionResult | undefined> {
-    const config = getProviderConfig(ctx.webhook)
-    const apiKey = config.apiKey as string
-    if (!apiKey) throw new Error('{Service} API Key is required.')
-
-    const res = await fetch('https://api.{service}.com/webhooks', {
-      method: 'POST',
-      headers: { Authorization: `Bearer ${apiKey}`, 'Content-Type': 'application/json' },
-      body: JSON.stringify({ url: getNotificationUrl(ctx.webhook) }),
-    })
-
-    if (!res.ok) throw new Error(`{Service} error: ${res.status}`)
-    const { id } = (await res.json()) as { id: string }
-    return { providerConfigUpdates: { externalId: id } }
-  },
-
-  async deleteSubscription(ctx: DeleteSubscriptionContext): Promise<void> {
-    const config = getProviderConfig(ctx.webhook)
-    const { apiKey, externalId } = config as { apiKey?: string; externalId?: string }
-    if (!apiKey || !externalId) return
-    await fetch(`https://api.{service}.com/webhooks/${externalId}`, {
-      method: 'DELETE',
-      headers: { Authorization: `Bearer ${apiKey}` },
-    }).catch(() => {})
-  },
-}
-```
-
-**Key points:**
-- Throw from `createSubscription` — orchestration rolls back the DB webhook
-- Never throw from `deleteSubscription` — log non-fatally
-- Return `{ providerConfigUpdates: { externalId } }` — orchestration merges into `providerConfig`
-- Add `apiKey` field to `build{Service}ExtraFields` with `password: true`
-
-## Trigger Outputs Schema
-
-Trigger outputs use the same schema as block outputs (NOT tool outputs).
-
-**Supported:** `type` + `description` for leaf fields, nested objects for complex data.
-**NOT supported:** `optional: true`, `items` (those are tool-output-only features).
-
-```typescript
-export function buildOutputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'Event type' },
-    timestamp: { type: 'string', description: 'When it occurred' },
-    payload: { type: 'json', description: 'Full event payload' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Checklist
-
-### Trigger Definition
-- [ ] Created `utils.ts` with options, instructions, extra fields, and output builders
-- [ ] Primary trigger has `includeDropdown: true`; secondary triggers do NOT
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-
-### Registration
-- [ ] All triggers in `triggers/registry.ts` → `TRIGGER_REGISTRY`
-- [ ] Block has `triggers.enabled: true` and lists all trigger IDs in `triggers.available`
-- [ ] Block spreads all trigger subBlocks: `...getTrigger('id').subBlocks`
-
-### Provider Handler (if needed)
-- [ ] Handler file at `apps/sim/lib/webhooks/providers/{service}.ts`
-- [ ] Registered in `providers/registry.ts` (alphabetical)
-- [ ] Signature validator is a private function inside the handler file
-- [ ] `formatInput` output keys match trigger `outputs` exactly
-- [ ] Event matching uses dynamic `await import()` for trigger utils
-
-### Auto Registration (if supported)
-- [ ] `createSubscription` and `deleteSubscription` on the handler
-- [ ] NO changes to `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] API key field uses `password: true`
-
-### Testing
-- [ ] `bun run type-check` passes
-- [ ] Manually verify `formatInput` output keys match trigger `outputs` keys
-- [ ] Trigger UI shows correctly in the block

.agents/skills/add-trigger/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Trigger"
-  short_description: "Build Sim webhook triggers"
-  brand_color: "#DC2626"
-  default_prompt: "Use $add-trigger to create or update webhook triggers for a Sim integration."

.agents/skills/cleanup/SKILL.md

@@ -1,25 +0,0 @@
----
-name: cleanup
-description: Run all code quality skills in sequence — effects, memo, callbacks, state, React Query, and emcn design review
----
-
-# Cleanup
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Steps
-
-Run each of these skills in order on the specified scope, passing through the scope and fix arguments. After each skill completes, move to the next. Do not skip any.
-
-1. `/you-might-not-need-an-effect $ARGUMENTS`
-2. `/you-might-not-need-a-memo $ARGUMENTS`
-3. `/you-might-not-need-a-callback $ARGUMENTS`
-4. `/you-might-not-need-state $ARGUMENTS`
-5. `/react-query-best-practices $ARGUMENTS`
-6. `/emcn-design-review $ARGUMENTS`
-
-After all skills have run, output a summary of what was found and fixed (or proposed) across all six passes.

.agents/skills/emcn-design-review/SKILL.md

@@ -1,335 +0,0 @@
----
-name: emcn-design-review
-description: Review UI code for alignment with the emcn design system — components, tokens, patterns, and conventions
----
-
-# EMCN Design Review
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses **emcn**, a custom component library built on Radix UI primitives with CVA (class-variance-authority) variants and CSS variable design tokens. All UI must use emcn components and tokens — never raw HTML elements or hardcoded colors.
-
-## Steps
-
-1. Read the emcn barrel export at `apps/sim/components/emcn/components/index.ts` to know what's available
-2. Read `apps/sim/app/_styles/globals.css` for the full set of CSS variable tokens
-3. Analyze the specified scope against every rule below
-4. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.
-
----
-
-## Imports
-
-- Import components from `@/components/emcn`, never from subpaths
-- Import icons from `@/components/emcn/icons` or `lucide-react`
-- Import `cn` from `@/lib/core/utils/cn` for conditional class merging
-- Import app-specific wrappers (Select, VerifiedBadge) from `@/components/ui`
-
-```tsx
-// Good
-import { Button, Modal, Badge } from '@/components/emcn'
-// Bad
-import { Button } from '@/components/emcn/components/button/button'
-```
-
----
-
-## Design Tokens (CSS Variables)
-
-Never use raw color values. Always use CSS variable tokens via Tailwind arbitrary values: `text-[var(--text-primary)]`, not `text-gray-500` or `#333`. The CSS variable pattern is canonical (1,700+ uses) — do not use Tailwind semantic classes like `text-muted-foreground`.
-
-### Text hierarchy
-| Token | Use |
-|-------|-----|
-| `text-[var(--text-primary)]` | Main content text |
-| `text-[var(--text-secondary)]` | Secondary/supporting text |
-| `text-[var(--text-tertiary)]` | Tertiary text |
-| `text-[var(--text-muted)]` | Disabled, placeholder text |
-| `text-[var(--text-icon)]` | Icon tinting |
-| `text-[var(--text-inverse)]` | Text on dark backgrounds |
-| `text-[var(--text-error)]` | Error/warning messages |
-
-### Surfaces (elevation)
-| Token | Use |
-|-------|-----|
-| `bg-[var(--bg)]` | Page background |
-| `bg-[var(--surface-2)]` through `bg-[var(--surface-7)]` | Increasing elevation |
-| `bg-[var(--surface-hover)]` | Hover state backgrounds |
-| `bg-[var(--surface-active)]` | Active/selected backgrounds |
-
-### Borders
-| Token | Use |
-|-------|-----|
-| `border-[var(--border)]` | Default borders |
-| `border-[var(--border-1)]` | Stronger borders (inputs, cards) |
-| `border-[var(--border-muted)]` | Subtle dividers |
-
-### Status
-| Token | Use |
-|-------|-----|
-| `--success` | Success states |
-| `--error` | Error states |
-| `--caution` | Warning states |
-
-### Brand
-| Token | Use |
-|-------|-----|
-| `--brand-secondary` | Brand color |
-| `--brand-accent` | Accent/CTA color |
-
-### Shadows
-Use shadow tokens, never raw box-shadow values:
-- `shadow-subtle`, `shadow-medium`, `shadow-overlay`
-- `shadow-kbd`, `shadow-card`
-
-### Z-Index
-Use z-index tokens for layering:
-- `z-[var(--z-dropdown)]` (100), `z-[var(--z-modal)]` (200), `z-[var(--z-popover)]` (300), `z-[var(--z-tooltip)]` (400), `z-[var(--z-toast)]` (500)
-
----
-
-## Component Usage Rules
-
-### Buttons
-Available variants: `default`, `primary`, `destructive`, `ghost`, `outline`, `active`, `secondary`, `tertiary`, `subtle`, `ghost-secondary`, `3d`
-
-| Action type | Variant | Frequency |
-|-------------|---------|-----------|
-| Toolbar, icon-only, utility actions | `ghost` | Most common (28%) |
-| Primary action (create, save, submit) | `primary` | Very common (24%) |
-| Cancel, close, secondary action | `default` | Common |
-| Delete, remove, destructive action | `destructive` | Targeted use only |
-| Active/selected state | `active` | Targeted use only |
-| Toggle, mode switch | `outline` | Moderate |
-
-Sizes: `sm` (compact, 32% of buttons) or `md` (default, used when no size specified). Never create custom button styles — use an existing variant.
-
-Buttons without an explicit variant prop get `default` styling. This is acceptable for cancel/secondary actions.
-
-### Modals (Dialogs)
-Use `Modal` + subcomponents. Never build custom dialog overlays.
-
-```tsx
-<Modal open={open} onOpenChange={setOpen}>
-  <ModalContent size="sm">
-    <ModalHeader>Title</ModalHeader>
-    <ModalBody>Content</ModalBody>
-    <ModalFooter>
-      <Button variant="default" onClick={() => setOpen(false)}>Cancel</Button>
-      <Button variant="primary" onClick={handleSubmit}>Save</Button>
-    </ModalFooter>
-  </ModalContent>
-</Modal>
-```
-
-Modal sizes by frequency: `sm` (440px, most common — confirmations and simple dialogs), `md` (500px, forms), `lg` (600px, content-heavy), `xl` (800px, rare), `full` (1200px, rare).
-
-Footer buttons: Cancel on left (`variant="default"`), primary action on right. This pattern is followed 100% across the codebase.
-
-### Delete/Remove Confirmations
-Always use Modal with `size="sm"`. The established pattern:
-
-```tsx
-<Modal open={open} onOpenChange={setOpen}>
-  <ModalContent size="sm">
-    <ModalHeader>Delete {itemType}</ModalHeader>
-    <ModalBody>
-      <p>Description of consequences</p>
-      <p className="text-[var(--text-error)]">Warning about irreversibility</p>
-    </ModalBody>
-    <ModalFooter>
-      <Button variant="default" onClick={() => setOpen(false)}>Cancel</Button>
-      <Button variant="destructive" onClick={handleDelete} disabled={isDeleting}>
-        Delete
-      </Button>
-    </ModalFooter>
-  </ModalContent>
-</Modal>
-```
-
-Rules:
-- Title: "Delete {ItemType}" or "Remove {ItemType}" (use "Remove" for membership/association changes)
-- Include consequence description
-- Use `text-[var(--text-error)]` for warning text when the action is irreversible
-- `variant="destructive"` for the action button (100% compliance)
-- `variant="default"` for cancel (100% compliance)
-- Cancel left, destructive right (100% compliance)
-- For high-risk deletes (workspaces), require typing the name to confirm
-- Include recovery info if soft-delete: "You can restore it from Recently Deleted in Settings"
-
-### Toast Notifications
-Use the imperative `toast` API from `@/components/emcn`. Never build custom notification UI.
-
-```tsx
-import { toast } from '@/components/emcn'
-
-toast.success('Item saved')
-toast.error('Something went wrong')
-toast.success('Deleted', { action: { label: 'Undo', onClick: handleUndo } })
-```
-
-Variants: `default`, `success`, `error`. Auto-dismiss after 5s. Supports optional action buttons with callbacks.
-
-### Badges
-Use semantic color variants for status:
-
-| Status | Variant | Usage |
-|--------|---------|-------|
-| Error, failed, disconnected | `red` | Most common (15 uses) |
-| Metadata, roles, auth types, scopes | `gray-secondary` | Very common (12 uses) |
-| Type annotations (TS types, field types) | `type` | Very common (12 uses) |
-| Success, active, enabled, running | `green` | Common (7 uses) |
-| Neutral, default, unknown | `gray` | Common (6 uses) |
-| Outline, parameters, public | `outline` | Moderate (6 uses) |
-| Warning, processing | `amber` | Moderate (5 uses) |
-| Paused, warning | `orange` | Occasional |
-| Info, queued | `blue` | Occasional |
-| Data types (arrays) | `purple` | Occasional |
-| Generic with border | `default` | Occasional |
-
-Use `dot` prop for status indicators (19 instances in codebase). `icon` prop is available but rarely used.
-
-### Tooltips
-Use `Tooltip` from emcn with namespace pattern:
-
-```tsx
-<Tooltip.Root>
-  <Tooltip.Trigger asChild>
-    <Button variant="ghost">{icon}</Button>
-  </Tooltip.Trigger>
-  <Tooltip.Content>Helpful text</Tooltip.Content>
-</Tooltip.Root>
-```
-
-Use tooltips for icon-only buttons and truncated text. Don't tooltip self-explanatory elements.
-
-### Popovers
-Use for filters, option menus, and nested navigation:
-
-```tsx
-<Popover open={open} onOpenChange={setOpen} size="sm">
-  <PopoverTrigger asChild>
-    <Button variant="ghost">Trigger</Button>
-  </PopoverTrigger>
-  <PopoverContent side="bottom" align="end" minWidth={160}>
-    <PopoverSection>Section Title</PopoverSection>
-    <PopoverItem active={isActive} onClick={handleClick}>
-      Item Label
-    </PopoverItem>
-    <PopoverDivider />
-  </PopoverContent>
-</Popover>
-```
-
-### Dropdown Menus
-Use for context menus and action menus:
-
-```tsx
-<DropdownMenu>
-  <DropdownMenuTrigger asChild>
-    <Button variant="ghost">
-      <MoreHorizontal className="h-[14px] w-[14px]" />
-    </Button>
-  </DropdownMenuTrigger>
-  <DropdownMenuContent align="end">
-    <DropdownMenuItem onClick={handleEdit}>Edit</DropdownMenuItem>
-    <DropdownMenuSeparator />
-    <DropdownMenuItem onClick={handleDelete} className="text-[var(--text-error)]">
-      Delete
-    </DropdownMenuItem>
-  </DropdownMenuContent>
-</DropdownMenu>
-```
-
-Destructive items go last, after a separator, in error color.
-
-### Forms
-Use `FormField` wrapper for labeled inputs:
-
-```tsx
-<FormField label="Name" htmlFor="name" error={errors.name} optional>
-  <Input id="name" value={name} onChange={e => setName(e.target.value)} />
-</FormField>
-```
-
-Rules:
-- Use `Input` from emcn, never raw `<input>` (exception: hidden file inputs)
-- Use `Textarea` from emcn, never raw `<textarea>`
-- Use `FormField` for label + input + error layout
-- Mark optional fields with `optional` prop
-- Show errors inline below the input
-- Use `Combobox` for searchable selects
-- Use `TagInput` for multi-value inputs
-
-### Loading States
-Use `Skeleton` for content placeholders:
-
-```tsx
-<Skeleton className="h-5 w-[200px] rounded-md" />
-```
-
-Rules:
-- Mirror the actual UI structure with skeletons
-- Match exact dimensions of the final content
-- Use `rounded-md` to match component radius
-- Stack multiple skeletons for lists
-
-### Icons
-Standard sizing — `h-[14px] w-[14px]` is the dominant pattern (400+ uses):
-
-```tsx
-<Icon className="h-[14px] w-[14px] text-[var(--text-icon)]" />
-```
-
-Size scale by frequency:
-1. `h-[14px] w-[14px]` — default for inline icons (most common)
-2. `h-[16px] w-[16px]` — slightly larger inline icons
-3. `h-3 w-3` (12px) — compact/tight spaces
-4. `h-4 w-4` (16px) — Tailwind equivalent, also common
-5. `h-3.5 w-3.5` (14px) — Tailwind equivalent of 14px
-6. `h-5 w-5` (20px) — larger icons, section headers
-
-Use `text-[var(--text-icon)]` for icon color (113+ uses in codebase).
-
----
-
-## Styling Rules
-
-1. **Use `cn()` for conditional classes**: `cn('base', condition && 'conditional')` — never template literal concatenation like `` `base ${condition ? 'active' : ''}` ``
-2. **Inline styles**: Avoid. Exception: dynamic values that can't be expressed as Tailwind classes (e.g., `style={{ width: dynamicVar }}` or CSS variable references). Never use inline styles for colors or static values.
-3. **Never hardcode colors**: Use CSS variable tokens. Never `text-gray-500`, `bg-red-100`, `#fff`, or `rgb()`. Always `text-[var(--text-*)]`, `bg-[var(--surface-*)]`, etc.
-4. **Never use Tailwind semantic color classes**: Use `text-[var(--text-muted)]` not `text-muted-foreground`. The CSS variable pattern is canonical.
-5. **Never use global styles**: Keep all styling local to components
-6. **Hover states**: Use `hover-hover:` pseudo-class for hover-capable devices
-7. **Transitions**: Use `transition-colors` for color changes, `transition-colors duration-100` for fast hover
-8. **Border radius**: `rounded-lg` (large cards), `rounded-md` (medium), `rounded-sm` (small), `rounded-xs` (tiny)
-9. **Typography**: Use semantic sizes — `text-small` (13px), `text-caption` (12px), `text-xs` (11px), `text-micro` (10px)
-10. **Font weight**: Use `font-medium` for emphasis, avoid `font-bold` unless for headings
-11. **Spacing**: Use Tailwind gap/padding utilities. Common patterns: `gap-2`, `gap-3`, `px-4 py-2.5`
-
----
-
-## Anti-patterns to flag
-
-- Raw HTML `<button>` instead of Button component (exception: inside Radix primitives)
-- Raw HTML `<input>` instead of Input component (exception: hidden file inputs, read-only checkboxes in markdown)
-- Hardcoded Tailwind default colors (`text-gray-*`, `bg-red-*`, `text-blue-*`)
-- Hex values in className (`bg-[#fff]`, `text-[#333]`)
-- Tailwind semantic classes (`text-muted-foreground`) instead of CSS variables (`text-[var(--text-muted)]`)
-- Custom modal/dialog implementations instead of `Modal`
-- Custom toast/notification implementations instead of `toast`
-- Inline styles for colors or static values (dynamic values are acceptable)
-- Template literal className concatenation instead of `cn()`
-- Wrong button variant for the action type
-- Missing loading/skeleton states
-- Missing error states on forms
-- Importing from emcn subpaths instead of barrel export
-- Using arbitrary z-index (`z-50`, `z-[9999]`) instead of z-index tokens
-- Custom shadows instead of shadow tokens
-- Icon sizes that don't follow the established scale (default to `h-[14px] w-[14px]`)

.agents/skills/react-query-best-practices/SKILL.md

@@ -1,54 +0,0 @@
----
-name: react-query-best-practices
-description: Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership
----
-
-# React Query Best Practices
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/hooks/queries/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query (TanStack Query) as the single source of truth for all server state. All query hooks live in `hooks/queries/`. Zustand is used only for client-only UI state. Server data must never be duplicated into useState or Zustand outside of mutation callbacks that coordinate cross-store state.
-
-## References
-
-Read these before analyzing:
-1. https://tkdodo.eu/blog/practical-react-query — foundational defaults, custom hooks, avoiding local state copies
-2. https://tkdodo.eu/blog/effective-react-query-keys — key factory pattern, hierarchical keys, fuzzy invalidation
-3. https://tkdodo.eu/blog/react-query-as-a-state-manager — React Query IS your server state manager
-
-## Rules to enforce
-
-### Query key factories
-- Every file in `hooks/queries/` must have a hierarchical key factory with an `all` root key
-- Keys must include intermediate plural keys (`lists`, `details`) for prefix invalidation
-- Key factories are colocated with their query hooks, not in a global keys file
-
-### Query hooks
-- Every `queryFn` must forward `signal` for request cancellation
-- Every query must have an explicit `staleTime` (default 0 is almost never correct)
-- `keepPreviousData` / `placeholderData` only on variable-key queries (where params change), never on static keys
-- Use `enabled` to prevent queries from running without required params
-
-### Mutations
-- Use `onSettled` (not `onSuccess`) for cache reconciliation — it fires on both success and error
-- For optimistic updates: save previous data in `onMutate`, roll back in `onError`
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- Don't include mutation objects in `useCallback` deps — `.mutate()` is stable
-
-### Server state ownership
-- Never copy query data into useState. Use query data directly in components.
-- Never copy query data into Zustand stores (exception: mutation callbacks that coordinate cross-store state like temp ID replacement)
-- The query cache is not a local state manager — `setQueryData` is for optimistic updates only
-- Forms are the one deliberate exception: copy server data into local form state with `staleTime: Infinity`
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope against the rules listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.agents/skills/validate-connector/SKILL.md

@@ -1,349 +0,0 @@
----
-name: validate-connector
-description: Audit an existing Sim knowledge base connector against the service API docs and repository conventions, then report and fix issues in auth, config fields, pagination, document mapping, tags, and registry entries. Use when validating or repairing code in `apps/sim/connectors/{service}/`.
----
-
-# Validate Connector Skill
-
-You are an expert auditor for Sim knowledge base connectors. Your job is to thoroughly validate that an existing connector is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate a connector:
-1. Read the service's API documentation (via Context7 or WebFetch)
-2. Read the connector implementation, OAuth config, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the connector — do not skip any:
-
-```
-apps/sim/connectors/{service}/{service}.ts   # Connector implementation
-apps/sim/connectors/{service}/index.ts       # Barrel export
-apps/sim/connectors/registry.ts              # Connector registry entry
-apps/sim/connectors/types.ts                 # ConnectorConfig interface, ExternalDocument, etc.
-apps/sim/connectors/utils.ts                 # Shared utilities (computeContentHash, htmlToPlainText, etc.)
-apps/sim/lib/oauth/oauth.ts                  # OAUTH_PROVIDERS — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts                  # getCanonicalScopesForProvider, getScopesForService, SCOPE_DESCRIPTIONS
-apps/sim/lib/oauth/types.ts                  # OAuthService union type
-apps/sim/components/icons.tsx                 # Icon definition for the service
-```
-
-If the connector uses selectors, also read:
-```
-apps/sim/hooks/selectors/registry.ts         # Selector key definitions
-apps/sim/hooks/selectors/types.ts            # SelectorKey union type
-apps/sim/lib/workflows/subblocks/context.ts  # SELECTOR_CONTEXT_FIELDS
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (cursor, offset, next token)
-- Rate limits and error formats
-- OAuth scopes and their meanings
-
-Use Context7 (resolve-library-id → query-docs) or WebFetch to retrieve documentation. If both fail, note which claims are based on training knowledge vs verified docs.
-
-### Hard Rule: No Guessed Source Schemas
-
-If the service docs do not clearly show document list responses, document fetch responses, metadata fields, or pagination shapes, you MUST tell the user instead of guessing.
-
-- Do NOT infer document fields from unrelated endpoints
-- Do NOT guess pagination cursors or response wrappers
-- Do NOT assume metadata keys that are not documented
-- Do NOT treat probable shapes as validated
-
-If a schema is unknown, validation must explicitly recommend:
-1. sample API responses,
-2. live test credentials, or
-3. trimming the connector to only documented fields.
-
-## Step 3: Validate API Endpoints
-
-For **every** API call in the connector (`listDocuments`, `getDocument`, `validateConfig`, and any helper functions), verify against the API docs:
-
-### URLs and Methods
-- [ ] Base URL is correct for the service's API version
-- [ ] Endpoint paths match the API docs exactly
-- [ ] HTTP method is correct (GET, POST, PUT, PATCH, DELETE)
-- [ ] Path parameters are correctly interpolated and URI-encoded where needed
-- [ ] Query parameters use correct names and formats per the API docs
-
-### Headers
-- [ ] Authorization header uses the correct format:
-  - OAuth: `Authorization: Bearer ${accessToken}`
-  - API Key: correct header name per the service's docs
-- [ ] `Content-Type` is set for POST/PUT/PATCH requests
-- [ ] Any service-specific headers are present (e.g., `Notion-Version`, `Dropbox-API-Arg`)
-- [ ] No headers are sent that the API doesn't support or silently ignores
-
-### Request Bodies
-- [ ] POST/PUT body fields match API parameter names exactly
-- [ ] Required fields are always sent
-- [ ] Optional fields are conditionally included (not sent as `null` or empty unless the API expects that)
-- [ ] Field value types match API expectations (string vs number vs boolean)
-
-### Input Sanitization
-- [ ] User-controlled values interpolated into query strings are properly escaped:
-  - OData `$filter`: single quotes escaped with `''` (e.g., `externalId.replace(/'/g, "''")`)
-  - SOQL: single quotes escaped with `\'`
-  - GraphQL variables: passed as variables, not interpolated into query strings
-  - URL path segments: `encodeURIComponent()` applied
-- [ ] URL-type config fields (e.g., `siteUrl`, `instanceUrl`) are normalized:
-  - Strip `https://` / `http://` prefix if the API expects bare domains
-  - Strip trailing `/`
-  - Apply `.trim()` before validation
-
-### Response Parsing
-- [ ] Response structure is correctly traversed (e.g., `data.results` vs `data.items` vs `data`)
-- [ ] Field names extracted match what the API actually returns
-- [ ] Nullable fields are handled with `?? null` or `|| undefined`
-- [ ] Error responses are checked before accessing data fields
-- [ ] Every extracted field and pagination value is backed by official docs or live-verified sample payloads
-
-## Step 4: Validate OAuth Scopes (if OAuth connector)
-
-Scopes must be correctly declared and sufficient for all API calls the connector makes.
-
-### Connector requiredScopes
-- [ ] `requiredScopes` in the connector's `auth` config lists all scopes needed by the connector
-- [ ] Each scope in `requiredScopes` is a real, valid scope recognized by the service's API
-- [ ] No invalid, deprecated, or made-up scopes are listed
-- [ ] No unnecessary excess scopes beyond what the connector actually needs
-
-### Scope Subset Validation (CRITICAL)
-- [ ] Every scope in `requiredScopes` exists in the OAuth provider's `scopes` array in `lib/oauth/oauth.ts`
-- [ ] Find the provider in `OAUTH_PROVIDERS[providerGroup].services[serviceId].scopes`
-- [ ] Verify: `requiredScopes` ⊆ `OAUTH_PROVIDERS scopes` (every required scope is present in the provider config)
-- [ ] If a required scope is NOT in the provider config, flag as **critical** — the connector will fail at runtime
-
-### Scope Sufficiency
-For each API endpoint the connector calls:
-- [ ] Identify which scopes are required per the API docs
-- [ ] Verify those scopes are included in the connector's `requiredScopes`
-- [ ] If the connector calls endpoints requiring scopes not in `requiredScopes`, flag as **warning**
-
-### Token Refresh Config
-- [ ] Check the `getOAuthTokenRefreshConfig` function in `lib/oauth/oauth.ts` for this provider
-- [ ] `useBasicAuth` matches the service's token exchange requirements
-- [ ] `supportsRefreshTokenRotation` matches whether the service issues rotating refresh tokens
-- [ ] Token endpoint URL is correct
-
-## Step 5: Validate Pagination
-
-### listDocuments Pagination
-- [ ] Cursor/pagination parameter name matches the API docs
-- [ ] Response pagination field is correctly extracted (e.g., `next_cursor`, `nextPageToken`, `@odata.nextLink`, `offset`)
-- [ ] `hasMore` is correctly determined from the response
-- [ ] `nextCursor` is correctly passed back for the next page
-- [ ] `maxItems` / `maxRecords` cap is correctly applied across pages using `syncContext.totalDocsFetched`
-- [ ] Page size is within the API's allowed range (not exceeding max page size)
-- [ ] Last page precision: when a `maxItems` cap exists, the final page request uses `Math.min(PAGE_SIZE, remaining)` to avoid fetching more records than needed
-- [ ] No off-by-one errors in pagination tracking
-- [ ] The connector does NOT hit known API pagination limits silently (e.g., HubSpot search 10k cap)
-
-### Pagination State Across Pages
-- [ ] `syncContext` is used to cache state across pages (user names, field maps, instance URLs, portal IDs, etc.)
-- [ ] Cached state in `syncContext` is correctly initialized on first page and reused on subsequent pages
-
-## Step 6: Validate Data Transformation
-
-### Content Deferral (CRITICAL)
-Connectors that require per-document API calls to fetch content (file download, export, blocks fetch) MUST use `contentDeferred: true`. This is the standard pattern for reliability — without it, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-- [ ] If the connector downloads content per-doc during `listDocuments`, it MUST use `contentDeferred: true` instead
-- [ ] `listDocuments` returns lightweight stubs with `content: ''` and `contentDeferred: true`
-- [ ] `getDocument` fetches actual content and returns the full document with `contentDeferred: false`
-- [ ] A shared stub function (e.g., `fileToStub`) is used by both `listDocuments` and `getDocument` to guarantee `contentHash` consistency
-- [ ] `contentHash` is metadata-based (e.g., `service:{id}:{modifiedTime}`), NOT content-based — it must be derivable from list metadata alone
-- [ ] The `contentHash` is identical whether produced by `listDocuments` or `getDocument`
-
-Connectors where the list API already returns content inline (e.g., Slack messages, Reddit posts) do NOT need `contentDeferred`.
-
-### ExternalDocument Construction
-- [ ] `externalId` is a stable, unique identifier from the source API
-- [ ] `title` is extracted from the correct field and has a sensible fallback (e.g., `'Untitled'`)
-- [ ] `content` is plain text — HTML content is stripped using `htmlToPlainText` from `@/connectors/utils`
-- [ ] `mimeType` is `'text/plain'`
-- [ ] `contentHash` uses a metadata-based format (e.g., `service:{id}:{modifiedTime}`) for connectors with `contentDeferred: true`, or `computeContentHash` from `@/connectors/utils` for inline-content connectors
-- [ ] `sourceUrl` is a valid, complete URL back to the original resource (not relative)
-- [ ] `metadata` contains all fields referenced by `mapTags` and `tagDefinitions`
-
-### Content Extraction
-- [ ] Rich text / HTML fields are converted to plain text before indexing
-- [ ] Important content is not silently dropped (e.g., nested blocks, table cells, code blocks)
-- [ ] Content is not silently truncated without logging a warning
-- [ ] Empty/blank documents are properly filtered out
-- [ ] Size checks use `Buffer.byteLength(text, 'utf8')` not `text.length` when comparing against byte-based limits (e.g., `MAX_FILE_SIZE` in bytes)
-
-## Step 7: Validate Tag Definitions and mapTags
-
-### tagDefinitions
-- [ ] Each `tagDefinition` has an `id`, `displayName`, and `fieldType`
-- [ ] `fieldType` matches the actual data type: `'text'` for strings, `'number'` for numbers, `'date'` for dates, `'boolean'` for booleans
-- [ ] Every `id` in `tagDefinitions` is returned by `mapTags`
-- [ ] No `tagDefinition` references a field that `mapTags` never produces
-
-### mapTags
-- [ ] Return keys match `tagDefinition` `id` values exactly
-- [ ] Date values are properly parsed using `parseTagDate` from `@/connectors/utils`
-- [ ] Array values are properly joined using `joinTagArray` from `@/connectors/utils`
-- [ ] Number values are validated (not `NaN`)
-- [ ] Metadata field names accessed in `mapTags` match what `listDocuments`/`getDocument` store in `metadata`
-
-## Step 8: Validate Config Fields and Validation
-
-### configFields
-- [ ] Every field has `id`, `title`, `type`
-- [ ] `required` is set explicitly (not omitted)
-- [ ] Dropdown fields have `options` with `label` and `id` for each option
-- [ ] Selector fields follow the canonical pair pattern:
-  - A `type: 'selector'` field with `selectorKey`, `canonicalParamId`, `mode: 'basic'`
-  - A `type: 'short-input'` field with the same `canonicalParamId`, `mode: 'advanced'`
-  - `required` is identical on both fields in the pair
-- [ ] `selectorKey` values exist in the selector registry
-- [ ] `dependsOn` references selector field `id` values, not `canonicalParamId`
-
-### validateConfig
-- [ ] Validates all required fields are present before making API calls
-- [ ] Validates optional numeric fields (checks `Number.isNaN`, positive values)
-- [ ] Makes a lightweight API call to verify access (e.g., fetch 1 record, get profile)
-- [ ] Uses `VALIDATE_RETRY_OPTIONS` for retry budget
-- [ ] Returns `{ valid: true }` on success
-- [ ] Returns `{ valid: false, error: 'descriptive message' }` on failure
-- [ ] Catches exceptions and returns user-friendly error messages
-- [ ] Does NOT make expensive calls (full data listing, large queries)
-
-## Step 9: Validate getDocument
-
-- [ ] Fetches a single document by `externalId`
-- [ ] Returns `null` for 404 / not found (does not throw)
-- [ ] Returns the same `ExternalDocument` shape as `listDocuments`
-- [ ] If `listDocuments` uses `contentDeferred: true`, `getDocument` MUST fetch actual content and return `contentDeferred: false`
-- [ ] If `listDocuments` uses `contentDeferred: true`, `getDocument` MUST use the same stub function to ensure `contentHash` is identical
-- [ ] Handles all content types that `listDocuments` can produce (e.g., if `listDocuments` returns both pages and blogposts, `getDocument` must handle both — not hardcode one endpoint)
-- [ ] Forwards `syncContext` if it needs cached state (user names, field maps, etc.)
-- [ ] Error handling is graceful (catches, logs, returns null or throws with context)
-- [ ] Does not redundantly re-fetch data already included in the initial API response (e.g., if comments come back with the post, don't fetch them again separately)
-
-## Step 10: Validate General Quality
-
-### fetchWithRetry Usage
-- [ ] All external API calls use `fetchWithRetry` from `@/lib/knowledge/documents/utils`
-- [ ] No raw `fetch()` calls to external APIs
-- [ ] `VALIDATE_RETRY_OPTIONS` used in `validateConfig`
-- [ ] If `validateConfig` calls a shared helper (e.g., `linearGraphQL`, `resolveId`), that helper must accept and forward `retryOptions` to `fetchWithRetry`
-- [ ] Default retry options used in `listDocuments`/`getDocument`
-
-### API Efficiency
-- [ ] APIs that support field selection (e.g., `$select`, `sysparm_fields`, `fields`) should request only the fields the connector needs — in both `listDocuments` AND `getDocument`
-- [ ] No redundant API calls: if a helper already fetches data (e.g., site metadata), callers should reuse the result instead of making a second call for the same information
-- [ ] Sequential per-item API calls (fetching details for each document in a loop) should be batched with `Promise.all` and a concurrency limit of 3-5
-
-### Error Handling
-- [ ] Individual document failures are caught and logged without aborting the sync
-- [ ] API error responses include status codes in error messages
-- [ ] No unhandled promise rejections in concurrent operations
-
-### Concurrency
-- [ ] Concurrent API calls use reasonable batch sizes (3-5 is typical)
-- [ ] No unbounded `Promise.all` over large arrays
-
-### Logging
-- [ ] Uses `createLogger` from `@sim/logger` (not `console.log`)
-- [ ] Logs sync progress at `info` level
-- [ ] Logs errors at `warn` or `error` level with context
-
-### Registry
-- [ ] Connector is exported from `connectors/{service}/index.ts`
-- [ ] Connector is registered in `connectors/registry.ts`
-- [ ] Registry key matches the connector's `id` field
-
-## Step 11: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors, data loss, or auth failures):
-- Wrong API endpoint URL or HTTP method
-- Invalid or missing OAuth scopes (not in provider config)
-- Incorrect response field mapping (accessing wrong path)
-- SOQL/query fields that don't exist on the target object
-- Pagination that silently hits undocumented API limits
-- Missing error handling that would crash the sync
-- `requiredScopes` not a subset of OAuth provider scopes
-- Query/filter injection: user-controlled values interpolated into OData `$filter`, SOQL, or query strings without escaping
-- Per-document content download in `listDocuments` without `contentDeferred: true` — causes sync timeouts for large document sets
-- `contentHash` mismatch between `listDocuments` stub and `getDocument` return — causes unnecessary re-processing every sync
-
-**Warning** (incorrect behavior, data quality issues, or convention violations):
-- HTML content not stripped via `htmlToPlainText`
-- `getDocument` not forwarding `syncContext`
-- `getDocument` hardcoded to one content type when `listDocuments` returns multiple (e.g., only pages but not blogposts)
-- Missing `tagDefinition` for metadata fields returned by `mapTags`
-- Incorrect `useBasicAuth` or `supportsRefreshTokenRotation` in token refresh config
-- Invalid scope names that the API doesn't recognize (even if silently ignored)
-- Private resources excluded from name-based lookup despite scopes being available
-- Silent data truncation without logging
-- Size checks using `text.length` (character count) instead of `Buffer.byteLength` (byte count) for byte-based limits
-- URL-type config fields not normalized (protocol prefix, trailing slashes cause API failures)
-- `VALIDATE_RETRY_OPTIONS` not threaded through helper functions called by `validateConfig`
-
-**Suggestion** (minor improvements):
-- Missing incremental sync support despite API supporting it
-- Overly broad scopes that could be narrowed (not wrong, but could be tighter)
-- Source URL format could be more specific
-- Missing `orderBy` for deterministic pagination
-- Redundant API calls that could be cached in `syncContext`
-- Sequential per-item API calls that could be batched with `Promise.all` (concurrency 3-5)
-- API supports field selection but connector fetches all fields (e.g., missing `$select`, `sysparm_fields`, `fields`)
-- `getDocument` re-fetches data already included in the initial API response (e.g., comments returned with post)
-- Last page of pagination requests full `PAGE_SIZE` when fewer records remain (`Math.min(PAGE_SIZE, remaining)`)
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes
-2. TypeScript compiles clean
-3. Re-read all modified files to verify fixes are correct
-4. Any remaining unknown source schemas were explicitly reported to the user instead of guessed
-
-## Checklist Summary
-
-- [ ] Read connector implementation, types, utils, registry, and OAuth config
-- [ ] Pulled and read official API documentation for the service
-- [ ] Validated every API endpoint URL, method, headers, and body against API docs
-- [ ] Validated input sanitization: no query/filter injection, URL fields normalized
-- [ ] Validated OAuth scopes: `requiredScopes` ⊆ OAuth provider `scopes` in `oauth.ts`
-- [ ] Validated each scope is real and recognized by the service's API
-- [ ] Validated scopes are sufficient for all API endpoints the connector calls
-- [ ] Validated token refresh config (`useBasicAuth`, `supportsRefreshTokenRotation`)
-- [ ] Validated pagination: cursor names, page sizes, hasMore logic, no silent caps
-- [ ] Validated content deferral: `contentDeferred: true` used when per-doc content fetch required, metadata-based `contentHash` consistent between stub and `getDocument`
-- [ ] Validated data transformation: plain text extraction, HTML stripping, content hashing
-- [ ] Validated tag definitions match mapTags output, correct fieldTypes
-- [ ] Validated config fields: canonical pairs, selector keys, required flags
-- [ ] Validated validateConfig: lightweight check, error messages, retry options
-- [ ] Validated getDocument: null on 404, all content types handled, no redundant re-fetches, syncContext forwarding
-- [ ] Validated fetchWithRetry used for all external calls (no raw fetch), VALIDATE_RETRY_OPTIONS threaded through helpers
-- [ ] Validated API efficiency: field selection used, no redundant calls, sequential fetches batched
-- [ ] Validated error handling: graceful failures, no unhandled rejections
-- [ ] Validated logging: createLogger, no console.log
-- [ ] Validated registry: correct export, correct key
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.agents/skills/validate-connector/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Validate Connector"
-  short_description: "Audit a Sim knowledge connector"
-  brand_color: "#059669"
-  default_prompt: "Use $validate-connector to audit and fix a Sim knowledge connector against its API docs."

.agents/skills/validate-integration/SKILL.md

@@ -1,305 +0,0 @@
----
-name: validate-integration
-description: Audit an existing Sim integration against the service API docs and repository conventions, then report and fix issues across tools, blocks, outputs, OAuth scopes, triggers, and registry entries. Use when validating or repairing a service integration under `apps/sim/tools`, `apps/sim/blocks`, or `apps/sim/triggers`.
----
-
-# Validate Integration Skill
-
-You are an expert auditor for Sim integrations. Your job is to thoroughly validate that an existing integration is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate an integration:
-1. Read the service's API documentation (via WebFetch or Context7)
-2. Read every tool, the block, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the integration — do not skip any:
-
-```
-apps/sim/tools/{service}/          # All tool files, types.ts, index.ts
-apps/sim/blocks/blocks/{service}.ts # Block definition
-apps/sim/tools/registry.ts          # Tool registry entries for this service
-apps/sim/blocks/registry.ts         # Block registry entry for this service
-apps/sim/components/icons.tsx        # Icon definition
-apps/sim/lib/auth/auth.ts           # OAuth config — should use getCanonicalScopesForProvider()
-apps/sim/lib/oauth/oauth.ts         # OAuth provider config — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts               # Scope utilities, SCOPE_DESCRIPTIONS for modal UI
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (which param name, which response field)
-- Rate limits and error formats
-
-### Hard Rule: No Guessed Response Schemas
-
-If the official docs do not clearly show the response JSON shape for an endpoint, you MUST tell the user instead of guessing.
-
-- Do NOT assume field names from nearby endpoints
-- Do NOT infer nested JSON paths without evidence
-- Do NOT treat "likely" fields as confirmed outputs
-- Do NOT accept implementation guesses as valid just because they are defensive
-
-If a response schema is unknown, the validation must explicitly call that out and require:
-1. sample responses from the user,
-2. live test credentials for verification, or
-3. trimming the tool/block down to only documented fields.
-
-## Step 3: Validate Tools
-
-For **every** tool file, check:
-
-### Tool ID and Naming
-- [ ] Tool ID uses `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`)
-- [ ] Tool `name` is human-readable (e.g., `'X Create Tweet'`)
-- [ ] Tool `description` is a concise one-liner describing what it does
-- [ ] Tool `version` is set (`'1.0.0'` or `'2.0.0'` for V2)
-
-### Params
-- [ ] All required API params are marked `required: true`
-- [ ] All optional API params are marked `required: false`
-- [ ] Every param has explicit `required: true` or `required: false` — never omitted
-- [ ] Param types match the API (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] Visibility is correct:
-  - `'hidden'` — ONLY for OAuth access tokens and system-injected params
-  - `'user-only'` — for API keys, credentials, and account-specific IDs the user must provide
-  - `'user-or-llm'` — for everything else (search queries, content, filters, IDs that could come from other blocks)
-- [ ] Every param has a `description` that explains what it does
-
-### Request
-- [ ] URL matches the API endpoint exactly (correct base URL, path segments, path params)
-- [ ] HTTP method matches the API spec (GET, POST, PUT, PATCH, DELETE)
-- [ ] Headers include correct auth pattern:
-  - OAuth: `Authorization: Bearer ${params.accessToken}`
-  - API Key: correct header name and format per the service's docs
-- [ ] `Content-Type` header is set for POST/PUT/PATCH requests
-- [ ] Body sends all required fields and only includes optional fields when provided
-- [ ] For GET requests with query params: URL is constructed correctly with query string
-- [ ] ID fields in URL paths are `.trim()`-ed to prevent copy-paste whitespace errors
-- [ ] Path params use template literals correctly: `` `https://api.service.com/v1/${params.id.trim()}` ``
-
-### Response / transformResponse
-- [ ] Correctly parses the API response (`await response.json()`)
-- [ ] Extracts the right fields from the response structure (e.g., `data.data` vs `data` vs `data.results`)
-- [ ] All nullable fields use `?? null`
-- [ ] All optional arrays use `?? []`
-- [ ] Error cases are handled: checks for missing/empty data and returns meaningful error
-- [ ] Does NOT do raw JSON dumps — extracts meaningful, individual fields
-- [ ] Every extracted field is backed by official docs or live-verified sample payloads
-
-### Outputs
-- [ ] All output fields match what the API actually returns
-- [ ] No fields are missing that the API provides and users would commonly need
-- [ ] No phantom fields defined that the API doesn't return
-- [ ] `optional: true` is set on fields that may not exist in all responses
-- [ ] When using `type: 'json'` and the shape is known, `properties` defines the inner fields
-- [ ] When using `type: 'array'`, `items` defines the item structure with `properties`
-- [ ] Field descriptions are accurate and helpful
-
-### Types (types.ts)
-- [ ] Has param interfaces for every tool (e.g., `XCreateTweetParams`)
-- [ ] Has response interfaces for every tool (extending `ToolResponse`)
-- [ ] Optional params use `?` in the interface (e.g., `replyTo?: string`)
-- [ ] Field names in types match actual API field names
-- [ ] Shared response types are properly reused (e.g., `XTweetResponse` shared across tweet tools)
-
-### Barrel Export (index.ts)
-- [ ] Every tool is exported
-- [ ] All types are re-exported (`export * from './types'`)
-- [ ] No orphaned exports (tools that don't exist)
-
-### Tool Registry (tools/registry.ts)
-- [ ] Every tool is imported and registered
-- [ ] Registry keys use snake_case and match tool IDs exactly
-- [ ] Entries are in alphabetical order within the file
-
-## Step 4: Validate Block
-
-### Block ↔ Tool Alignment (CRITICAL)
-
-This is the most important validation — the block must be perfectly aligned with every tool it references.
-
-For **each tool** in `tools.access`:
-- [ ] The operation dropdown has an option whose ID matches the tool ID (or the `tools.config.tool` function correctly maps to it)
-- [ ] Every **required** tool param (except `accessToken`) has a corresponding subBlock input that is:
-  - Shown when that operation is selected (correct `condition`)
-  - Marked as `required: true` (or conditionally required)
-- [ ] Every **optional** tool param has a corresponding subBlock input (or is intentionally omitted if truly never needed)
-- [ ] SubBlock `id` values are unique across the entire block — no duplicates even across different conditions
-- [ ] The `tools.config.tool` function returns the correct tool ID for every possible operation value
-- [ ] The `tools.config.params` function correctly maps subBlock IDs to tool param names when they differ
-
-### SubBlocks
-- [ ] Operation dropdown lists ALL tool operations available in `tools.access`
-- [ ] Dropdown option labels are human-readable and descriptive
-- [ ] Conditions use correct syntax:
-  - Single value: `{ field: 'operation', value: 'x_create_tweet' }`
-  - Multiple values (OR): `{ field: 'operation', value: ['x_create_tweet', 'x_delete_tweet'] }`
-  - Negation: `{ field: 'operation', value: 'delete', not: true }`
-  - Compound: `{ field: 'op', value: 'send', and: { field: 'type', value: 'dm' } }`
-- [ ] Condition arrays include ALL operations that use that field — none missing
-- [ ] `dependsOn` is set for fields that need other values (selectors depending on credential, cascading dropdowns)
-- [ ] SubBlock types match tool param types:
-  - Enum/fixed options → `dropdown`
-  - Free text → `short-input`
-  - Long text/content → `long-input`
-  - True/false → `dropdown` with Yes/No options (not `switch` unless purely UI toggle)
-  - Credentials → `oauth-input` with correct `serviceId`
-- [ ] Dropdown `value: () => 'default'` is set for dropdowns with a sensible default
-
-### Advanced Mode
-- [ ] Optional, rarely-used fields are set to `mode: 'advanced'`:
-  - Pagination tokens / next tokens
-  - Time range filters (start/end time)
-  - Sort order / direction options
-  - Max results / per page limits
-  - Reply settings / threading options
-  - Rarely used IDs (reply-to, quote-tweet, etc.)
-  - Exclude filters
-- [ ] **Required** fields are NEVER set to `mode: 'advanced'`
-- [ ] Fields that users fill in most of the time are NOT set to `mode: 'advanced'`
-
-### WandConfig
-- [ ] Timestamp fields have `wandConfig` with `generationType: 'timestamp'`
-- [ ] Comma-separated list fields have `wandConfig` with a descriptive prompt
-- [ ] Complex filter/query fields have `wandConfig` with format examples in the prompt
-- [ ] All `wandConfig` prompts end with "Return ONLY the [format] - no explanations, no extra text."
-- [ ] `wandConfig.placeholder` describes what to type in natural language
-
-### Tools Config
-- [ ] `tools.access` lists **every** tool ID the block can use — none missing
-- [ ] `tools.config.tool` returns the correct tool ID for each operation
-- [ ] Type coercions are in `tools.config.params` (runs at execution time), NOT in `tools.config.tool` (runs at serialization time before variable resolution)
-- [ ] `tools.config.params` handles:
-  - `Number()` conversion for numeric params that come as strings from inputs
-  - `Boolean` / string-to-boolean conversion for toggle params
-  - Empty string → `undefined` conversion for optional dropdown values
-  - Any subBlock ID → tool param name remapping
-- [ ] No `Number()`, `JSON.parse()`, or other coercions in `tools.config.tool` — these would destroy dynamic references like `<Block.output>`
-
-### Block Outputs
-- [ ] Outputs cover the key fields returned by ALL tools (not just one operation)
-- [ ] Output types are correct (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] `type: 'json'` outputs either:
-  - Describe inner fields in the description string (GOOD): `'User profile (id, name, username, bio)'`
-  - Use nested output definitions (BEST): `{ id: { type: 'string' }, name: { type: 'string' } }`
-- [ ] No opaque `type: 'json'` with vague descriptions like `'Response data'`
-- [ ] Outputs that only appear for certain operations use `condition` if supported, or document which operations return them
-
-### Block Metadata
-- [ ] `type` is snake_case (e.g., `'x'`, `'cloudflare'`)
-- [ ] `name` is human-readable (e.g., `'X'`, `'Cloudflare'`)
-- [ ] `description` is a concise one-liner
-- [ ] `longDescription` provides detail for docs
-- [ ] `docsLink` points to `'https://docs.sim.ai/tools/{service}'`
-- [ ] `category` is `'tools'`
-- [ ] `bgColor` uses the service's brand color hex
-- [ ] `icon` references the correct icon component from `@/components/icons`
-- [ ] `authMode` is set correctly (`AuthMode.OAuth` or `AuthMode.ApiKey`)
-- [ ] Block is registered in `blocks/registry.ts` alphabetically
-
-### Block Inputs
-- [ ] `inputs` section lists all subBlock params that the block accepts
-- [ ] Input types match the subBlock types
-- [ ] When using `canonicalParamId`, inputs list the canonical ID (not the raw subBlock IDs)
-
-## Step 5: Validate OAuth Scopes (if OAuth service)
-
-Scopes are centralized — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-- [ ] Scopes defined in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-- [ ] `auth.ts` uses `getCanonicalScopesForProvider(providerId)` — NOT a hardcoded array
-- [ ] Block `requiredScopes` uses `getScopesForService(serviceId)` — NOT a hardcoded array
-- [ ] No hardcoded scope arrays in `auth.ts` or block files (should all use utility functions)
-- [ ] Each scope has a human-readable description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] No excess scopes that aren't needed by any tool
-
-## Step 6: Validate Pagination Consistency
-
-If any tools support pagination:
-- [ ] Pagination param names match the API docs (e.g., `pagination_token` vs `next_token` vs `cursor`)
-- [ ] Different API endpoints that use different pagination param names have separate subBlocks in the block
-- [ ] Pagination response fields (`nextToken`, `cursor`, etc.) are included in tool outputs
-- [ ] Pagination subBlocks are set to `mode: 'advanced'`
-
-## Step 7: Validate Error Handling
-
-- [ ] `transformResponse` checks for error conditions before accessing data
-- [ ] Error responses include meaningful messages (not just generic "failed")
-- [ ] HTTP error status codes are handled (check `response.ok` or status codes)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors or incorrect behavior):
-- Wrong endpoint URL or HTTP method
-- Missing required params or wrong `required` flag
-- Incorrect response field mapping (accessing wrong path in response)
-- Missing error handling that would cause crashes
-- Tool ID mismatch between tool file, registry, and block `tools.access`
-- OAuth scopes missing in `auth.ts` that tools need
-- `tools.config.tool` returning wrong tool ID for an operation
-- Type coercions in `tools.config.tool` instead of `tools.config.params`
-
-**Warning** (follows conventions incorrectly or has usability issues):
-- Optional field not set to `mode: 'advanced'`
-- Missing `wandConfig` on timestamp/complex fields
-- Wrong `visibility` on params (e.g., `'hidden'` instead of `'user-or-llm'`)
-- Missing `optional: true` on nullable outputs
-- Opaque `type: 'json'` without property descriptions
-- Missing `.trim()` on ID fields in request URLs
-- Missing `?? null` on nullable response fields
-- Block condition array missing an operation that uses that field
-- Hardcoded scope arrays instead of using `getScopesForService()` / `getCanonicalScopesForProvider()`
-- Missing scope description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-
-**Suggestion** (minor improvements):
-- Better description text
-- Inconsistent naming across tools
-- Missing `longDescription` or `docsLink`
-- Pagination fields that could benefit from `wandConfig`
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes with no fixes needed
-2. TypeScript compiles clean (no type errors)
-3. Re-read all modified files to verify fixes are correct
-4. Any remaining unknown response schemas were explicitly reported to the user instead of guessed
-
-## Checklist Summary
-
-- [ ] Read ALL tool files, block, types, index, and registries
-- [ ] Pulled and read official API documentation
-- [ ] Validated every tool's ID, params, request, response, outputs, and types against API docs
-- [ ] Validated block ↔ tool alignment (every tool param has a subBlock, every condition is correct)
-- [ ] Validated advanced mode on optional/rarely-used fields
-- [ ] Validated wandConfig on timestamps and complex inputs
-- [ ] Validated tools.config mapping, tool selector, and type coercions
-- [ ] Validated block outputs match what tools return, with typed JSON where possible
-- [ ] Validated OAuth scopes use centralized utilities (getScopesForService, getCanonicalScopesForProvider) — no hardcoded arrays
-- [ ] Validated scope descriptions exist in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for all scopes
-- [ ] Validated pagination consistency across tools and block
-- [ ] Validated error handling (error checks, meaningful messages)
-- [ ] Validated registry entries (tools and block, alphabetical, correct imports)
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.agents/skills/validate-integration/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Validate Integration"
-  short_description: "Audit a Sim service integration"
-  brand_color: "#B45309"
-  default_prompt: "Use $validate-integration to audit and fix a Sim integration against its API docs."

.agents/skills/validate-trigger/SKILL.md

@@ -1,228 +0,0 @@
----
-name: validate-trigger
-description: Audit an existing Sim webhook trigger against the service's webhook API docs and repository conventions, then report and fix issues across trigger definitions, provider handler, output alignment, registration, and security. Use when validating or repairing a trigger under `apps/sim/triggers/{service}/` or `apps/sim/lib/webhooks/providers/{service}.ts`.
----
-
-# Validate Trigger
-
-You are an expert auditor for Sim webhook triggers. Your job is to validate that an existing trigger implementation is correct, complete, secure, and aligned across all layers.
-
-## Your Task
-
-1. Read the service's webhook/API documentation (via WebFetch)
-2. Read every trigger file, provider handler, and registry entry
-3. Cross-reference against the API docs and Sim conventions
-4. Report all issues grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the trigger — do not skip any:
-
-```
-apps/sim/triggers/{service}/           # All trigger files, utils.ts, index.ts
-apps/sim/lib/webhooks/providers/{service}.ts  # Provider handler (if exists)
-apps/sim/lib/webhooks/providers/registry.ts   # Handler registry
-apps/sim/triggers/registry.ts                 # Trigger registry
-apps/sim/blocks/blocks/{service}.ts           # Block definition (trigger wiring)
-```
-
-Also read for reference:
-```
-apps/sim/lib/webhooks/providers/types.ts            # WebhookProviderHandler interface
-apps/sim/lib/webhooks/providers/utils.ts            # Shared helpers (createHmacVerifier, etc.)
-apps/sim/lib/webhooks/provider-subscription-utils.ts    # Subscription helpers
-apps/sim/lib/webhooks/processor.ts                  # Central webhook processor
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the service's official webhook documentation. This is the **source of truth** for:
-- Webhook event types and payload shapes
-- Signature/auth verification method (HMAC algorithm, header names, secret format)
-- Challenge/verification handshake requirements
-- Webhook subscription API (create/delete endpoints, if applicable)
-- Retry behavior and delivery guarantees
-
-### Hard Rule: No Guessed Webhook Payload Schemas
-
-If the official docs do not clearly show the webhook payload JSON for an event, you MUST tell the user instead of guessing.
-
-- Do NOT invent payload field names
-- Do NOT infer nested payload paths without evidence
-- Do NOT treat likely event shapes as verified
-- Do NOT accept `formatInput` mappings that are not backed by docs or live payloads
-
-If a payload schema is unknown, validation must explicitly recommend:
-1. sample webhook payloads,
-2. a live test webhook source, or
-3. trimming the trigger to only documented outputs.
-
-## Step 3: Validate Trigger Definitions
-
-### utils.ts
-- [ ] `{service}TriggerOptions` lists all trigger IDs accurately
-- [ ] `{service}SetupInstructions` provides clear, correct steps for the service
-- [ ] `build{Service}ExtraFields` includes relevant filter/config fields with correct `condition`
-- [ ] Output builders expose all meaningful fields from the webhook payload
-- [ ] Output builders do NOT use `optional: true` or `items` (tool-output-only features)
-- [ ] Nested output objects correctly model the payload structure
-
-### Trigger Files
-- [ ] Exactly one primary trigger has `includeDropdown: true`
-- [ ] All secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper (not hand-rolled subBlocks)
-- [ ] Every trigger's `id` matches the convention `{service}_{event_name}`
-- [ ] Every trigger's `provider` matches the service name used in the handler registry
-- [ ] `index.ts` barrel exports all triggers
-
-### Trigger ↔ Provider Alignment (CRITICAL)
-- [ ] Every trigger ID referenced in `matchEvent` logic exists in `{service}TriggerOptions`
-- [ ] Event matching logic in the provider correctly maps trigger IDs to service event types
-- [ ] Event matching logic in `is{Service}EventMatch` (if exists) correctly identifies events per the API docs
-
-## Step 4: Validate Provider Handler
-
-### Auth Verification
-- [ ] `verifyAuth` correctly validates webhook signatures per the service's documentation
-- [ ] HMAC algorithm matches (SHA-1, SHA-256, SHA-512)
-- [ ] Signature header name matches the API docs exactly
-- [ ] Signature format is handled (raw hex, `sha256=` prefix, base64, etc.)
-- [ ] Uses `safeCompare` for timing-safe comparison (no `===`)
-- [ ] If `webhookSecret` is required, handler rejects when it's missing (fail-closed)
-- [ ] Signature is computed over raw body (not parsed JSON)
-
-### Event Matching
-- [ ] `matchEvent` returns `boolean` (not `NextResponse` or other values)
-- [ ] Challenge/verification events are excluded from matching (e.g., `endpoint.url_validation`)
-- [ ] When `triggerId` is a generic webhook ID, all events pass through
-- [ ] When `triggerId` is specific, only matching events pass
-- [ ] Event matching logic uses dynamic `await import()` for trigger utils (avoids circular deps)
-
-### formatInput (CRITICAL)
-- [ ] Every key in the `formatInput` return matches a key in the trigger `outputs` schema
-- [ ] Every key in the trigger `outputs` schema is populated by `formatInput`
-- [ ] No extra undeclared keys that users can't discover in the UI
-- [ ] No wrapper objects (`webhook: { ... }`, `{service}: { ... }`)
-- [ ] Nested output paths exist at the correct depth (e.g., `resource.id` actually has `resource: { id: ... }`)
-- [ ] `null` is used for missing optional fields (not empty strings or empty objects)
-- [ ] Returns `{ input: { ... } }` — not a bare object
-- [ ] Every mapped payload field is backed by official docs or live-verified webhook payloads
-
-### Idempotency
-- [ ] `extractIdempotencyId` returns a stable, unique key per delivery
-- [ ] Uses provider-specific delivery IDs when available (e.g., `X-Request-Id`, `Linear-Delivery`, `svix-id`)
-- [ ] Falls back to content-based ID (e.g., `${type}:${id}`) when no delivery header exists
-- [ ] Does NOT include timestamps in the idempotency key (would break dedup on retries)
-
-### Challenge Handling (if applicable)
-- [ ] `handleChallenge` correctly implements the service's URL verification handshake
-- [ ] Returns the expected response format per the API docs
-- [ ] Env-backed secrets are resolved via `resolveEnvVarsInObject` if needed
-
-## Step 5: Validate Automatic Subscription Lifecycle
-
-If the service supports programmatic webhook creation:
-
-### createSubscription
-- [ ] Calls the correct API endpoint to create a webhook
-- [ ] Sends the correct event types/filters
-- [ ] Passes the notification URL from `getNotificationUrl(ctx.webhook)`
-- [ ] Returns `{ providerConfigUpdates: { externalId } }` with the external webhook ID
-- [ ] Throws on failure (orchestration handles rollback)
-- [ ] Provides user-friendly error messages (401 → "Invalid API Key", etc.)
-
-### deleteSubscription
-- [ ] Calls the correct API endpoint to delete the webhook
-- [ ] Handles 404 gracefully (webhook already deleted)
-- [ ] Never throws — catches errors and logs non-fatally
-- [ ] Skips gracefully when `apiKey` or `externalId` is missing
-
-### Orchestration Isolation
-- [ ] NO provider-specific logic in `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] All subscription logic lives on the handler (`createSubscription`/`deleteSubscription`)
-
-## Step 6: Validate Registration and Block Wiring
-
-### Trigger Registry (`triggers/registry.ts`)
-- [ ] All triggers are imported and registered
-- [ ] Registry keys match trigger IDs exactly
-- [ ] No orphaned entries (triggers that don't exist)
-
-### Provider Handler Registry (`providers/registry.ts`)
-- [ ] Handler is imported and registered (if handler exists)
-- [ ] Registry key matches the `provider` field on the trigger configs
-- [ ] Entries are in alphabetical order
-
-### Block Wiring (`blocks/blocks/{service}.ts`)
-- [ ] Block has `triggers.enabled: true`
-- [ ] `triggers.available` lists all trigger IDs
-- [ ] All trigger subBlocks are spread into `subBlocks`: `...getTrigger('id').subBlocks`
-- [ ] No trigger IDs in `triggers.available` that aren't in the registry
-- [ ] No trigger subBlocks spread that aren't in `triggers.available`
-
-## Step 7: Validate Security
-
-- [ ] Webhook secrets are never logged (not even at debug level)
-- [ ] Auth verification runs before any event processing
-- [ ] No secret comparison uses `===` (must use `safeCompare` or `crypto.timingSafeEqual`)
-- [ ] Timestamp/replay protection is reasonable (not too tight for retries, not too loose for security)
-- [ ] Raw body is used for signature verification (not re-serialized JSON)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (runtime errors, security issues, or data loss):
-- Wrong HMAC algorithm or header name
-- `formatInput` keys don't match trigger `outputs`
-- Missing `verifyAuth` when the service sends signed webhooks
-- `matchEvent` returns non-boolean values
-- Provider-specific logic leaking into shared orchestration files
-- Trigger IDs mismatch between trigger files, registry, and block
-- `createSubscription` calling wrong API endpoint
-- Auth comparison using `===` instead of `safeCompare`
-
-**Warning** (convention violations or usability issues):
-- Missing `extractIdempotencyId` when the service provides delivery IDs
-- Timestamps in idempotency keys (breaks dedup on retries)
-- Missing challenge handling when the service requires URL verification
-- Output schema missing fields that `formatInput` returns (undiscoverable data)
-- Overly tight timestamp skew window that rejects legitimate retries
-- `matchEvent` not filtering challenge/verification events
-- Setup instructions missing important steps
-
-**Suggestion** (minor improvements):
-- More specific output field descriptions
-- Additional output fields that could be exposed
-- Better error messages in `createSubscription`
-- Logging improvements
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run type-check` passes
-2. Re-read all modified files to verify fixes are correct
-3. Provider handler tests pass (if they exist): `bun test {service}`
-4. Any remaining unknown webhook payload schemas were explicitly reported to the user instead of guessed
-
-## Checklist Summary
-
-- [ ] Read all trigger files, provider handler, types, registries, and block
-- [ ] Pulled and read official webhook/API documentation
-- [ ] Validated trigger definitions: options, instructions, extra fields, outputs
-- [ ] Validated primary/secondary trigger distinction (`includeDropdown`)
-- [ ] Validated provider handler: auth, matchEvent, formatInput, idempotency
-- [ ] Validated output alignment: every `outputs` key ↔ every `formatInput` key
-- [ ] Validated subscription lifecycle: createSubscription, deleteSubscription, no shared-file edits
-- [ ] Validated registration: trigger registry, handler registry, block wiring
-- [ ] Validated security: safe comparison, no secret logging, replay protection
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] `bun run type-check` passes after fixes

.agents/skills/you-might-not-need-a-callback/SKILL.md

@@ -1,51 +0,0 @@
----
-name: you-might-not-need-a-callback
-description: Analyze and fix useCallback anti-patterns in your code
----
-
-# You Might Not Need a Callback
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://react.dev/reference/react/useCallback — official docs on when useCallback is actually needed
-
-## When useCallback IS needed
-
-- Passing a callback to a child wrapped in `React.memo` (to preserve referential equality)
-- The callback is a dependency of another hook (`useEffect`, `useMemo`)
-- The callback is used in a custom hook that documents referential stability requirements
-
-## Anti-patterns to detect
-
-1. **useCallback on functions not passed as props or deps**: If the function is only called within the same component and isn't in any dependency array, useCallback adds overhead for no benefit. Just declare the function normally.
-2. **useCallback with exhaustive deps that change every render**: If the dependency array includes values that change on every render, useCallback recalculates every time. The memoization is wasted. Either stabilize the deps (use refs) or remove the useCallback.
-3. **useCallback on event handlers passed to native elements**: `<button onClick={handleClick}>` — native elements don't benefit from stable references. Only child components wrapped in React.memo do.
-4. **useCallback wrapping a function that creates new objects/arrays**: If the callback returns `{ ...newObj }` or `[...newArr]`, memoizing the callback doesn't prevent the child from re-rendering due to new return values. The memoization is at the wrong level.
-5. **useCallback with an empty dep array when deps are needed**: Stale closures — the callback captures outdated values. Either add proper deps or use refs for values that shouldn't trigger re-creation.
-6. **Pairing useCallback with React.memo unnecessarily**: If the child component is cheap to render, neither useCallback nor React.memo adds value. Only optimize when you've measured a performance problem.
-7. **useCallback in custom hooks that don't need stable references**: Not every hook return needs to be memoized. Only stabilize callbacks when consumers depend on referential equality.
-
-## Codebase-specific notes
-
-This codebase uses a ref pattern for stable callbacks in hooks:
-```tsx
-const idRef = useRef(id)
-useEffect(() => { idRef.current = id }, [id])
-const fetchData = useCallback(async () => {
-  // use idRef.current instead of id
-}, []) // empty deps because refs are used
-```
-This pattern is correct — don't flag it as an anti-pattern.
-
-## Steps
-
-1. Read the reference above
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.agents/skills/you-might-not-need-a-memo/SKILL.md

@@ -1,33 +0,0 @@
----
-name: you-might-not-need-a-memo
-description: Analyze and fix useMemo/React.memo anti-patterns in your code
----
-
-# You Might Not Need a Memo
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://overreacted.io/before-you-memo/ — two techniques to avoid memo entirely
-
-## Anti-patterns to detect
-
-1. **Wrapping a slow component in React.memo when state can be moved down**: If a component re-renders because of state it doesn't use, move that state into a smaller child component instead of memoizing. The slow component stops re-rendering without memo.
-2. **Wrapping in React.memo when children can be lifted up**: If a parent owns state that changes frequently, extract the stateful part and pass the expensive subtree as `children`. Children passed as props don't re-render when the parent's state changes.
-3. **useMemo on cheap computations**: Filtering or mapping a small array, string concatenation, simple arithmetic — these don't need memoization. Only memoize when you've measured a performance problem.
-4. **useMemo with constantly-changing deps**: If the dependency array changes on every render, useMemo does nothing — it recalculates every time. Fix the deps or remove the memo.
-5. **useMemo to create objects/arrays passed as props**: Instead of memoizing to prevent child re-renders, consider whether the child even needs referential stability. If the child doesn't use React.memo or pass it to a dep array, the memo is wasted.
-6. **React.memo on components that always receive new props**: If the parent always passes new objects, arrays, or callbacks, React.memo's shallow comparison always fails. Fix the parent instead of memoizing the child.
-7. **useMemo for derived state**: If you're computing a value from props or state, just compute it inline during render. React renders are fast. `const fullName = first + ' ' + last` doesn't need useMemo.
-
-## Steps
-
-1. Read the reference above to understand the two core techniques (move state down, lift content up)
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.agents/skills/you-might-not-need-an-effect/SKILL.md

@@ -1,17 +0,0 @@
----
-name: you-might-not-need-an-effect
-description: Analyze and fix useEffect anti-patterns in your code
----
-
-# You Might Not Need an Effect
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-Steps:
-1. Read https://react.dev/learn/you-might-not-need-an-effect to understand the guidelines
-2. Analyze the specified scope for useEffect anti-patterns
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.agents/skills/you-might-not-need-state/SKILL.md

@@ -1,38 +0,0 @@
----
-name: you-might-not-need-state
-description: Analyze and fix unnecessary useState, derived state, and server-state-in-local-state anti-patterns
----
-
-# You Might Not Need State
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query for all server state and Zustand for client-only global state. useState should only be used for ephemeral UI concerns (open/closed, hover, local form input). Server data should never be copied into useState or Zustand — React Query is the single source of truth.
-
-## References
-
-Read these before analyzing:
-1. https://react.dev/learn/choosing-the-state-structure — 5 principles for structuring state
-2. https://tkdodo.eu/blog/dont-over-use-state — never store derived/computed values in state
-3. https://tkdodo.eu/blog/putting-props-to-use-state — never mirror props into state via useEffect
-
-## Anti-patterns to detect
-
-1. **Derived state stored in useState**: If a value can be computed from props, other state, or query data, compute it inline during render instead of storing it in state.
-2. **Server state copied into useState**: Never `useState` + `useEffect` to sync React Query data into local state. Use query data directly. The only exception is forms where users edit server data.
-3. **Props mirrored into state**: Never `useState(prop)` + `useEffect(() => setState(prop))`. Use the prop directly, or use a key to reset component state.
-4. **Chained useEffect state updates**: Never chain Effects that set state to trigger other Effects. Calculate all derived values in the event handler or inline during render.
-5. **Storing objects when an ID suffices**: Store `selectedId` not a copy of the selected object. Derive the object: `items.find(i => i.id === selectedId)`.
-6. **State that duplicates Zustand or React Query**: If the data already lives in a store or query cache, don't create a parallel useState.
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/commands/add-block.md

@@ -1,831 +0,0 @@
----
-description: Create a block configuration for a Sim integration with proper subBlocks, conditions, and tool wiring
-argument-hint: <service-name>
----
-
-# Add Block Skill
-
-You are an expert at creating block configurations for Sim. You understand the serializer, subBlock types, conditions, dependsOn, modes, and all UI patterns.
-
-## Your Task
-
-When the user asks you to create a block:
-1. Create the block file in `apps/sim/blocks/blocks/{service}.ts`
-2. Configure all subBlocks with proper types, conditions, and dependencies
-3. Wire up tools correctly
-
-## Block Configuration Structure
-
-```typescript
-import { {ServiceName}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {ServiceName}Block: BlockConfig = {
-  type: '{service}',                    // snake_case identifier
-  name: '{Service Name}',               // Human readable
-  description: 'Brief description',     // One sentence
-  longDescription: 'Detailed description for docs',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',                    // 'tools' | 'blocks' | 'triggers'
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
-  bgColor: '#HEXCOLOR',                 // Brand color
-  icon: {ServiceName}Icon,
-
-  // Auth mode
-  authMode: AuthMode.OAuth,             // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Define all UI fields here
-  ],
-
-  tools: {
-    access: ['tool_id_1', 'tool_id_2'], // Array of tool IDs this block can use
-    config: {
-      tool: (params) => `{service}_${params.operation}`,  // Tool selector function
-      params: (params) => ({
-        // Transform subBlock values to tool params
-      }),
-    },
-  },
-
-  inputs: {
-    // Optional: define expected inputs from other blocks
-  },
-
-  outputs: {
-    // Define outputs available to downstream blocks
-  },
-}
-```
-
-## SubBlock Types Reference
-
-**Critical:** Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions.
-
-### Text Inputs
-```typescript
-// Single-line input
-{ id: 'field', title: 'Label', type: 'short-input', placeholder: '...' }
-
-// Multi-line input
-{ id: 'field', title: 'Label', type: 'long-input', placeholder: '...', rows: 6 }
-
-// Password input
-{ id: 'apiKey', title: 'API Key', type: 'short-input', password: true }
-```
-
-### Selection Inputs
-```typescript
-// Dropdown (static options)
-{
-  id: 'operation',
-  title: 'Operation',
-  type: 'dropdown',
-  options: [
-    { label: 'Create', id: 'create' },
-    { label: 'Update', id: 'update' },
-  ],
-  value: () => 'create',  // Default value function
-}
-
-// Combobox (searchable dropdown)
-{
-  id: 'field',
-  title: 'Label',
-  type: 'combobox',
-  options: [...],
-  searchable: true,
-}
-```
-
-### Code/JSON Inputs
-```typescript
-{
-  id: 'code',
-  title: 'Code',
-  type: 'code',
-  language: 'javascript',  // 'javascript' | 'json' | 'python'
-  placeholder: '// Enter code...',
-}
-```
-
-### OAuth/Credentials
-```typescript
-{
-  id: 'credential',
-  title: 'Account',
-  type: 'oauth-input',
-  serviceId: '{service}',  // Must match OAuth provider service key
-  requiredScopes: getScopesForService('{service}'),  // Import from @/lib/oauth/utils
-  placeholder: 'Select account',
-  required: true,
-}
-```
-
-**Scopes:** Always use `getScopesForService(serviceId)` from `@/lib/oauth/utils` for `requiredScopes`. Never hardcode scope arrays — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-**Scope descriptions:** When adding a new OAuth provider, also add human-readable descriptions for all scopes in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`.
-
-### Selectors (with dynamic options)
-```typescript
-// Channel selector (Slack, Discord, etc.)
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  serviceId: '{service}',
-  placeholder: 'Select channel',
-  dependsOn: ['credential'],
-}
-
-// Project selector (Jira, etc.)
-{
-  id: 'project',
-  title: 'Project',
-  type: 'project-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-
-// File selector (Google Drive, etc.)
-{
-  id: 'file',
-  title: 'File',
-  type: 'file-selector',
-  serviceId: '{service}',
-  mimeType: 'application/pdf',
-  dependsOn: ['credential'],
-}
-
-// User selector
-{
-  id: 'user',
-  title: 'User',
-  type: 'user-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-```
-
-### Other Types
-```typescript
-// Switch/toggle
-{ id: 'enabled', type: 'switch' }
-
-// Slider
-{ id: 'temperature', title: 'Temperature', type: 'slider', min: 0, max: 2, step: 0.1 }
-
-// Table (key-value pairs)
-{ id: 'headers', title: 'Headers', type: 'table', columns: ['Key', 'Value'] }
-
-// File upload
-{
-  id: 'files',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,
-  acceptedTypes: 'image/*,application/pdf',
-}
-```
-
-## File Input Handling
-
-When your block accepts file uploads, use the basic/advanced mode pattern with `normalizeFileInput`.
-
-### Basic/Advanced File Pattern
-
-```typescript
-// Basic mode: Visual file upload
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from other blocks
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any subblock's `id` in the same block
-- Values are stored under subblock `id`, not `canonicalParamId`
-
-### Normalizing File Input in tools.config
-
-Use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  access: ['service_upload'],
-  config: {
-    tool: (params) => {
-      // Check all field IDs: uploadFile (basic), fileRef (advanced), fileContent (legacy)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `service_${params.operation}`
-    },
-  },
-}
-```
-
-**Why this pattern?**
-- Values come through as `params.uploadFile` or `params.fileRef` (the subblock IDs)
-- `canonicalParamId` only controls UI/schema mapping, not runtime values
-- `normalizeFileInput` handles JSON strings from advanced mode template resolution
-
-### File Input Types in `inputs`
-
-Use `type: 'json'` for file inputs:
-
-```typescript
-inputs: {
-  uploadFile: { type: 'json', description: 'Uploaded file (UserFile)' },
-  fileRef: { type: 'json', description: 'File reference from previous block' },
-  // Legacy field for backwards compatibility
-  fileContent: { type: 'string', description: 'Legacy: base64 encoded content' },
-}
-```
-
-### Multiple Files
-
-For multiple file uploads:
-
-```typescript
-{
-  id: 'attachments',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,  // Allow multiple files
-  maxSize: 25,     // Max size in MB per file
-  acceptedTypes: 'image/*,application/pdf,.doc,.docx',
-}
-
-// In tools.config:
-const normalizedFiles = normalizeFileInput(
-  params.attachments || params.attachmentRefs,
-  // No { single: true } - returns array
-)
-if (normalizedFiles) {
-  params.files = normalizedFiles
-}
-```
-
-## Condition Syntax
-
-Controls when a field is shown based on other field values.
-
-### Simple Condition
-```typescript
-condition: { field: 'operation', value: 'create' }
-// Shows when operation === 'create'
-```
-
-### Multiple Values (OR)
-```typescript
-condition: { field: 'operation', value: ['create', 'update'] }
-// Shows when operation is 'create' OR 'update'
-```
-
-### Negation
-```typescript
-condition: { field: 'operation', value: 'delete', not: true }
-// Shows when operation !== 'delete'
-```
-
-### Compound (AND)
-```typescript
-condition: {
-  field: 'operation',
-  value: 'send',
-  and: {
-    field: 'type',
-    value: 'dm',
-    not: true,
-  }
-}
-// Shows when operation === 'send' AND type !== 'dm'
-```
-
-### Complex Example
-```typescript
-condition: {
-  field: 'operation',
-  value: ['list', 'search'],
-  not: true,
-  and: {
-    field: 'authMethod',
-    value: 'oauth',
-  }
-}
-// Shows when operation NOT in ['list', 'search'] AND authMethod === 'oauth'
-```
-
-## DependsOn Pattern
-
-Controls when a field is enabled and when its options are refetched.
-
-### Simple Array (all must be set)
-```typescript
-dependsOn: ['credential']
-// Enabled only when credential has a value
-// Options refetch when credential changes
-
-dependsOn: ['credential', 'projectId']
-// Enabled only when BOTH have values
-```
-
-### Complex (all + any)
-```typescript
-dependsOn: {
-  all: ['authMethod'],           // All must be set
-  any: ['credential', 'apiKey']  // At least one must be set
-}
-// Enabled when authMethod is set AND (credential OR apiKey is set)
-```
-
-## Required Pattern
-
-Can be boolean or condition-based.
-
-### Simple Boolean
-```typescript
-required: true
-required: false
-```
-
-### Conditional Required
-```typescript
-required: { field: 'operation', value: 'create' }
-// Required only when operation === 'create'
-
-required: { field: 'operation', value: ['create', 'update'] }
-// Required when operation is 'create' OR 'update'
-```
-
-## Mode Pattern (Basic vs Advanced)
-
-Controls which UI view shows the field.
-
-### Mode Options
-- `'basic'` - Only in basic view (default UI)
-- `'advanced'` - Only in advanced view
-- `'both'` - Both views (default if not specified)
-- `'trigger'` - Only in trigger configuration
-
-### canonicalParamId Pattern
-
-Maps multiple UI fields to a single serialized parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  dependsOn: ['credential'],
-}
-
-// Advanced mode: Manual input
-{
-  id: 'channelId',
-  title: 'Channel ID',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  placeholder: 'Enter channel ID manually',
-}
-```
-
-**How it works:**
-- In basic mode: `channel` selector value → `params.channel`
-- In advanced mode: `channelId` input value → `params.channel`
-- The serializer consolidates based on current mode
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any other subblock's `id` in the same block (causes conflicts)
-- `canonicalParamId` must be unique per block (only one basic/advanced pair per canonicalParamId)
-- ONLY use `canonicalParamId` to link basic/advanced mode alternatives for the same logical parameter
-- Do NOT use it for any other purpose
-
-## WandConfig Pattern
-
-Enables AI-assisted field generation.
-
-```typescript
-{
-  id: 'query',
-  title: 'Query',
-  type: 'code',
-  language: 'json',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a query based on the user request. Return ONLY the JSON.',
-    placeholder: 'Describe what you want to query...',
-    generationType: 'json-object',  // Optional: affects AI behavior
-    maintainHistory: true,          // Optional: keeps conversation context
-  },
-}
-```
-
-### Generation Types
-- `'javascript-function-body'` - JS code generation
-- `'json-object'` - Raw JSON (adds "no markdown" instruction)
-- `'json-schema'` - JSON Schema definitions
-- `'sql-query'` - SQL statements
-- `'timestamp'` - Adds current date/time context
-
-## Tools Configuration
-
-**Important:** `tools.config.tool` runs during serialization before variable resolution. Put `Number()` and other type coercions in `tools.config.params` instead, which runs at execution time after variables are resolved.
-
-**Preferred:** Use tool names directly as dropdown option IDs to avoid switch cases:
-```typescript
-// Dropdown options use tool IDs directly
-options: [
-  { label: 'Create', id: 'service_create' },
-  { label: 'Read', id: 'service_read' },
-]
-
-// Tool selector just returns the operation value
-tool: (params) => params.operation,
-```
-
-### With Parameter Transformation
-```typescript
-tools: {
-  access: ['service_action'],
-  config: {
-    tool: (params) => 'service_action',
-    params: (params) => ({
-      id: params.resourceId,
-      data: typeof params.data === 'string' ? JSON.parse(params.data) : params.data,
-    }),
-  },
-}
-```
-
-### V2 Versioned Tool Selector
-```typescript
-import { createVersionedToolSelector } from '@/blocks/utils'
-
-tools: {
-  access: [
-    'service_create_v2',
-    'service_read_v2',
-    'service_update_v2',
-  ],
-  config: {
-    tool: createVersionedToolSelector({
-      baseToolSelector: (params) => `service_${params.operation}`,
-      suffix: '_v2',
-      fallbackToolId: 'service_create_v2',
-    }),
-  },
-}
-```
-
-## Outputs Definition
-
-**IMPORTANT:** Block outputs have a simpler schema than tool outputs. Block outputs do NOT support:
-- `optional: true` - This is only for tool outputs
-- `items` property - This is only for tool outputs with array types
-
-Block outputs only support:
-- `type` - The data type ('string', 'number', 'boolean', 'json', 'array')
-- `description` - Human readable description
-- Nested object structure (for complex types)
-
-```typescript
-outputs: {
-  // Simple outputs
-  id: { type: 'string', description: 'Resource ID' },
-  success: { type: 'boolean', description: 'Whether operation succeeded' },
-
-  // Use type: 'json' for complex objects or arrays (NOT type: 'array' with items)
-  items: { type: 'json', description: 'List of items' },
-  metadata: { type: 'json', description: 'Response metadata' },
-
-  // Nested outputs (for structured data)
-  user: {
-    id: { type: 'string', description: 'User ID' },
-    name: { type: 'string', description: 'User name' },
-    email: { type: 'string', description: 'User email' },
-  },
-}
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **describe the inner fields in the description** so downstream blocks know what properties are available. For well-known, stable objects, use nested output definitions instead:
-
-```typescript
-outputs: {
-  // BAD: Opaque json with no info about what's inside
-  plan: { type: 'json', description: 'Zone plan information' },
-
-  // GOOD: Describe the known fields in the description
-  plan: {
-    type: 'json',
-    description: 'Zone plan information (id, name, price, currency, frequency, is_subscribed)',
-  },
-
-  // BEST: Use nested output definition when the shape is stable and well-known
-  plan: {
-    id: { type: 'string', description: 'Plan identifier' },
-    name: { type: 'string', description: 'Plan name' },
-    price: { type: 'number', description: 'Plan price' },
-    currency: { type: 'string', description: 'Price currency' },
-  },
-}
-```
-
-Use the nested pattern when:
-- The object has a small, stable set of fields (< 10)
-- Downstream blocks will commonly access specific properties
-- The API response shape is well-documented and unlikely to change
-
-Use `type: 'json'` with a descriptive string when:
-- The object has many fields or a dynamic shape
-- It represents a list/array of items
-- The shape varies by operation
-
-## V2 Block Pattern
-
-When creating V2 blocks (alongside legacy V1):
-
-```typescript
-// V1 Block - mark as legacy
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service (Legacy)',
-  hideFromToolbar: true,  // Hide from toolbar
-  // ... rest of config
-}
-
-// V2 Block - visible, uses V2 tools
-export const ServiceV2Block: BlockConfig = {
-  type: 'service_v2',
-  name: 'Service',              // Clean name
-  hideFromToolbar: false,       // Visible
-  subBlocks: ServiceBlock.subBlocks,  // Reuse UI
-  tools: {
-    access: ServiceBlock.tools?.access?.map(id => `${id}_v2`) || [],
-    config: {
-      tool: createVersionedToolSelector({
-        baseToolSelector: (params) => (ServiceBlock.tools?.config as any)?.tool(params),
-        suffix: '_v2',
-        fallbackToolId: 'service_default_v2',
-      }),
-      params: ServiceBlock.tools?.config?.params,
-    },
-  },
-  outputs: {
-    // Flat, API-aligned outputs (not wrapped in content/metadata)
-  },
-}
-```
-
-## Registering Blocks
-
-After creating the block, remind the user to:
-1. Import in `apps/sim/blocks/registry.ts`
-2. Add to the `registry` object (alphabetically):
-
-```typescript
-import { ServiceBlock } from '@/blocks/blocks/service'
-
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  service: ServiceBlock,
-}
-```
-
-## Complete Example
-
-```typescript
-import { ServiceIcon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service',
-  description: 'Integrate with Service API',
-  longDescription: 'Full description for documentation...',
-  docsLink: 'https://docs.sim.ai/tools/service',
-  category: 'tools',
-  integrationType: IntegrationType.DeveloperTools,
-  tags: ['oauth', 'api'],
-  bgColor: '#FF6B6B',
-  icon: ServiceIcon,
-  authMode: AuthMode.OAuth,
-
-  subBlocks: [
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Create', id: 'create' },
-        { label: 'Read', id: 'read' },
-        { label: 'Update', id: 'update' },
-        { label: 'Delete', id: 'delete' },
-      ],
-      value: () => 'create',
-    },
-    {
-      id: 'credential',
-      title: 'Service Account',
-      type: 'oauth-input',
-      serviceId: 'service',
-      requiredScopes: getScopesForService('service'),
-      placeholder: 'Select account',
-      required: true,
-    },
-    {
-      id: 'resourceId',
-      title: 'Resource ID',
-      type: 'short-input',
-      placeholder: 'Enter resource ID',
-      condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-      required: { field: 'operation', value: ['read', 'update', 'delete'] },
-    },
-    {
-      id: 'name',
-      title: 'Name',
-      type: 'short-input',
-      placeholder: 'Resource name',
-      condition: { field: 'operation', value: ['create', 'update'] },
-      required: { field: 'operation', value: 'create' },
-    },
-  ],
-
-  tools: {
-    access: ['service_create', 'service_read', 'service_update', 'service_delete'],
-    config: {
-      tool: (params) => `service_${params.operation}`,
-    },
-  },
-
-  outputs: {
-    id: { type: 'string', description: 'Resource ID' },
-    name: { type: 'string', description: 'Resource name' },
-    createdAt: { type: 'string', description: 'Creation timestamp' },
-  },
-}
-```
-
-## Connecting Blocks with Triggers
-
-If the service supports webhooks, connect the block to its triggers.
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const ServiceBlock: BlockConfig = {
-  // ... basic config ...
-
-  triggers: {
-    enabled: true,
-    available: ['service_event_a', 'service_event_b', 'service_webhook'],
-  },
-
-  subBlocks: [
-    // Tool subBlocks first...
-    { id: 'operation', /* ... */ },
-
-    // Then spread trigger subBlocks
-    ...getTrigger('service_event_a').subBlocks,
-    ...getTrigger('service_event_b').subBlocks,
-    ...getTrigger('service_webhook').subBlocks,
-  ],
-}
-```
-
-See the `/add-trigger` skill for creating triggers.
-
-## Icon Requirement
-
-If the icon doesn't already exist in `@/components/icons.tsx`, **do NOT search for it yourself**. After completing the block, ask the user to provide the SVG:
-
-```
-The block is complete, but I need an icon for {Service}.
-Please provide the SVG and I'll convert it to a React component.
-
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-```
-
-## Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. This includes:
-- Pagination tokens
-- Time range filters (start/end time)
-- Sort order options
-- Reply settings
-- Rarely used IDs (e.g., reply-to tweet ID, quote tweet ID)
-- Max results / limits
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  placeholder: 'ISO 8601 timestamp',
-  condition: { field: 'operation', value: ['search', 'list'] },
-  mode: 'advanced',  // Rarely used, hide from basic view
-}
-```
-
-## WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually, such as timestamps, comma-separated lists, and complex query strings. This gives users an AI-assisted input experience.
-
-```typescript
-// Timestamps - use generationType: 'timestamp' to inject current date context
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp based on the user description. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-
-// Comma-separated lists - simple prompt without generationType
-{
-  id: 'mediaIds',
-  title: 'Media IDs',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a comma-separated list of media IDs. Return ONLY the comma-separated values.',
-  },
-}
-```
-
-## Naming Convention
-
-All tool IDs referenced in `tools.access` and returned by `tools.config.tool` MUST use `snake_case` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase.
-
-## Checklist Before Finishing
-
-- [ ] `integrationType` is set to the correct `IntegrationType` enum value
-- [ ] `tags` array includes all applicable `IntegrationTag` values
-- [ ] All subBlocks have `id`, `title` (except switch), and `type`
-- [ ] Conditions use correct syntax (field, value, not, and)
-- [ ] DependsOn set for fields that need other values
-- [ ] Required fields marked correctly (boolean or condition)
-- [ ] OAuth inputs have correct `serviceId` and `requiredScopes: getScopesForService(serviceId)`
-- [ ] Scope descriptions added to `SCOPE_DESCRIPTIONS` in `lib/oauth/utils.ts` for any new scopes
-- [ ] Tools.access lists all tool IDs (snake_case)
-- [ ] Tools.config.tool returns correct tool ID (snake_case)
-- [ ] Outputs match tool outputs
-- [ ] Block registered in registry.ts
-- [ ] If icon missing: asked user to provide SVG
-- [ ] If triggers exist: `triggers` config set, trigger subBlocks spread
-- [ ] Optional/rarely-used fields set to `mode: 'advanced'`
-- [ ] Timestamps and complex inputs have `wandConfig` enabled
-
-## Final Validation (Required)
-
-After creating the block, you MUST validate it against every tool it references:
-
-1. **Read every tool definition** that appears in `tools.access` — do not skip any
-2. **For each tool, verify the block has correct:**
-   - SubBlock inputs that cover all required tool params (with correct `condition` to show for that operation)
-   - SubBlock input types that match the tool param types (e.g., dropdown for enums, short-input for strings)
-   - `tools.config.params` correctly maps subBlock IDs to tool param names (if they differ)
-   - Type coercions in `tools.config.params` for any params that need conversion (Number(), Boolean(), JSON.parse())
-3. **Verify block outputs** cover the key fields returned by all tools
-4. **Verify conditions** — each subBlock should only show for the operations that actually use it

.claude/commands/add-connector.md

@@ -1,528 +0,0 @@
----
-description: Add a knowledge base connector for syncing documents from an external source
-argument-hint: <service-name> [api-docs-url]
----
-
-# Add Connector Skill
-
-You are an expert at adding knowledge base connectors to Sim. A connector syncs documents from an external source (Confluence, Google Drive, Notion, etc.) into a knowledge base.
-
-## Your Task
-
-When the user asks you to create a connector:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Determine the auth mode: **OAuth** (if Sim already has an OAuth provider for the service) or **API key** (if the service uses API key / Bearer token auth)
-3. Create the connector directory and config
-4. Register it in the connector registry
-
-## Directory Structure
-
-Create files in `apps/sim/connectors/{service}/`:
-```
-connectors/{service}/
-├── index.ts          # Barrel export
-└── {service}.ts      # ConnectorConfig definition
-```
-
-## Authentication
-
-Connectors use a discriminated union for auth config (`ConnectorAuthConfig` in `connectors/types.ts`):
-
-```typescript
-type ConnectorAuthConfig =
-  | { mode: 'oauth'; provider: OAuthService; requiredScopes?: string[] }
-  | { mode: 'apiKey'; label?: string; placeholder?: string }
-```
-
-### OAuth mode
-For services with existing OAuth providers in `apps/sim/lib/oauth/types.ts`. The `provider` must match an `OAuthService`. The modal shows a credential picker and handles token refresh automatically.
-
-### API key mode
-For services that use API key / Bearer token auth. The modal shows a password input with the configured `label` and `placeholder`. The API key is encrypted at rest using AES-256-GCM and stored in a dedicated `encryptedApiKey` column on the connector record. The sync engine decrypts it automatically — connectors receive the raw access token in `listDocuments`, `getDocument`, and `validateConfig`.
-
-## ConnectorConfig Structure
-
-### OAuth connector example
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { {Service}Icon } from '@/components/icons'
-import { fetchWithRetry } from '@/lib/knowledge/documents/utils'
-import type { ConnectorConfig, ExternalDocument, ExternalDocumentList } from '@/connectors/types'
-
-const logger = createLogger('{Service}Connector')
-
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'oauth',
-    provider: '{service}',          // Must match OAuthService in lib/oauth/types.ts
-    requiredScopes: ['read:...'],
-  },
-
-  configFields: [
-    // Rendered dynamically by the add-connector modal UI
-    // Supports 'short-input' and 'dropdown' types
-  ],
-
-  listDocuments: async (accessToken, sourceConfig, cursor) => {
-    // Return metadata stubs with contentDeferred: true (if per-doc content fetch needed)
-    // Or full documents with content (if list API returns content inline)
-    // Return { documents: ExternalDocument[], nextCursor?, hasMore }
-  },
-
-  getDocument: async (accessToken, sourceConfig, externalId) => {
-    // Fetch full content for a single document
-    // Return ExternalDocument with contentDeferred: false, or null
-  },
-
-  validateConfig: async (accessToken, sourceConfig) => {
-    // Return { valid: true } or { valid: false, error: 'message' }
-  },
-
-  // Optional: map source metadata to semantic tag keys (translated to slots by sync engine)
-  mapTags: (metadata) => {
-    // Return Record<string, unknown> with keys matching tagDefinitions[].id
-  },
-}
-```
-
-### API key connector example
-
-```typescript
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'apiKey',
-    label: 'API Key',                       // Shown above the input field
-    placeholder: 'Enter your {Service} API key',  // Input placeholder
-  },
-
-  configFields: [ /* ... */ ],
-  listDocuments: async (accessToken, sourceConfig, cursor) => { /* ... */ },
-  getDocument: async (accessToken, sourceConfig, externalId) => { /* ... */ },
-  validateConfig: async (accessToken, sourceConfig) => { /* ... */ },
-}
-```
-
-## ConfigField Types
-
-The add-connector modal renders these automatically — no custom UI needed.
-
-Three field types are supported: `short-input`, `dropdown`, and `selector`.
-
-```typescript
-// Text input
-{
-  id: 'domain',
-  title: 'Domain',
-  type: 'short-input',
-  placeholder: 'yoursite.example.com',
-  required: true,
-}
-
-// Dropdown (static options)
-{
-  id: 'contentType',
-  title: 'Content Type',
-  type: 'dropdown',
-  required: false,
-  options: [
-    { label: 'Pages only', id: 'page' },
-    { label: 'Blog posts only', id: 'blogpost' },
-    { label: 'All content', id: 'all' },
-  ],
-}
-```
-
-## Dynamic Selectors (Canonical Pairs)
-
-Use `type: 'selector'` to fetch options dynamically from the existing selector registry (`hooks/selectors/registry.ts`). Selectors are always paired with a manual fallback input using the **canonical pair** pattern — a `selector` field (basic mode) and a `short-input` field (advanced mode) linked by `canonicalParamId`.
-
-The user sees a toggle button (ArrowLeftRight) to switch between the selector dropdown and manual text input. On submit, the modal resolves each canonical pair to the active mode's value, keyed by `canonicalParamId`.
-
-### Rules
-
-1. **Every selector field MUST have a canonical pair** — a corresponding `short-input` (or `dropdown`) field with the same `canonicalParamId` and `mode: 'advanced'`.
-2. **`required` must be set identically on both fields** in a pair. If the selector is required, the manual input must also be required.
-3. **`canonicalParamId` must match the key the connector expects in `sourceConfig`** (e.g. `baseId`, `channel`, `teamId`). The advanced field's `id` should typically match `canonicalParamId`.
-4. **`dependsOn` references the selector field's `id`**, not the `canonicalParamId`. The modal propagates dependency clearing across canonical siblings automatically — changing either field in a parent pair clears dependent children.
-
-### Selector canonical pair example (Airtable base → table cascade)
-
-```typescript
-configFields: [
-  // Base: selector (basic) + manual (advanced)
-  {
-    id: 'baseSelector',
-    title: 'Base',
-    type: 'selector',
-    selectorKey: 'airtable.bases',     // Must exist in hooks/selectors/registry.ts
-    canonicalParamId: 'baseId',
-    mode: 'basic',
-    placeholder: 'Select a base',
-    required: true,
-  },
-  {
-    id: 'baseId',
-    title: 'Base ID',
-    type: 'short-input',
-    canonicalParamId: 'baseId',
-    mode: 'advanced',
-    placeholder: 'e.g. appXXXXXXXXXXXXXX',
-    required: true,
-  },
-  // Table: selector depends on base (basic) + manual (advanced)
-  {
-    id: 'tableSelector',
-    title: 'Table',
-    type: 'selector',
-    selectorKey: 'airtable.tables',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'basic',
-    dependsOn: ['baseSelector'],       // References the selector field ID
-    placeholder: 'Select a table',
-    required: true,
-  },
-  {
-    id: 'tableIdOrName',
-    title: 'Table Name or ID',
-    type: 'short-input',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'advanced',
-    placeholder: 'e.g. Tasks',
-    required: true,
-  },
-  // Non-selector fields stay as-is
-  { id: 'maxRecords', title: 'Max Records', type: 'short-input', ... },
-]
-```
-
-### Selector with domain dependency (Jira/Confluence pattern)
-
-When a selector depends on a plain `short-input` field (no canonical pair), `dependsOn` references that field's `id` directly. The `domain` field's value maps to `SelectorContext.domain` automatically via `SELECTOR_CONTEXT_FIELDS`.
-
-```typescript
-configFields: [
-  {
-    id: 'domain',
-    title: 'Jira Domain',
-    type: 'short-input',
-    placeholder: 'yoursite.atlassian.net',
-    required: true,
-  },
-  {
-    id: 'projectSelector',
-    title: 'Project',
-    type: 'selector',
-    selectorKey: 'jira.projects',
-    canonicalParamId: 'projectKey',
-    mode: 'basic',
-    dependsOn: ['domain'],
-    placeholder: 'Select a project',
-    required: true,
-  },
-  {
-    id: 'projectKey',
-    title: 'Project Key',
-    type: 'short-input',
-    canonicalParamId: 'projectKey',
-    mode: 'advanced',
-    placeholder: 'e.g. ENG, PROJ',
-    required: true,
-  },
-]
-```
-
-### How `dependsOn` maps to `SelectorContext`
-
-The connector selector field builds a `SelectorContext` from dependency values. For the mapping to work, each dependency's `canonicalParamId` (or field `id` for non-canonical fields) must exist in `SELECTOR_CONTEXT_FIELDS` (`lib/workflows/subblocks/context.ts`):
-
-```
-oauthCredential, domain, teamId, projectId, knowledgeBaseId, planId,
-siteId, collectionId, spreadsheetId, fileId, baseId, datasetId, serviceDeskId
-```
-
-### Available selector keys
-
-Check `hooks/selectors/types.ts` for the full `SelectorKey` union. Common ones for connectors:
-
-| SelectorKey | Context Deps | Returns |
-|-------------|-------------|---------|
-| `airtable.bases` | credential | Base ID + name |
-| `airtable.tables` | credential, `baseId` | Table ID + name |
-| `slack.channels` | credential | Channel ID + name |
-| `gmail.labels` | credential | Label ID + name |
-| `google.calendar` | credential | Calendar ID + name |
-| `linear.teams` | credential | Team ID + name |
-| `linear.projects` | credential, `teamId` | Project ID + name |
-| `jira.projects` | credential, `domain` | Project key + name |
-| `confluence.spaces` | credential, `domain` | Space key + name |
-| `notion.databases` | credential | Database ID + name |
-| `asana.workspaces` | credential | Workspace GID + name |
-| `microsoft.teams` | credential | Team ID + name |
-| `microsoft.channels` | credential, `teamId` | Channel ID + name |
-| `webflow.sites` | credential | Site ID + name |
-| `outlook.folders` | credential | Folder ID + name |
-
-## ExternalDocument Shape
-
-Every document returned from `listDocuments`/`getDocument` must include:
-
-```typescript
-{
-  externalId: string          // Source-specific unique ID
-  title: string               // Document title
-  content: string             // Extracted plain text (or '' if contentDeferred)
-  contentDeferred?: boolean   // true = content will be fetched via getDocument
-  mimeType: 'text/plain'     // Always text/plain (content is extracted)
-  contentHash: string         // Metadata-based hash for change detection
-  sourceUrl?: string          // Link back to original (stored on document record)
-  metadata?: Record<string, unknown>  // Source-specific data (fed to mapTags)
-}
-```
-
-## Content Deferral (Required for file/content-download connectors)
-
-**All connectors that require per-document API calls to fetch content MUST use `contentDeferred: true`.** This is the standard pattern — `listDocuments` returns lightweight metadata stubs, and content is fetched lazily by the sync engine via `getDocument` only for new/changed documents.
-
-This pattern is critical for reliability: the sync engine processes documents in batches and enqueues each batch for processing immediately. If a sync times out, all previously-batched documents are already queued. Without deferral, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-### When to use `contentDeferred: true`
-
-- The service's list API does NOT return document content (only metadata)
-- Content requires a separate download/export API call per document
-- Examples: Google Drive, OneDrive, SharePoint, Dropbox, Notion, Confluence, Gmail, Obsidian, Evernote, GitHub
-
-### When NOT to use `contentDeferred`
-
-- The list API already returns the full content inline (e.g., Slack messages, Reddit posts, HubSpot notes)
-- No per-document API call is needed to get content
-
-### Content Hash Strategy
-
-Use a **metadata-based** `contentHash` — never a content-based hash. The hash must be derivable from the list response metadata alone, so the sync engine can detect changes without downloading content.
-
-Good metadata hash sources:
-- `modifiedTime` / `lastModifiedDateTime` — changes when file is edited
-- Git blob SHA — unique per content version
-- API-provided content hash (e.g., Dropbox `content_hash`)
-- Version number (e.g., Confluence page version)
-
-Format: `{service}:{id}:{changeIndicator}`
-
-```typescript
-// Google Drive: modifiedTime changes on edit
-contentHash: `gdrive:${file.id}:${file.modifiedTime ?? ''}`
-
-// GitHub: blob SHA is a content-addressable hash
-contentHash: `gitsha:${item.sha}`
-
-// Dropbox: API provides content_hash
-contentHash: `dropbox:${entry.id}:${entry.content_hash ?? entry.server_modified}`
-
-// Confluence: version number increments on edit
-contentHash: `confluence:${page.id}:${page.version.number}`
-```
-
-**Critical invariant:** The `contentHash` MUST be identical whether produced by `listDocuments` (stub) or `getDocument` (full doc). Both should use the same stub function to guarantee this.
-
-### Implementation Pattern
-
-```typescript
-// 1. Create a stub function (sync, no API calls)
-function fileToStub(file: ServiceFile): ExternalDocument {
-  return {
-    externalId: file.id,
-    title: file.name || 'Untitled',
-    content: '',
-    contentDeferred: true,
-    mimeType: 'text/plain',
-    sourceUrl: `https://service.com/file/${file.id}`,
-    contentHash: `service:${file.id}:${file.modifiedTime ?? ''}`,
-    metadata: { /* fields needed by mapTags */ },
-  }
-}
-
-// 2. listDocuments returns stubs (fast, metadata only)
-listDocuments: async (accessToken, sourceConfig, cursor) => {
-  const response = await fetchWithRetry(listUrl, { ... })
-  const files = (await response.json()).files
-  const documents = files.map(fileToStub)
-  return { documents, nextCursor, hasMore }
-}
-
-// 3. getDocument fetches content and returns full doc with SAME contentHash
-getDocument: async (accessToken, sourceConfig, externalId) => {
-  const metadata = await fetchWithRetry(metadataUrl, { ... })
-  const file = await metadata.json()
-  if (file.trashed) return null
-
-  try {
-    const content = await fetchContent(accessToken, file)
-    if (!content.trim()) return null
-    const stub = fileToStub(file)
-    return { ...stub, content, contentDeferred: false }
-  } catch (error) {
-    logger.warn(`Failed to fetch content for: ${file.name}`, { error })
-    return null
-  }
-}
-```
-
-### Reference Implementations
-
-- **Google Drive**: `connectors/google-drive/google-drive.ts` — file download/export with `modifiedTime` hash
-- **GitHub**: `connectors/github/github.ts` — git blob SHA hash
-- **Notion**: `connectors/notion/notion.ts` — blocks API with `last_edited_time` hash
-- **Confluence**: `connectors/confluence/confluence.ts` — version number hash
-
-## tagDefinitions — Declared Tag Definitions
-
-Declare which tags the connector populates using semantic IDs. Shown in the add-connector modal as opt-out checkboxes.
-On connector creation, slots are **dynamically assigned** via `getNextAvailableSlot` — connectors never hardcode slot names.
-
-```typescript
-tagDefinitions: [
-  { id: 'labels', displayName: 'Labels', fieldType: 'text' },
-  { id: 'version', displayName: 'Version', fieldType: 'number' },
-  { id: 'lastModified', displayName: 'Last Modified', fieldType: 'date' },
-],
-```
-
-Each entry has:
-- `id`: Semantic key matching a key returned by `mapTags` (e.g. `'labels'`, `'version'`)
-- `displayName`: Human-readable name shown in the UI (e.g. "Labels", "Last Modified")
-- `fieldType`: `'text'` | `'number'` | `'date'` | `'boolean'` — determines which slot pool to draw from
-
-Users can opt out of specific tags in the modal. Disabled IDs are stored in `sourceConfig.disabledTagIds`.
-The assigned mapping (`semantic id → slot`) is stored in `sourceConfig.tagSlotMapping`.
-
-## mapTags — Metadata to Semantic Keys
-
-Maps source metadata to semantic tag keys. Required if `tagDefinitions` is set.
-The sync engine calls this automatically and translates semantic keys to actual DB slots
-using the `tagSlotMapping` stored on the connector.
-
-Return keys must match the `id` values declared in `tagDefinitions`.
-
-```typescript
-mapTags: (metadata: Record<string, unknown>): Record<string, unknown> => {
-  const result: Record<string, unknown> = {}
-
-  // Validate arrays before casting — metadata may be malformed
-  const labels = Array.isArray(metadata.labels) ? (metadata.labels as string[]) : []
-  if (labels.length > 0) result.labels = labels.join(', ')
-
-  // Validate numbers — guard against NaN
-  if (metadata.version != null) {
-    const num = Number(metadata.version)
-    if (!Number.isNaN(num)) result.version = num
-  }
-
-  // Validate dates — guard against Invalid Date
-  if (typeof metadata.lastModified === 'string') {
-    const date = new Date(metadata.lastModified)
-    if (!Number.isNaN(date.getTime())) result.lastModified = date
-  }
-
-  return result
-}
-```
-
-## External API Calls — Use `fetchWithRetry`
-
-All external API calls must use `fetchWithRetry` from `@/lib/knowledge/documents/utils` instead of raw `fetch()`. This provides exponential backoff with retries on 429/502/503/504 errors. It returns a standard `Response` — all `.ok`, `.json()`, `.text()` checks work unchanged.
-
-For `validateConfig` (user-facing, called on save), pass `VALIDATE_RETRY_OPTIONS` to cap wait time at ~7s. Background operations (`listDocuments`, `getDocument`) use the built-in defaults (5 retries, ~31s max).
-
-```typescript
-import { VALIDATE_RETRY_OPTIONS, fetchWithRetry } from '@/lib/knowledge/documents/utils'
-
-// Background sync — use defaults
-const response = await fetchWithRetry(url, {
-  method: 'GET',
-  headers: { Authorization: `Bearer ${accessToken}` },
-})
-
-// validateConfig — tighter retry budget
-const response = await fetchWithRetry(url, { ... }, VALIDATE_RETRY_OPTIONS)
-```
-
-## sourceUrl
-
-If `ExternalDocument.sourceUrl` is set, the sync engine stores it on the document record. Always construct the full URL (not a relative path).
-
-## Sync Engine Behavior (Do Not Modify)
-
-The sync engine (`lib/knowledge/connectors/sync-engine.ts`) is connector-agnostic. It:
-1. Calls `listDocuments` with pagination until `hasMore` is false
-2. Compares `contentHash` to detect new/changed/unchanged documents
-3. Stores `sourceUrl` and calls `mapTags` on insert/update automatically
-4. Handles soft-delete of removed documents
-5. Resolves access tokens automatically — OAuth tokens are refreshed, API keys are decrypted from the `encryptedApiKey` column
-
-You never need to modify the sync engine when adding a connector.
-
-## Icon
-
-The `icon` field on `ConnectorConfig` is used throughout the UI — in the connector list, the add-connector modal, and as the document icon in the knowledge base table (replacing the generic file type icon for connector-sourced documents). The icon is read from `CONNECTOR_REGISTRY[connectorType].icon` at runtime — no separate icon map to maintain.
-
-If the service already has an icon in `apps/sim/components/icons.tsx` (from a tool integration), reuse it. Otherwise, ask the user to provide the SVG.
-
-## Registering
-
-Add one line to `apps/sim/connectors/registry.ts`:
-
-```typescript
-import { {service}Connector } from '@/connectors/{service}'
-
-export const CONNECTOR_REGISTRY: ConnectorRegistry = {
-  // ... existing connectors ...
-  {service}: {service}Connector,
-}
-```
-
-## Reference Implementations
-
-- **OAuth + contentDeferred**: `apps/sim/connectors/google-drive/google-drive.ts` — file download with metadata-based hash, `orderBy` for deterministic pagination
-- **OAuth + contentDeferred (blocks API)**: `apps/sim/connectors/notion/notion.ts` — complex block content extraction deferred to `getDocument`
-- **OAuth + contentDeferred (git)**: `apps/sim/connectors/github/github.ts` — blob SHA hash, tree listing
-- **OAuth + inline content**: `apps/sim/connectors/confluence/confluence.ts` — multiple config field types, `mapTags`, label fetching
-- **API key**: `apps/sim/connectors/fireflies/fireflies.ts` — GraphQL API with Bearer token auth
-
-## Checklist
-
-- [ ] Created `connectors/{service}/{service}.ts` with full ConnectorConfig
-- [ ] Created `connectors/{service}/index.ts` barrel export
-- [ ] **Auth configured correctly:**
-  - OAuth: `auth.provider` matches an existing `OAuthService` in `lib/oauth/types.ts`
-  - API key: `auth.label` and `auth.placeholder` set appropriately
-- [ ] **Selector fields configured correctly (if applicable):**
-  - Every `type: 'selector'` field has a canonical pair (`short-input` or `dropdown` with same `canonicalParamId` and `mode: 'advanced'`)
-  - `required` is identical on both fields in each canonical pair
-  - `selectorKey` exists in `hooks/selectors/registry.ts`
-  - `dependsOn` references selector field IDs (not `canonicalParamId`)
-  - Dependency `canonicalParamId` values exist in `SELECTOR_CONTEXT_FIELDS`
-- [ ] `listDocuments` handles pagination with metadata-based content hashes
-- [ ] `contentDeferred: true` used if content requires per-doc API calls (file download, export, blocks fetch)
-- [ ] `contentHash` is metadata-based (not content-based) and identical between stub and `getDocument`
-- [ ] `sourceUrl` set on each ExternalDocument (full URL, not relative)
-- [ ] `metadata` includes source-specific data for tag mapping
-- [ ] `tagDefinitions` declared for each semantic key returned by `mapTags`
-- [ ] `mapTags` implemented if source has useful metadata (labels, dates, versions)
-- [ ] `validateConfig` verifies the source is accessible
-- [ ] All external API calls use `fetchWithRetry` (not raw `fetch`)
-- [ ] All optional config fields validated in `validateConfig`
-- [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
-- [ ] Registered in `connectors/registry.ts`

.claude/commands/add-hosted-key.md

@@ -1,296 +0,0 @@
----
-description: Add hosted API key support to a tool so Sim provides the key when users don't bring their own
-argument-hint: <service-name>
----
-
-# Adding Hosted Key Support to a Tool
-
-When a tool has hosted key support, Sim provides its own API key if the user hasn't configured one (via BYOK or env var). Usage is metered and billed to the workspace.
-
-## Overview
-
-| Step | What | Where |
-|------|------|-------|
-| 1 | Register BYOK provider ID | `tools/types.ts`, `app/api/workspaces/[id]/byok-keys/route.ts` |
-| 2 | Research the API's pricing and rate limits | API docs / pricing page (before writing any code) |
-| 3 | Add `hosting` config to the tool | `tools/{service}/{action}.ts` |
-| 4 | Hide API key field when hosted | `blocks/blocks/{service}.ts` |
-| 5 | Add to BYOK settings UI | BYOK settings component (`byok.tsx`) |
-| 6 | Summarize pricing and throttling comparison | Output to user (after all code changes) |
-
-## Step 1: Register the BYOK Provider ID
-
-Add the new provider to the `BYOKProviderId` union in `tools/types.ts`:
-
-```typescript
-export type BYOKProviderId =
-  | 'openai'
-  | 'anthropic'
-  // ...existing providers
-  | 'your_service'
-```
-
-Then add it to `VALID_PROVIDERS` in `app/api/workspaces/[id]/byok-keys/route.ts`:
-
-```typescript
-const VALID_PROVIDERS = ['openai', 'anthropic', 'google', 'mistral', 'your_service'] as const
-```
-
-## Step 2: Research the API's Pricing Model and Rate Limits
-
-**Before writing any `getCost` or `rateLimit` code**, look up the service's official documentation for both pricing and rate limits. You need to understand:
-
-### Pricing
-
-1. **How the API charges** — per request, per credit, per token, per step, per minute, etc.
-2. **Whether the API reports cost in its response** — look for fields like `creditsUsed`, `costDollars`, `tokensUsed`, or similar in the response body or headers
-3. **Whether cost varies by endpoint/options** — some APIs charge more for certain features (e.g., Firecrawl charges 1 credit/page base but +4 for JSON format, +4 for enhanced mode)
-4. **The dollar-per-unit rate** — what each credit/token/unit costs in dollars on our plan
-
-### Rate Limits
-
-1. **What rate limits the API enforces** — requests per minute/second, tokens per minute, concurrent requests, etc.
-2. **Whether limits vary by plan tier** — free vs paid vs enterprise often have different ceilings
-3. **Whether limits are per-key or per-account** — determines whether adding more hosted keys actually increases total throughput
-4. **What the API returns when rate limited** — HTTP 429, `Retry-After` header, error body format, etc.
-5. **Whether there are multiple dimensions** — some APIs limit both requests/min AND tokens/min independently
-
-Search the API's docs/pricing page (use WebSearch/WebFetch). Capture the pricing model as a comment in `getCost` so future maintainers know the source of truth.
-
-### Setting Our Rate Limits
-
-Our rate limiter (`lib/core/rate-limiter/hosted-key/`) uses a token-bucket algorithm applied **per billing actor** (workspace). It supports two modes:
-
-- **`per_request`** — simple; just `requestsPerMinute`. Good when the API charges flat per-request or cost doesn't vary much.
-- **`custom`** — `requestsPerMinute` plus additional `dimensions` (e.g., `tokens`, `search_units`). Each dimension has its own `limitPerMinute` and an `extractUsage` function that reads actual usage from the response. Use when the API charges on a variable metric (tokens, credits) and you want to cap that metric too.
-
-When choosing values for `requestsPerMinute` and any dimension limits:
-
-- **Stay well below the API's per-key limit** — our keys are shared across all workspaces. If the API allows 60 RPM per key and we have 3 keys, the global ceiling is ~180 RPM. Set the per-workspace limit low enough (e.g., 20-60 RPM) that many workspaces can coexist without collectively hitting the API's ceiling.
-- **Account for key pooling** — our round-robin distributes requests across `N` hosted keys, so the effective API-side rate per key is `(total requests) / N`. But per-workspace limits are enforced *before* key selection, so they apply regardless of key count.
-- **Prefer conservative defaults** — it's easy to raise limits later but hard to claw back after users depend on high throughput.
-
-## Step 3: Add `hosting` Config to the Tool
-
-Add a `hosting` object to the tool's `ToolConfig`. This tells the execution layer how to acquire hosted keys, calculate cost, and rate-limit.
-
-```typescript
-hosting: {
-  envKeyPrefix: 'YOUR_SERVICE_API_KEY',
-  apiKeyParam: 'apiKey',
-  byokProviderId: 'your_service',
-  pricing: {
-    type: 'custom',
-    getCost: (_params, output) => {
-      if (output.creditsUsed == null) {
-        throw new Error('Response missing creditsUsed field')
-      }
-      const creditsUsed = output.creditsUsed as number
-      const cost = creditsUsed * 0.001 // dollars per credit
-      return { cost, metadata: { creditsUsed } }
-    },
-  },
-  rateLimit: {
-    mode: 'per_request',
-    requestsPerMinute: 100,
-  },
-},
-```
-
-### Hosted Key Env Var Convention
-
-Keys use a numbered naming pattern driven by a count env var:
-
-```
-YOUR_SERVICE_API_KEY_COUNT=3
-YOUR_SERVICE_API_KEY_1=sk-...
-YOUR_SERVICE_API_KEY_2=sk-...
-YOUR_SERVICE_API_KEY_3=sk-...
-```
-
-The `envKeyPrefix` value (`YOUR_SERVICE_API_KEY`) determines which env vars are read at runtime. Adding more keys only requires bumping the count and adding the new env var.
-
-### Pricing: Prefer API-Reported Cost
-
-Always prefer using cost data returned by the API (e.g., `creditsUsed`, `costDollars`). This is the most accurate because it accounts for variable pricing tiers, feature modifiers, and plan-level discounts.
-
-**When the API reports cost** — use it directly and throw if missing:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (output.creditsUsed == null) {
-      throw new Error('Response missing creditsUsed field')
-    }
-    // $0.001 per credit — from https://example.com/pricing
-    const cost = (output.creditsUsed as number) * 0.001
-    return { cost, metadata: { creditsUsed: output.creditsUsed } }
-  },
-},
-```
-
-**When the API does NOT report cost** — compute it from params/output based on the pricing docs, but still validate the data you depend on:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (!Array.isArray(output.searchResults)) {
-      throw new Error('Response missing searchResults, cannot determine cost')
-    }
-    // Serper: 1 credit for <=10 results, 2 credits for >10 — from https://serper.dev/pricing
-    const credits = Number(params.num) > 10 ? 2 : 1
-    return { cost: credits * 0.001, metadata: { credits } }
-  },
-},
-```
-
-**`getCost` must always throw** if it cannot determine cost. Never silently fall back to a default — this would hide billing inaccuracies.
-
-### Capturing Cost Data from the API
-
-If the API returns cost info, capture it in `transformResponse` so `getCost` can read it from the output:
-
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      results: data.results,
-      creditsUsed: data.creditsUsed,  // pass through for getCost
-    },
-  }
-},
-```
-
-For async/polling tools, capture it in `postProcess` when the job completes:
-
-```typescript
-if (jobData.status === 'completed') {
-  result.output = {
-    data: jobData.data,
-    creditsUsed: jobData.creditsUsed,
-  }
-}
-```
-
-## Step 4: Hide the API Key Field When Hosted
-
-In the block config (`blocks/blocks/{service}.ts`), add `hideWhenHosted: true` to the API key subblock. This hides the field on hosted Sim since the platform provides the key:
-
-```typescript
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-},
-```
-
-The visibility is controlled by `isSubBlockHidden()` in `lib/workflows/subblocks/visibility.ts`, which checks both the `isHosted` feature flag (`hideWhenHosted`) and optional env var conditions (`hideWhenEnvSet`).
-
-### Excluding Specific Operations from Hosted Key Support
-
-When a block has multiple operations but some operations should **not** use a hosted key (e.g., the underlying API is deprecated, unsupported, or too expensive), use the **duplicate apiKey subblock** pattern. This is the same pattern Exa uses for its `research` operation:
-
-1. **Remove the `hosting` config** from the tool definition for that operation — it must not have a `hosting` object at all.
-2. **Duplicate the `apiKey` subblock** in the block config with opposing conditions:
-
-```typescript
-// API Key — hidden when hosted for operations with hosted key support
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-  condition: { field: 'operation', value: 'unsupported_op', not: true },
-},
-// API Key — always visible for unsupported_op (no hosted key support)
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  condition: { field: 'operation', value: 'unsupported_op' },
-},
-```
-
-Both subblocks share the same `id: 'apiKey'`, so the same value flows to the tool. The conditions ensure only one is visible at a time. The first has `hideWhenHosted: true` and shows for all hosted operations; the second has no `hideWhenHosted` and shows only for the excluded operation — meaning users must always provide their own key for that operation.
-
-To exclude multiple operations, use an array: `{ field: 'operation', value: ['op_a', 'op_b'] }`.
-
-**Reference implementations:**
-- **Exa** (`blocks/blocks/exa.ts`): `research` operation excluded from hosting — lines 309-329
-- **Google Maps** (`blocks/blocks/google_maps.ts`): `speed_limits` operation excluded from hosting (deprecated Roads API)
-
-## Step 5: Add to the BYOK Settings UI
-
-Add an entry to the `PROVIDERS` array in the BYOK settings component so users can bring their own key. You need the service icon from `components/icons.tsx`:
-
-```typescript
-{
-  id: 'your_service',
-  name: 'Your Service',
-  icon: YourServiceIcon,
-  description: 'What this service does',
-  placeholder: 'Enter your API key',
-},
-```
-
-## Step 6: Summarize Pricing and Throttling Comparison
-
-After all code changes are complete, output a detailed summary to the user covering:
-
-### What to include
-
-1. **API's pricing model** — how the service charges (per token, per credit, per request, etc.), the specific rates found in docs, and whether the API reports cost in responses.
-2. **Our `getCost` approach** — how we calculate cost, what fields we depend on, and any assumptions or estimates (especially when the API doesn't report exact dollar cost).
-3. **API's rate limits** — the documented limits (RPM, TPM, concurrent, etc.), which plan tier they apply to, and whether they're per-key or per-account.
-4. **Our `rateLimit` config** — what we set for `requestsPerMinute` (and dimensions if custom mode), why we chose those values, and how they compare to the API's limits.
-5. **Key pooling impact** — how many hosted keys we expect, and how round-robin distribution affects the effective per-key rate at the API.
-6. **Gaps or risks** — anything the API charges for that we don't meter, rate limit dimensions we chose not to enforce, or pricing that may be inaccurate due to variable model/tier costs.
-
-### Format
-
-Present this as a structured summary with clear headings. Example:
-
-```
-### Pricing
-- **API charges**: $X per 1M tokens (input), $Y per 1M tokens (output) — varies by model
-- **Response reports cost?**: No — only token counts in `usage` field
-- **Our getCost**: Estimates cost at $Z per 1M total tokens based on median model pricing
-- **Risk**: Actual cost varies by model; our estimate may over/undercharge for cheap/expensive models
-
-### Throttling
-- **API limits**: 300 RPM per key (paid tier), 60 RPM (free tier)
-- **Per-key or per-account**: Per key — more keys = more throughput
-- **Our config**: 60 RPM per workspace (per_request mode)
-- **With N keys**: Effective per-key rate is (total RPM across workspaces) / N
-- **Headroom**: Comfortable — even 10 active workspaces at full rate = 600 RPM / 3 keys = 200 RPM per key, under the 300 RPM API limit
-```
-
-This summary helps reviewers verify that the pricing and rate limiting are well-calibrated and surfaces any risks that need monitoring.
-
-## Checklist
-
-- [ ] Provider added to `BYOKProviderId` in `tools/types.ts`
-- [ ] Provider added to `VALID_PROVIDERS` in the BYOK keys API route
-- [ ] API pricing docs researched — understand per-unit cost and whether the API reports cost in responses
-- [ ] API rate limits researched — understand RPM/TPM limits, per-key vs per-account, and plan tiers
-- [ ] `hosting` config added to the tool with `envKeyPrefix`, `apiKeyParam`, `byokProviderId`, `pricing`, and `rateLimit`
-- [ ] `getCost` throws if required cost data is missing from the response
-- [ ] Cost data captured in `transformResponse` or `postProcess` if API provides it
-- [ ] `hideWhenHosted: true` added to the API key subblock in the block config
-- [ ] Provider entry added to the BYOK settings UI with icon and description
-- [ ] Env vars documented: `{PREFIX}_COUNT` and `{PREFIX}_1..N`
-- [ ] Pricing and throttling summary provided to reviewer

.claude/commands/add-integration.md

@@ -1,764 +0,0 @@
----
-description: Add a complete integration to Sim (tools, block, icon, registration)
-argument-hint: <service-name> [api-docs-url]
----
-
-# Add Integration Skill
-
-You are an expert at adding complete integrations to Sim. This skill orchestrates the full process of adding a new service integration.
-
-## Overview
-
-Adding an integration involves these steps in order:
-1. **Research** - Read the service's API documentation
-2. **Create Tools** - Build tool configurations for each API operation
-3. **Create Block** - Build the block UI configuration
-4. **Add Icon** - Add the service's brand icon
-5. **Create Triggers** (optional) - If the service supports webhooks
-6. **Register** - Register tools, block, and triggers in their registries
-7. **Generate Docs** - Run the docs generation script
-
-## Step 1: Research the API
-
-Before writing any code:
-1. Use Context7 to find official documentation: `mcp__plugin_context7_context7__resolve-library-id`
-2. Or use WebFetch to read API docs directly
-3. Identify:
-   - Authentication method (OAuth, API Key, both)
-   - Available operations (CRUD, search, etc.)
-   - Required vs optional parameters
-   - Response structures
-
-## Step 2: Create Tools
-
-### Directory Structure
-```
-apps/sim/tools/{service}/
-├── index.ts          # Barrel exports
-├── types.ts          # TypeScript interfaces
-├── {action1}.ts      # Tool for action 1
-├── {action2}.ts      # Tool for action 2
-└── ...
-```
-
-### Key Patterns
-
-**types.ts:**
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-export interface {Service}{Action}Params {
-  accessToken: string      // For OAuth services
-  // OR
-  apiKey: string          // For API key services
-
-  requiredParam: string
-  optionalParam?: string
-}
-
-export interface {Service}Response extends ToolResponse {
-  output: {
-    // Define output structure
-  }
-}
-```
-
-**Tool file pattern:**
-```typescript
-export const {service}{Action}Tool: ToolConfig<Params, Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: '...',
-  version: '1.0.0',
-
-  oauth: { required: true, provider: '{service}' },  // If OAuth
-
-  params: {
-    accessToken: { type: 'string', required: true, visibility: 'hidden', description: '...' },
-    // ... other params
-  },
-
-  request: { url, method, headers, body },
-
-  transformResponse: async (response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        field: data.field ?? null,  // Always handle nullables
-      },
-    }
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Critical Rules
-- `visibility: 'hidden'` for OAuth tokens
-- `visibility: 'user-only'` for API keys and user credentials
-- `visibility: 'user-or-llm'` for operation parameters
-- Always use `?? null` for nullable API response fields
-- Always use `?? []` for optional array fields
-- Set `optional: true` for outputs that may not exist
-- Never output raw JSON dumps - extract meaningful fields
-- When using `type: 'json'` and you know the object shape, define `properties` with the inner fields so downstream consumers know the structure. Only use bare `type: 'json'` when the shape is truly dynamic
-
-## Step 3: Create Block
-
-### File Location
-`apps/sim/blocks/blocks/{service}.ts`
-
-### Block Structure
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {Service}Block: BlockConfig = {
-  type: '{service}',
-  name: '{Service}',
-  description: '...',
-  longDescription: '...',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
-  bgColor: '#HEXCOLOR',
-  icon: {Service}Icon,
-  authMode: AuthMode.OAuth,  // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Operation dropdown
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Operation 1', id: 'action1' },
-        { label: 'Operation 2', id: 'action2' },
-      ],
-      value: () => 'action1',
-    },
-    // Credential field
-    {
-      id: 'credential',
-      title: '{Service} Account',
-      type: 'oauth-input',
-      serviceId: '{service}',
-      requiredScopes: getScopesForService('{service}'),
-      required: true,
-    },
-    // Conditional fields per operation
-    // ...
-  ],
-
-  tools: {
-    access: ['{service}_action1', '{service}_action2'],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-    },
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Key SubBlock Patterns
-
-**Condition-based visibility:**
-```typescript
-{
-  id: 'resourceId',
-  title: 'Resource ID',
-  type: 'short-input',
-  condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-  required: { field: 'operation', value: ['read', 'update', 'delete'] },
-}
-```
-
-**DependsOn for cascading selectors:**
-```typescript
-{
-  id: 'project',
-  type: 'project-selector',
-  dependsOn: ['credential'],
-},
-{
-  id: 'issue',
-  type: 'file-selector',
-  dependsOn: ['credential', 'project'],
-}
-```
-
-**Basic/Advanced mode for dual UX:**
-```typescript
-// Basic: Visual selector
-{
-  id: 'channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',
-  dependsOn: ['credential'],
-},
-// Advanced: Manual input
-{
-  id: 'channelId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',
-}
-```
-
-**Critical Canonical Param Rules:**
-- `canonicalParamId` must NOT match any subblock's `id` in the block
-- `canonicalParamId` must be unique per operation/condition context
-- Only use `canonicalParamId` to link basic/advanced alternatives for the same logical parameter
-- `mode` only controls UI visibility, NOT serialization. Without `canonicalParamId`, both basic and advanced field values would be sent
-- Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions
-- **Required consistency:** If one subblock in a canonical group has `required: true`, ALL subblocks in that group must have `required: true` (prevents bypassing validation by switching modes)
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs (e.g., `fileSelector`, `manualFileId`)
-- **Params function:** Must use canonical param IDs, NOT raw subblock IDs (raw IDs are deleted after canonical transformation)
-
-## Step 4: Add Icon
-
-### File Location
-`apps/sim/components/icons.tsx`
-
-### Pattern
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg
-      {...props}
-      viewBox="0 0 24 24"
-      fill="none"
-      xmlns="http://www.w3.org/2000/svg"
-    >
-      {/* SVG paths from user-provided SVG */}
-    </svg>
-  )
-}
-```
-
-### Getting Icons
-**Do NOT search for icons yourself.** At the end of implementation, ask the user to provide the SVG:
-
-```
-I've completed the integration. Before I can add the icon, please provide the SVG for {Service}.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-Once the user provides the SVG:
-1. Extract the SVG paths/content
-2. Create a React component that spreads props
-3. Ensure viewBox is preserved from the original SVG
-
-## Step 5: Create Triggers (Optional)
-
-If the service supports webhooks, create triggers using the generic `buildTriggerSubBlocks` helper.
-
-### Directory Structure
-```
-apps/sim/triggers/{service}/
-├── index.ts      # Barrel exports
-├── utils.ts      # Trigger options, setup instructions, extra fields
-├── {event_a}.ts  # Primary trigger (includes dropdown)
-├── {event_b}.ts  # Secondary triggers (no dropdown)
-└── webhook.ts    # Generic webhook (optional)
-```
-
-### Key Pattern
-
-```typescript
-import { buildTriggerSubBlocks } from '@/triggers'
-import { {service}TriggerOptions, {service}SetupInstructions, build{Service}ExtraFields } from './utils'
-
-// Primary trigger - includeDropdown: true
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,  // Only for primary trigger!
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  // ...
-}
-
-// Secondary triggers - no dropdown
-export const {service}EventBTrigger: TriggerConfig = {
-  id: '{service}_event_b',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_b',
-    triggerOptions: {service}TriggerOptions,
-    // No includeDropdown!
-    setupInstructions: {service}SetupInstructions('Event B'),
-    extraFields: build{Service}ExtraFields('{service}_event_b'),
-  }),
-  // ...
-}
-```
-
-### Connect to Block
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-  subBlocks: [
-    // Tool fields...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-}
-```
-
-See `/add-trigger` skill for complete documentation.
-
-## Step 6: Register Everything
-
-### Tools Registry (`apps/sim/tools/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}Action1Tool,
-  {service}Action2Tool,
-} from '@/tools/{service}'
-
-// Add to tools object (alphabetically)
-export const tools: Record<string, ToolConfig> = {
-  // ... existing tools ...
-  {service}_action1: {service}Action1Tool,
-  {service}_action2: {service}Action2Tool,
-}
-```
-
-### Block Registry (`apps/sim/blocks/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import { {Service}Block } from '@/blocks/blocks/{service}'
-
-// Add to registry (alphabetically)
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  {service}: {Service}Block,
-}
-```
-
-### Trigger Registry (`apps/sim/triggers/registry.ts`) - If triggers exist
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}EventATrigger,
-  {service}EventBTrigger,
-  {service}WebhookTrigger,
-} from '@/triggers/{service}'
-
-// Add to TRIGGER_REGISTRY (alphabetically)
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing triggers ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-  {service}_webhook: {service}WebhookTrigger,
-}
-```
-
-## Step 7: Generate Docs
-
-Run the documentation generator:
-```bash
-bun run scripts/generate-docs.ts
-```
-
-This creates `apps/docs/content/docs/en/tools/{service}.mdx`
-
-## V2 Integration Pattern
-
-If creating V2 versions (API-aligned outputs):
-
-1. **V2 Tools** - Add `_v2` suffix, version `2.0.0`, flat outputs
-2. **V2 Block** - Add `_v2` type, use `createVersionedToolSelector`
-3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`
-4. **Registry** - Register both versions
-
-```typescript
-// In registry
-{service}: {Service}Block,        // V1 (legacy, hidden)
-{service}_v2: {Service}V2Block,   // V2 (visible)
-```
-
-## Complete Checklist
-
-### Tools
-- [ ] Created `tools/{service}/` directory
-- [ ] Created `types.ts` with all interfaces
-- [ ] Created tool file for each operation
-- [ ] All params have correct visibility
-- [ ] All nullable fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all tools in `tools/registry.ts`
-
-### Block
-- [ ] Created `blocks/blocks/{service}.ts`
-- [ ] Set `integrationType` to the correct `IntegrationType` enum value
-- [ ] Set `tags` array with all applicable `IntegrationTag` values
-- [ ] Defined operation dropdown with all operations
-- [ ] Added credential field with `requiredScopes: getScopesForService('{service}')`
-- [ ] Added conditional fields per operation
-- [ ] Set up dependsOn for cascading selectors
-- [ ] Configured tools.access with all tool IDs
-- [ ] Configured tools.config.tool selector
-- [ ] Defined outputs matching tool outputs
-- [ ] Registered block in `blocks/registry.ts`
-- [ ] If triggers: set `triggers.enabled` and `triggers.available`
-- [ ] If triggers: spread trigger subBlocks with `getTrigger()`
-
-### OAuth Scopes (if OAuth service)
-- [ ] Defined scopes in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS`
-- [ ] Added scope descriptions in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] Used `getCanonicalScopesForProvider()` in `auth.ts` (never hardcode)
-- [ ] Used `getScopesForService()` in block `requiredScopes` (never hardcode)
-
-### Icon
-- [ ] Asked user to provide SVG
-- [ ] Added icon to `components/icons.tsx`
-- [ ] Icon spreads props correctly
-
-### Triggers (if service supports webhooks)
-- [ ] Created `triggers/{service}/` directory
-- [ ] Created `utils.ts` with options, instructions, and extra fields helpers
-- [ ] Primary trigger uses `includeDropdown: true`
-- [ ] Secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all triggers in `triggers/registry.ts`
-
-### Docs
-- [ ] Ran `bun run scripts/generate-docs.ts`
-- [ ] Verified docs file created
-
-### Final Validation (Required)
-- [ ] Read every tool file and cross-referenced inputs/outputs against the API docs
-- [ ] Verified block subBlocks cover all required tool params with correct conditions
-- [ ] Verified block outputs match what the tools actually return
-- [ ] Verified `tools.config.params` correctly maps and coerces all param types
-
-## Example Command
-
-When the user asks to add an integration:
-
-```
-User: Add a Stripe integration
-
-You: I'll add the Stripe integration. Let me:
-
-1. First, research the Stripe API using Context7
-2. Create the tools for key operations (payments, subscriptions, etc.)
-3. Create the block with operation dropdown
-4. Register everything
-5. Generate docs
-6. Ask you for the Stripe icon SVG
-
-[Proceed with implementation...]
-
-[After completing steps 1-5...]
-
-I've completed the Stripe integration. Before I can add the icon, please provide the SVG for Stripe.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-## File Handling
-
-When your integration handles file uploads or downloads, follow these patterns to work with `UserFile` objects consistently.
-
-### What is a UserFile?
-
-A `UserFile` is the standard file representation in Sim:
-
-```typescript
-interface UserFile {
-  id: string       // Unique identifier
-  name: string     // Original filename
-  url: string      // Presigned URL for download
-  size: number     // File size in bytes
-  type: string     // MIME type (e.g., 'application/pdf')
-  base64?: string  // Optional base64 content (if small file)
-  key?: string     // Internal storage key
-  context?: object // Storage context metadata
-}
-```
-
-### File Input Pattern (Uploads)
-
-For tools that accept file uploads, **always route through an internal API endpoint** rather than calling external APIs directly. This ensures proper file content retrieval.
-
-#### 1. Block SubBlocks for File Input
-
-Use the basic/advanced mode pattern:
-
-```typescript
-// Basic mode: File upload UI
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Maps to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from previous block
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Same canonical param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical:** `canonicalParamId` must NOT match any subblock `id`.
-
-#### 2. Normalize File Input in Block Config
-
-In `tools.config.tool`, use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  config: {
-    tool: (params) => {
-      // Normalize file from basic (uploadFile), advanced (fileRef), or legacy (fileContent)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `{service}_${params.operation}`
-    },
-  },
-}
-```
-
-#### 3. Create Internal API Route
-
-Create `apps/sim/app/api/tools/{service}/{action}/route.ts`:
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { NextResponse, type NextRequest } from 'next/server'
-import { z } from 'zod'
-import { checkInternalAuth } from '@/lib/auth/hybrid'
-import { generateRequestId } from '@/lib/core/utils/request'
-import { FileInputSchema, type RawFileInput } from '@/lib/uploads/utils/file-schemas'
-import { processFilesToUserFiles } from '@/lib/uploads/utils/file-utils'
-import { downloadFileFromStorage } from '@/lib/uploads/utils/file-utils.server'
-
-const logger = createLogger('{Service}UploadAPI')
-
-const RequestSchema = z.object({
-  accessToken: z.string(),
-  file: FileInputSchema.optional().nullable(),
-  // Legacy field for backwards compatibility
-  fileContent: z.string().optional().nullable(),
-  // ... other params
-})
-
-export async function POST(request: NextRequest) {
-  const requestId = generateRequestId()
-
-  const authResult = await checkInternalAuth(request, { requireWorkflowId: false })
-  if (!authResult.success) {
-    return NextResponse.json({ success: false, error: 'Unauthorized' }, { status: 401 })
-  }
-
-  const body = await request.json()
-  const data = RequestSchema.parse(body)
-
-  let fileBuffer: Buffer
-  let fileName: string
-
-  // Prefer UserFile input, fall back to legacy base64
-  if (data.file) {
-    const userFiles = processFilesToUserFiles([data.file as RawFileInput], requestId, logger)
-    if (userFiles.length === 0) {
-      return NextResponse.json({ success: false, error: 'Invalid file' }, { status: 400 })
-    }
-    const userFile = userFiles[0]
-    fileBuffer = await downloadFileFromStorage(userFile, requestId, logger)
-    fileName = userFile.name
-  } else if (data.fileContent) {
-    // Legacy: base64 string (backwards compatibility)
-    fileBuffer = Buffer.from(data.fileContent, 'base64')
-    fileName = 'file'
-  } else {
-    return NextResponse.json({ success: false, error: 'File required' }, { status: 400 })
-  }
-
-  // Now call external API with fileBuffer
-  const response = await fetch('https://api.{service}.com/upload', {
-    method: 'POST',
-    headers: { Authorization: `Bearer ${data.accessToken}` },
-    body: new Uint8Array(fileBuffer),  // Convert Buffer for fetch
-  })
-
-  // ... handle response
-}
-```
-
-#### 4. Update Tool to Use Internal Route
-
-```typescript
-export const {service}UploadTool: ToolConfig<Params, Response> = {
-  id: '{service}_upload',
-  // ...
-  params: {
-    file: { type: 'file', required: false, visibility: 'user-or-llm' },
-    fileContent: { type: 'string', required: false, visibility: 'hidden' }, // Legacy
-  },
-  request: {
-    url: '/api/tools/{service}/upload',  // Internal route
-    method: 'POST',
-    body: (params) => ({
-      accessToken: params.accessToken,
-      file: params.file,
-      fileContent: params.fileContent,
-    }),
-  },
-}
-```
-
-### File Output Pattern (Downloads)
-
-For tools that return files, use `FileToolProcessor` to store files and return `UserFile` objects.
-
-#### In Tool transformResponse
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-transformResponse: async (response, context) => {
-  const data = await response.json()
-
-  // Process file outputs to UserFile objects
-  const fileProcessor = new FileToolProcessor(context)
-  const file = await fileProcessor.processFileData({
-    data: data.content,      // base64 or buffer
-    mimeType: data.mimeType,
-    filename: data.filename,
-  })
-
-  return {
-    success: true,
-    output: { file },
-  }
-}
-```
-
-#### In API Route (for complex file handling)
-
-```typescript
-// Return file data that FileToolProcessor can handle
-return NextResponse.json({
-  success: true,
-  output: {
-    file: {
-      data: base64Content,
-      mimeType: 'application/pdf',
-      filename: 'document.pdf',
-    },
-  },
-})
-```
-
-### Key Helpers Reference
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get file Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-| `isUserFile` | `@/lib/core/utils/user-file` | Type guard for UserFile objects |
-| `FileInputSchema` | `@/lib/uploads/utils/file-schemas` | Zod schema for file validation |
-
-### Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. Examples: pagination tokens, time range filters, sort order, max results, reply settings.
-
-### WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually:
-- **Timestamps**: Use `generationType: 'timestamp'` to inject current date context into the AI prompt
-- **JSON arrays**: Use `generationType: 'json-object'` for structured data
-- **Complex queries**: Use a descriptive prompt explaining the expected format
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-```
-
-### OAuth Scopes (Centralized System)
-
-Scopes are maintained in a single source of truth and reused everywhere:
-
-1. **Define scopes** in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-2. **Add descriptions** in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for the OAuth modal UI
-3. **Reference in auth.ts** using `getCanonicalScopesForProvider(providerId)` from `@/lib/oauth/utils`
-4. **Reference in blocks** using `getScopesForService(serviceId)` from `@/lib/oauth/utils`
-
-**Never hardcode scope arrays** in `auth.ts` or block `requiredScopes`. Always import from the centralized source.
-
-```typescript
-// In auth.ts (Better Auth config)
-scopes: getCanonicalScopesForProvider('{service}'),
-
-// In block credential sub-block
-requiredScopes: getScopesForService('{service}'),
-```
-
-### Common Gotchas
-
-1. **OAuth serviceId must match** - The `serviceId` in oauth-input must match the OAuth provider configuration
-2. **All tool IDs MUST be snake_case** - `stripe_create_payment`, not `stripeCreatePayment`. This applies to tool `id` fields, registry keys, `tools.access` arrays, and `tools.config.tool` return values
-3. **Block type is snake_case** - `type: 'stripe'`, not `type: 'Stripe'`
-4. **Alphabetical ordering** - Keep imports and registry entries alphabetically sorted
-5. **Required can be conditional** - Use `required: { field: 'op', value: 'create' }` instead of always true
-6. **DependsOn clears options** - When a dependency changes, selector options are refetched
-7. **Never pass Buffer directly to fetch** - Convert to `new Uint8Array(buffer)` for TypeScript compatibility
-8. **Always handle legacy file params** - Keep hidden `fileContent` params for backwards compatibility
-9. **Optional fields use advanced mode** - Set `mode: 'advanced'` on rarely-used optional fields
-10. **Complex inputs need wandConfig** - Timestamps, JSON arrays, and other hard-to-type values should have `wandConfig` enabled
-11. **Never hardcode scopes** - Use `getScopesForService()` in blocks and `getCanonicalScopesForProvider()` in auth.ts
-12. **Always add scope descriptions** - New scopes must have entries in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`

.claude/commands/add-tools.md

@@ -1,321 +0,0 @@
----
-description: Create tool configurations for a Sim integration by reading API docs
-argument-hint: <service-name> [api-docs-url]
----
-
-# Add Tools Skill
-
-You are an expert at creating tool configurations for Sim integrations. Your job is to read API documentation and create properly structured tool files.
-
-## Your Task
-
-When the user asks you to create tools for a service:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Create the tools directory structure
-3. Generate properly typed tool configurations
-
-## Directory Structure
-
-Create files in `apps/sim/tools/{service}/`:
-```
-tools/{service}/
-├── index.ts      # Barrel export
-├── types.ts      # Parameter & response types
-└── {action}.ts   # Individual tool files (one per operation)
-```
-
-## Tool Configuration Structure
-
-Every tool MUST follow this exact structure:
-
-```typescript
-import type { {ServiceName}{Action}Params } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-interface {ServiceName}{Action}Response {
-  success: boolean
-  output: {
-    // Define output structure here
-  }
-}
-
-export const {serviceName}{Action}Tool: ToolConfig<
-  {ServiceName}{Action}Params,
-  {ServiceName}{Action}Response
-> = {
-  id: '{service}_{action}',           // snake_case, matches tool name
-  name: '{Service} {Action}',         // Human readable
-  description: 'Brief description',   // One sentence
-  version: '1.0.0',
-
-  // OAuth config (if service uses OAuth)
-  oauth: {
-    required: true,
-    provider: '{service}',            // Must match OAuth provider ID
-  },
-
-  params: {
-    // Hidden params (system-injected, only use hidden for oauth accessToken)
-    accessToken: {
-      type: 'string',
-      required: true,
-      visibility: 'hidden',
-      description: 'OAuth access token',
-    },
-    // User-only params (credentials, api key, IDs user must provide)
-    someId: {
-      type: 'string',
-      required: true,
-      visibility: 'user-only',
-      description: 'The ID of the resource',
-    },
-    // User-or-LLM params (everything else, can be provided by user OR computed by LLM)
-    query: {
-      type: 'string',
-      required: false,                // Use false for optional
-      visibility: 'user-or-llm',
-      description: 'Search query',
-    },
-  },
-
-  request: {
-    url: (params) => `https://api.service.com/v1/resource/${params.id}`,
-    method: 'POST',
-    headers: (params) => ({
-      Authorization: `Bearer ${params.accessToken}`,
-      'Content-Type': 'application/json',
-    }),
-    body: (params) => ({
-      // Request body - only for POST/PUT/PATCH
-      // Trim ID fields to prevent copy-paste whitespace errors:
-      // userId: params.userId?.trim(),
-    }),
-  },
-
-  transformResponse: async (response: Response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        // Map API response to output
-        // Use ?? null for nullable fields
-        // Use ?? [] for optional arrays
-      },
-    }
-  },
-
-  outputs: {
-    // Define each output field
-  },
-}
-```
-
-## Critical Rules for Parameters
-
-### Visibility Options
-- `'hidden'` - System-injected (OAuth tokens, internal params). User never sees.
-- `'user-only'` - User must provide (credentials, api keys, account-specific IDs)
-- `'user-or-llm'` - User provides OR LLM can compute (search queries, content, filters, most fall into this category)
-
-### Parameter Types
-- `'string'` - Text values
-- `'number'` - Numeric values
-- `'boolean'` - True/false
-- `'json'` - Complex objects (NOT 'object', use 'json')
-- `'file'` - Single file
-- `'file[]'` - Multiple files
-
-### Required vs Optional
-- Always explicitly set `required: true` or `required: false`
-- Optional params should have `required: false`
-
-## Critical Rules for Outputs
-
-### Output Types
-- `'string'`, `'number'`, `'boolean'` - Primitives
-- `'json'` - Complex objects (use this, NOT 'object')
-- `'array'` - Arrays with `items` property
-- `'object'` - Objects with `properties` property
-
-### Optional Outputs
-Add `optional: true` for fields that may not exist in the response:
-```typescript
-closedAt: {
-  type: 'string',
-  description: 'When the issue was closed',
-  optional: true,
-},
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **always define the inner structure** using `properties` so downstream consumers know what fields are available:
-
-```typescript
-// BAD: Opaque json with no info about what's inside
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-},
-
-// GOOD: Define the known properties
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-  properties: {
-    id: { type: 'string', description: 'Unique ID' },
-    status: { type: 'string', description: 'Current status' },
-    count: { type: 'number', description: 'Total count' },
-  },
-},
-```
-
-For arrays of objects, define the item structure:
-```typescript
-items: {
-  type: 'array',
-  description: 'List of items',
-  items: {
-    type: 'object',
-    properties: {
-      id: { type: 'string', description: 'Item ID' },
-      name: { type: 'string', description: 'Item name' },
-    },
-  },
-},
-```
-
-Only use bare `type: 'json'` without `properties` when the shape is truly dynamic or unknown.
-
-## Critical Rules for transformResponse
-
-### Handle Nullable Fields
-ALWAYS use `?? null` for fields that may be undefined:
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      id: data.id,
-      title: data.title,
-      body: data.body ?? null,           // May be undefined
-      assignee: data.assignee ?? null,   // May be undefined
-      labels: data.labels ?? [],         // Default to empty array
-      closedAt: data.closed_at ?? null,  // May be undefined
-    },
-  }
-}
-```
-
-### Never Output Raw JSON Dumps
-DON'T do this:
-```typescript
-output: {
-  data: data,  // BAD - raw JSON dump
-}
-```
-
-DO this instead - extract meaningful fields:
-```typescript
-output: {
-  id: data.id,
-  name: data.name,
-  status: data.status,
-  metadata: {
-    createdAt: data.created_at,
-    updatedAt: data.updated_at,
-  },
-}
-```
-
-## Types File Pattern
-
-Create `types.ts` with interfaces for all params and responses:
-
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-// Parameter interfaces
-export interface {Service}{Action}Params {
-  accessToken: string
-  requiredField: string
-  optionalField?: string
-}
-
-// Response interfaces (extend ToolResponse)
-export interface {Service}{Action}Response extends ToolResponse {
-  output: {
-    field1: string
-    field2: number
-    optionalField?: string | null
-  }
-}
-```
-
-## Index.ts Barrel Export Pattern
-
-```typescript
-// Export all tools
-export { serviceTool1 } from './{action1}'
-export { serviceTool2 } from './{action2}'
-
-// Export types
-export * from './types'
-```
-
-## Registering Tools
-
-After creating tools, remind the user to:
-1. Import tools in `apps/sim/tools/registry.ts`
-2. Add to the `tools` object with snake_case keys:
-```typescript
-import { serviceActionTool } from '@/tools/{service}'
-
-export const tools = {
-  // ... existing tools ...
-  {service}_{action}: serviceActionTool,
-}
-```
-
-## V2 Tool Pattern
-
-If creating V2 tools (API-aligned outputs), use `_v2` suffix:
-- Tool ID: `{service}_{action}_v2`
-- Variable name: `{action}V2Tool`
-- Version: `'2.0.0'`
-- Outputs: Flat, API-aligned (no content/metadata wrapper)
-
-## Naming Convention
-
-All tool IDs MUST use `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase for tool IDs.
-
-## Checklist Before Finishing
-
-- [ ] All tool IDs use snake_case
-- [ ] All params have explicit `required: true` or `required: false`
-- [ ] All params have appropriate `visibility`
-- [ ] All nullable response fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] No raw JSON dumps in outputs
-- [ ] Types file has all interfaces
-- [ ] Index.ts exports all tools
-
-## Final Validation (Required)
-
-After creating all tools, you MUST validate every tool before finishing:
-
-1. **Read every tool file** you created — do not skip any
-2. **Cross-reference with the API docs** to verify:
-   - All required params are marked `required: true`
-   - All optional params are marked `required: false`
-   - Param types match the API (string, number, boolean, json)
-   - Request URL, method, headers, and body match the API spec
-   - `transformResponse` extracts the correct fields from the API response
-   - All output fields match what the API actually returns
-   - No fields are missing from outputs that the API provides
-   - No extra fields are defined in outputs that the API doesn't return
-3. **Verify consistency** across tools:
-   - Shared types in `types.ts` match all tools that use them
-   - Tool IDs in the barrel export match the tool file definitions
-   - Error handling is consistent (error checks, meaningful messages)

.claude/commands/add-trigger.md

@@ -1,497 +0,0 @@
----
-description: Create webhook or polling triggers for a Sim integration
-argument-hint: <service-name>
----
-
-# Add Trigger
-
-You are an expert at creating webhook and polling triggers for Sim. You understand the trigger system, the generic `buildTriggerSubBlocks` helper, polling infrastructure, and how triggers connect to blocks.
-
-## Your Task
-
-1. Research what webhook events the service supports — if the service lacks reliable webhooks, use polling
-2. Create the trigger files using the generic builder (webhook) or manual config (polling)
-3. Create a provider handler (webhook) or polling handler (polling)
-4. Register triggers and connect them to the block
-
-## Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel exports
-├── utils.ts              # Service-specific helpers (options, instructions, extra fields, outputs)
-├── {event_a}.ts          # Primary trigger (includes dropdown)
-├── {event_b}.ts          # Secondary trigger (no dropdown)
-└── webhook.ts            # Generic webhook trigger (optional, for "all events")
-
-apps/sim/lib/webhooks/
-├── provider-subscription-utils.ts  # Shared subscription helpers (getProviderConfig, getNotificationUrl)
-├── providers/
-│   ├── {service}.ts       # Provider handler (auth, formatInput, matchEvent, subscriptions)
-│   ├── types.ts           # WebhookProviderHandler interface
-│   ├── utils.ts           # Shared helpers (createHmacVerifier, verifyTokenAuth, skipByEventTypes)
-│   └── registry.ts        # Handler map + default handler
-```
-
-## Step 1: Create `utils.ts`
-
-This file contains all service-specific helpers used by triggers.
-
-```typescript
-import type { SubBlockConfig } from '@/blocks/types'
-import type { TriggerOutput } from '@/triggers/types'
-
-export const {service}TriggerOptions = [
-  { label: 'Event A', id: '{service}_event_a' },
-  { label: 'Event B', id: '{service}_event_b' },
-]
-
-export function {service}SetupInstructions(eventType: string): string {
-  const instructions = [
-    'Copy the <strong>Webhook URL</strong> above',
-    'Go to <strong>{Service} Settings > Webhooks</strong>',
-    `Select the <strong>${eventType}</strong> event type`,
-    'Paste the webhook URL and save',
-    'Click "Save" above to activate your trigger',
-  ]
-  return instructions
-    .map((instruction, index) =>
-      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
-    )
-    .join('')
-}
-
-export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
-  return [
-    {
-      id: 'projectId',
-      title: 'Project ID (Optional)',
-      type: 'short-input',
-      placeholder: 'Leave empty for all projects',
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-  ]
-}
-
-export function build{Service}Outputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'The type of event' },
-    resourceId: { type: 'string', description: 'ID of the affected resource' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Step 2: Create Trigger Files
-
-**Primary trigger** — MUST include `includeDropdown: true`:
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { buildTriggerSubBlocks } from '@/triggers'
-import { build{Service}ExtraFields, build{Service}Outputs, {service}SetupInstructions, {service}TriggerOptions } from '@/triggers/{service}/utils'
-import type { TriggerConfig } from '@/triggers/types'
-
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  name: '{Service} Event A',
-  provider: '{service}',
-  description: 'Trigger workflow when Event A occurs',
-  version: '1.0.0',
-  icon: {Service}Icon,
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  outputs: build{Service}Outputs(),
-  webhook: { method: 'POST', headers: { 'Content-Type': 'application/json' } },
-}
-```
-
-**Secondary triggers** — NO `includeDropdown` (it's already in the primary):
-
-```typescript
-export const {service}EventBTrigger: TriggerConfig = {
-  // Same as above but: id: '{service}_event_b', no includeDropdown
-}
-```
-
-## Step 3: Register and Wire
-
-### `apps/sim/triggers/{service}/index.ts`
-
-```typescript
-export { {service}EventATrigger } from './event_a'
-export { {service}EventBTrigger } from './event_b'
-```
-
-### `apps/sim/triggers/registry.ts`
-
-```typescript
-import { {service}EventATrigger, {service}EventBTrigger } from '@/triggers/{service}'
-
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-}
-```
-
-### Block file (`apps/sim/blocks/blocks/{service}.ts`)
-
-Wire triggers into the block so the trigger UI appears and `generate-docs.ts` discovers them. Two changes are needed:
-
-1. **Spread trigger subBlocks** at the end of the block's `subBlocks` array
-2. **Add `triggers` property** after `outputs` with `enabled: true` and `available: [...]`
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  // ...
-  subBlocks: [
-    // Regular tool subBlocks first...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-  // ... tools, inputs, outputs ...
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-}
-```
-
-**Versioned blocks (V1 + V2):** Many integrations have a hidden V1 block and a visible V2 block. Where you add the trigger wiring depends on how V2 inherits from V1:
-
-- **V2 uses `...V1Block` spread** (e.g., Google Calendar): Add trigger to V1 — V2 inherits both `subBlocks` and `triggers` automatically.
-- **V2 defines its own `subBlocks`** (e.g., Google Sheets): Add trigger to V2 (the visible block). V1 is hidden and doesn't need it.
-- **Single block, no V2** (e.g., Google Drive): Add trigger directly.
-
-`generate-docs.ts` deduplicates by base type (first match wins). If V1 is processed first without triggers, the V2 triggers won't appear in `integrations.json`. Always verify by checking the output after running the script.
-
-## Provider Handler
-
-All provider-specific webhook logic lives in a single handler file: `apps/sim/lib/webhooks/providers/{service}.ts`.
-
-### When to Create a Handler
-
-| Behavior | Method | Examples |
-|---|---|---|
-| HMAC signature auth | `verifyAuth` via `createHmacVerifier` | Ashby, Jira, Linear, Typeform |
-| Custom token auth | `verifyAuth` via `verifyTokenAuth` | Generic, Google Forms |
-| Event filtering | `matchEvent` | GitHub, Jira, Attio, HubSpot |
-| Idempotency dedup | `extractIdempotencyId` | Slack, Stripe, Linear, Jira |
-| Custom input formatting | `formatInput` | Slack, Teams, Attio, Ashby |
-| Auto webhook creation | `createSubscription` | Ashby, Grain, Calendly, Airtable |
-| Auto webhook deletion | `deleteSubscription` | Ashby, Grain, Calendly, Airtable |
-| Challenge/verification | `handleChallenge` | Slack, WhatsApp, Teams |
-| Custom success response | `formatSuccessResponse` | Slack, Twilio Voice, Teams |
-
-If none apply, you don't need a handler. The default handler provides bearer token auth.
-
-### Example Handler
-
-```typescript
-import crypto from 'crypto'
-import { createLogger } from '@sim/logger'
-import { safeCompare } from '@/lib/core/security/encryption'
-import type { EventMatchContext, FormatInputContext, FormatInputResult, WebhookProviderHandler } from '@/lib/webhooks/providers/types'
-import { createHmacVerifier } from '@/lib/webhooks/providers/utils'
-
-const logger = createLogger('WebhookProvider:{Service}')
-
-function validate{Service}Signature(secret: string, signature: string, body: string): boolean {
-  if (!secret || !signature || !body) return false
-  const computed = crypto.createHmac('sha256', secret).update(body, 'utf8').digest('hex')
-  return safeCompare(computed, signature)
-}
-
-export const {service}Handler: WebhookProviderHandler = {
-  verifyAuth: createHmacVerifier({
-    configKey: 'webhookSecret',
-    headerName: 'X-{Service}-Signature',
-    validateFn: validate{Service}Signature,
-    providerLabel: '{Service}',
-  }),
-
-  async matchEvent({ body, requestId, providerConfig }: EventMatchContext) {
-    const triggerId = providerConfig.triggerId as string | undefined
-    if (triggerId && triggerId !== '{service}_webhook') {
-      const { is{Service}EventMatch } = await import('@/triggers/{service}/utils')
-      if (!is{Service}EventMatch(triggerId, body as Record<string, unknown>)) return false
-    }
-    return true
-  },
-
-  async formatInput({ body }: FormatInputContext): Promise<FormatInputResult> {
-    const b = body as Record<string, unknown>
-    return {
-      input: {
-        eventType: b.type,
-        resourceId: (b.data as Record<string, unknown>)?.id || '',
-        resource: b.data,
-      },
-    }
-  },
-
-  extractIdempotencyId(body: unknown) {
-    const obj = body as Record<string, unknown>
-    return obj.id && obj.type ? `${obj.type}:${obj.id}` : null
-  },
-}
-```
-
-### Register the Handler
-
-In `apps/sim/lib/webhooks/providers/registry.ts`:
-
-```typescript
-import { {service}Handler } from '@/lib/webhooks/providers/{service}'
-
-const PROVIDER_HANDLERS: Record<string, WebhookProviderHandler> = {
-  // ... existing (alphabetical) ...
-  {service}: {service}Handler,
-}
-```
-
-## Output Alignment (Critical)
-
-There are two sources of truth that **MUST be aligned**:
-
-1. **Trigger `outputs`** — schema defining what fields SHOULD be available (UI tag dropdown)
-2. **`formatInput` on the handler** — implementation that transforms raw payload into actual data
-
-If they differ: the tag dropdown shows fields that don't exist, or actual data has fields users can't discover.
-
-**Rules for `formatInput`:**
-- Return `{ input: { ... } }` where inner keys match trigger `outputs` exactly
-- Return `{ input: ..., skip: { message: '...' } }` to skip execution
-- No wrapper objects or duplication
-- Use `null` for missing optional data
-
-## Automatic Webhook Registration
-
-If the service API supports programmatic webhook creation, implement `createSubscription` and `deleteSubscription` on the handler. The orchestration layer calls these automatically — **no code touches `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`**.
-
-```typescript
-import { getNotificationUrl, getProviderConfig } from '@/lib/webhooks/provider-subscription-utils'
-import type { DeleteSubscriptionContext, SubscriptionContext, SubscriptionResult } from '@/lib/webhooks/providers/types'
-
-export const {service}Handler: WebhookProviderHandler = {
-  async createSubscription(ctx: SubscriptionContext): Promise<SubscriptionResult | undefined> {
-    const config = getProviderConfig(ctx.webhook)
-    const apiKey = config.apiKey as string
-    if (!apiKey) throw new Error('{Service} API Key is required.')
-
-    const res = await fetch('https://api.{service}.com/webhooks', {
-      method: 'POST',
-      headers: { Authorization: `Bearer ${apiKey}`, 'Content-Type': 'application/json' },
-      body: JSON.stringify({ url: getNotificationUrl(ctx.webhook) }),
-    })
-
-    if (!res.ok) throw new Error(`{Service} error: ${res.status}`)
-    const { id } = (await res.json()) as { id: string }
-    return { providerConfigUpdates: { externalId: id } }
-  },
-
-  async deleteSubscription(ctx: DeleteSubscriptionContext): Promise<void> {
-    const config = getProviderConfig(ctx.webhook)
-    const { apiKey, externalId } = config as { apiKey?: string; externalId?: string }
-    if (!apiKey || !externalId) return
-    await fetch(`https://api.{service}.com/webhooks/${externalId}`, {
-      method: 'DELETE',
-      headers: { Authorization: `Bearer ${apiKey}` },
-    }).catch(() => {})
-  },
-}
-```
-
-**Key points:**
-- Throw from `createSubscription` — orchestration rolls back the DB webhook
-- Never throw from `deleteSubscription` — log non-fatally
-- Return `{ providerConfigUpdates: { externalId } }` — orchestration merges into `providerConfig`
-- Add `apiKey` field to `build{Service}ExtraFields` with `password: true`
-
-## Trigger Outputs Schema
-
-Trigger outputs use the same schema as block outputs (NOT tool outputs).
-
-**Supported:** `type` + `description` for leaf fields, nested objects for complex data.
-**NOT supported:** `optional: true`, `items` (those are tool-output-only features).
-
-```typescript
-export function buildOutputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'Event type' },
-    timestamp: { type: 'string', description: 'When it occurred' },
-    payload: { type: 'json', description: 'Full event payload' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Polling Triggers
-
-Use polling when the service lacks reliable webhooks (e.g., Google Sheets, Google Drive, Google Calendar, Gmail, RSS, IMAP). Polling triggers do NOT use `buildTriggerSubBlocks` — they define subBlocks manually.
-
-### Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel export
-└── poller.ts             # TriggerConfig with polling: true
-
-apps/sim/lib/webhooks/polling/
-└── {service}.ts           # PollingProviderHandler implementation
-```
-
-### Polling Handler (`apps/sim/lib/webhooks/polling/{service}.ts`)
-
-```typescript
-import { pollingIdempotency } from '@/lib/core/idempotency/service'
-import type { PollingProviderHandler, PollWebhookContext } from '@/lib/webhooks/polling/types'
-import { markWebhookFailed, markWebhookSuccess, resolveOAuthCredential, updateWebhookProviderConfig } from '@/lib/webhooks/polling/utils'
-import { processPolledWebhookEvent } from '@/lib/webhooks/processor'
-
-export const {service}PollingHandler: PollingProviderHandler = {
-  provider: '{service}',
-  label: '{Service}',
-
-  async pollWebhook(ctx: PollWebhookContext): Promise<'success' | 'failure'> {
-    const { webhookData, workflowData, requestId, logger } = ctx
-    const webhookId = webhookData.id
-
-    try {
-      // For OAuth services:
-      const accessToken = await resolveOAuthCredential(webhookData, '{service}', requestId, logger)
-      const config = webhookData.providerConfig as unknown as {Service}WebhookConfig
-
-      // First poll: seed state, emit nothing
-      if (!config.lastCheckedTimestamp) {
-        await updateWebhookProviderConfig(webhookId, { lastCheckedTimestamp: new Date().toISOString() }, logger)
-        await markWebhookSuccess(webhookId, logger)
-        return 'success'
-      }
-
-      // Fetch changes since last poll, process with idempotency
-      // ...
-
-      await markWebhookSuccess(webhookId, logger)
-      return 'success'
-    } catch (error) {
-      logger.error(`[${requestId}] Error processing {service} webhook ${webhookId}:`, error)
-      await markWebhookFailed(webhookId, logger)
-      return 'failure'
-    }
-  },
-}
-```
-
-**Key patterns:**
-- First poll seeds state and emits nothing (avoids flooding with existing data)
-- Use `pollingIdempotency.executeWithIdempotency(provider, key, callback)` for dedup
-- Use `processPolledWebhookEvent(webhookData, workflowData, payload, requestId)` to fire the workflow
-- Use `updateWebhookProviderConfig(webhookId, partialConfig, logger)` for read-merge-write on state
-- Use the latest server-side timestamp from API responses (not wall clock) to avoid clock skew
-
-### Trigger Config (`apps/sim/triggers/{service}/poller.ts`)
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { TriggerConfig } from '@/triggers/types'
-
-export const {service}PollingTrigger: TriggerConfig = {
-  id: '{service}_poller',
-  name: '{Service} Trigger',
-  provider: '{service}',
-  description: 'Triggers when ...',
-  version: '1.0.0',
-  icon: {Service}Icon,
-  polling: true,               // REQUIRED — routes to polling infrastructure
-
-  subBlocks: [
-    { id: 'triggerCredentials', type: 'oauth-input', title: 'Credentials', serviceId: '{service}', requiredScopes: [], required: true, mode: 'trigger', supportsCredentialSets: true },
-    // ... service-specific config fields (dropdowns, inputs, switches) ...
-    { id: 'triggerInstructions', type: 'text', title: 'Setup Instructions', hideFromPreview: true, mode: 'trigger', defaultValue: '...' },
-  ],
-
-  outputs: {
-    // Must match the payload shape from processPolledWebhookEvent
-  },
-}
-```
-
-### Registration (3 places)
-
-1. **`apps/sim/triggers/constants.ts`** — add provider to `POLLING_PROVIDERS` Set
-2. **`apps/sim/lib/webhooks/polling/registry.ts`** — import handler, add to `POLLING_HANDLERS`
-3. **`apps/sim/triggers/registry.ts`** — import trigger config, add to `TRIGGER_REGISTRY`
-
-### Helm Cron Job
-
-Add to `helm/sim/values.yaml` under the existing polling cron jobs:
-
-```yaml
-{service}WebhookPoll:
-  schedule: "*/1 * * * *"
-  concurrencyPolicy: Forbid
-  url: "http://sim:3000/api/webhooks/poll/{service}"
-```
-
-### Reference Implementations
-
-- Simple: `apps/sim/lib/webhooks/polling/rss.ts` + `apps/sim/triggers/rss/poller.ts`
-- Complex (OAuth, attachments): `apps/sim/lib/webhooks/polling/gmail.ts` + `apps/sim/triggers/gmail/poller.ts`
-- Cursor-based (changes API): `apps/sim/lib/webhooks/polling/google-drive.ts`
-- Timestamp-based: `apps/sim/lib/webhooks/polling/google-calendar.ts`
-
-## Checklist
-
-### Trigger Definition
-- [ ] Created `utils.ts` with options, instructions, extra fields, and output builders
-- [ ] Primary trigger has `includeDropdown: true`; secondary triggers do NOT
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-
-### Registration
-- [ ] All triggers in `triggers/registry.ts` → `TRIGGER_REGISTRY`
-- [ ] Block has `triggers.enabled: true` and lists all trigger IDs in `triggers.available`
-- [ ] Block spreads all trigger subBlocks: `...getTrigger('id').subBlocks`
-
-### Provider Handler (if needed)
-- [ ] Handler file at `apps/sim/lib/webhooks/providers/{service}.ts`
-- [ ] Registered in `providers/registry.ts` (alphabetical)
-- [ ] Signature validator is a private function inside the handler file
-- [ ] `formatInput` output keys match trigger `outputs` exactly
-- [ ] Event matching uses dynamic `await import()` for trigger utils
-
-### Auto Registration (if supported)
-- [ ] `createSubscription` and `deleteSubscription` on the handler
-- [ ] NO changes to `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] API key field uses `password: true`
-
-### Polling Trigger (if applicable)
-- [ ] Handler implements `PollingProviderHandler` at `lib/webhooks/polling/{service}.ts`
-- [ ] Trigger config has `polling: true` and defines subBlocks manually (no `buildTriggerSubBlocks`)
-- [ ] Provider string matches across: trigger config, handler, `POLLING_PROVIDERS`, polling registry
-- [ ] First poll seeds state and emits nothing
-- [ ] Added provider to `POLLING_PROVIDERS` in `triggers/constants.ts`
-- [ ] Added handler to `POLLING_HANDLERS` in `lib/webhooks/polling/registry.ts`
-- [ ] Added cron job to `helm/sim/values.yaml`
-- [ ] Payload shape matches trigger `outputs` schema
-
-### Testing
-- [ ] `bun run type-check` passes
-- [ ] Manually verify output keys match trigger `outputs` keys
-- [ ] Trigger UI shows correctly in the block

.claude/commands/cleanup.md

@@ -1,25 +0,0 @@
----
-description: Run all code quality skills in sequence — effects, memo, callbacks, state, React Query, and emcn design review
-argument-hint: [scope] [fix=true|false]
----
-
-# Cleanup
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Steps
-
-Run each of these skills in order on the specified scope, passing through the scope and fix arguments. After each skill completes, move to the next. Do not skip any.
-
-1. `/you-might-not-need-an-effect $ARGUMENTS`
-2. `/you-might-not-need-a-memo $ARGUMENTS`
-3. `/you-might-not-need-a-callback $ARGUMENTS`
-4. `/you-might-not-need-state $ARGUMENTS`
-5. `/react-query-best-practices $ARGUMENTS`
-6. `/emcn-design-review $ARGUMENTS`
-
-After all skills have run, output a summary of what was found and fixed (or proposed) across all six passes.

.claude/commands/council.md

@@ -1,12 +0,0 @@
----
-description: Spawn task agents to explore a given area of interest in the codebase
-argument-hint: <area-of-interest>
----
-
-Based on the given area of interest, please:
-
-1. Dig around the codebase in terms of that given area of interest, gather general information such as keywords and architecture overview.
-2. Spawn off n=10 (unless specified otherwise) task agents to dig deeper into the codebase in terms of that given area of interest, some of them should be out of the box for variance.
-3. Once the task agents are done, use the information to do what the user wants.
-
-If user is in plan mode, use the information to create the plan.

.claude/commands/emcn-design-review.md

@@ -1,79 +0,0 @@
----
-description: Review UI code for alignment with the emcn design system — components, tokens, patterns, and conventions
-argument-hint: [scope] [fix=true|false]
----
-
-# EMCN Design Review
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses **emcn**, a custom component library built on Radix UI primitives with CVA variants and CSS variable design tokens. All UI must use emcn components and tokens.
-
-## Steps
-
-1. Read the emcn barrel export at `apps/sim/components/emcn/components/index.ts` to know what's available
-2. Read `apps/sim/app/_styles/globals.css` for CSS variable tokens
-3. Analyze the specified scope against every rule below
-4. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.
-
----
-
-## Imports
-
-- Import from `@/components/emcn` barrel, never subpaths
-- Icons from `@/components/emcn/icons` or `lucide-react`
-- Use `cn` from `@/lib/core/utils/cn` for conditional classes
-
-## Design Tokens
-
-Use CSS variable pattern (`text-[var(--text-primary)]`), never Tailwind semantics (`text-muted-foreground`) or hardcoded colors (`text-gray-500`, `#333`).
-
-**Text**: `--text-primary`, `--text-secondary`, `--text-tertiary`, `--text-muted`, `--text-icon`, `--text-inverse`, `--text-error`
-**Surfaces**: `--bg`, `--surface-2` through `--surface-7`, `--surface-hover`, `--surface-active`
-**Borders**: `--border`, `--border-1`, `--border-muted`
-**Z-Index**: `--z-dropdown` (100), `--z-modal` (200), `--z-popover` (300), `--z-tooltip` (400), `--z-toast` (500)
-**Shadows**: `shadow-subtle`, `shadow-medium`, `shadow-overlay`, `shadow-card`
-
-## Buttons
-
-| Action | Variant |
-|--------|---------|
-| Toolbar, icon-only | `ghost` (most common, 28%) |
-| Create, save, submit | `primary` (24%) |
-| Cancel, close | `default` |
-| Delete, remove | `destructive` |
-| Selected state | `active` |
-| Toggle | `outline` |
-
-## Delete/Remove Confirmations
-
-Modal `size="sm"`, title "Delete/Remove {ItemType}", `variant="destructive"` action button, `variant="default"` cancel. Cancel left, action right (100% compliance). Use `text-[var(--text-error)]` for irreversible warnings.
-
-## Toast
-
-`toast.success()`, `toast.error()`, `toast()` from `@/components/emcn`. Never custom notification UI.
-
-## Badges
-
-`red`=error/failed, `gray-secondary`=metadata/roles, `type`=type annotations, `green`=success/active, `gray`=neutral, `amber`=processing, `orange`=paused, `blue`=info. Use `dot` prop for status indicators.
-
-## Icons
-
-Default: `h-[14px] w-[14px]` (400+ uses). Color: `text-[var(--text-icon)]`. Scale: 14px > 16px > 12px > 20px.
-
-## Anti-patterns to flag
-
-- Raw `<button>`/`<input>` instead of emcn components
-- Hardcoded colors (`text-gray-*`, `#hex`, `rgb()`)
-- Tailwind semantics (`text-muted-foreground`) instead of CSS variables
-- Template literal className instead of `cn()`
-- Inline styles for colors/static values (dynamic values OK)
-- Importing from emcn subpaths instead of barrel
-- Arbitrary z-index instead of tokens
-- Wrong button variant for action type

.claude/commands/react-query-best-practices.md

@@ -1,54 +0,0 @@
----
-description: Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership
-argument-hint: [scope] [fix=true|false]
----
-
-# React Query Best Practices
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/hooks/queries/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query (TanStack Query) as the single source of truth for all server state. All query hooks live in `hooks/queries/`. Zustand is used only for client-only UI state. Server data must never be duplicated into useState or Zustand outside of mutation callbacks that coordinate cross-store state.
-
-## References
-
-Read these before analyzing:
-1. https://tkdodo.eu/blog/practical-react-query — foundational defaults, custom hooks, avoiding local state copies
-2. https://tkdodo.eu/blog/effective-react-query-keys — key factory pattern, hierarchical keys, fuzzy invalidation
-3. https://tkdodo.eu/blog/react-query-as-a-state-manager — React Query IS your server state manager
-
-## Rules to enforce
-
-### Query key factories
-- Every file in `hooks/queries/` must have a hierarchical key factory with an `all` root key
-- Keys must include intermediate plural keys (`lists`, `details`) for prefix invalidation
-- Key factories are colocated with their query hooks, not in a global keys file
-
-### Query hooks
-- Every `queryFn` must forward `signal` for request cancellation
-- Every query must have an explicit `staleTime` (default 0 is almost never correct)
-- `keepPreviousData` / `placeholderData` only on variable-key queries (where params change), never on static keys
-- Use `enabled` to prevent queries from running without required params
-
-### Mutations
-- Use `onSettled` (not `onSuccess`) for cache reconciliation — it fires on both success and error
-- For optimistic updates: save previous data in `onMutate`, roll back in `onError`
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- Don't include mutation objects in `useCallback` deps — `.mutate()` is stable
-
-### Server state ownership
-- Never copy query data into useState. Use query data directly in components.
-- Never copy query data into Zustand stores (exception: mutation callbacks that coordinate cross-store state like temp ID replacement)
-- The query cache is not a local state manager — `setQueryData` is for optimistic updates only
-- Forms are the one deliberate exception: copy server data into local form state with `staleTime: Infinity`
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope against the rules listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/commands/validate-connector.md

@@ -1,316 +0,0 @@
----
-description: Validate an existing knowledge base connector against its service's API docs
-argument-hint: <service-name> [api-docs-url]
----
-
-# Validate Connector Skill
-
-You are an expert auditor for Sim knowledge base connectors. Your job is to thoroughly validate that an existing connector is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate a connector:
-1. Read the service's API documentation (via Context7 or WebFetch)
-2. Read the connector implementation, OAuth config, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the connector — do not skip any:
-
-```
-apps/sim/connectors/{service}/{service}.ts   # Connector implementation
-apps/sim/connectors/{service}/index.ts       # Barrel export
-apps/sim/connectors/registry.ts              # Connector registry entry
-apps/sim/connectors/types.ts                 # ConnectorConfig interface, ExternalDocument, etc.
-apps/sim/connectors/utils.ts                 # Shared utilities (computeContentHash, htmlToPlainText, etc.)
-apps/sim/lib/oauth/oauth.ts                  # OAUTH_PROVIDERS — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts                  # getCanonicalScopesForProvider, getScopesForService, SCOPE_DESCRIPTIONS
-apps/sim/lib/oauth/types.ts                  # OAuthService union type
-apps/sim/components/icons.tsx                 # Icon definition for the service
-```
-
-If the connector uses selectors, also read:
-```
-apps/sim/hooks/selectors/registry.ts         # Selector key definitions
-apps/sim/hooks/selectors/types.ts            # SelectorKey union type
-apps/sim/lib/workflows/subblocks/context.ts  # SELECTOR_CONTEXT_FIELDS
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (cursor, offset, next token)
-- Rate limits and error formats
-- OAuth scopes and their meanings
-
-Use Context7 (resolve-library-id → query-docs) or WebFetch to retrieve documentation. If both fail, note which claims are based on training knowledge vs verified docs.
-
-## Step 3: Validate API Endpoints
-
-For **every** API call in the connector (`listDocuments`, `getDocument`, `validateConfig`, and any helper functions), verify against the API docs:
-
-### URLs and Methods
-- [ ] Base URL is correct for the service's API version
-- [ ] Endpoint paths match the API docs exactly
-- [ ] HTTP method is correct (GET, POST, PUT, PATCH, DELETE)
-- [ ] Path parameters are correctly interpolated and URI-encoded where needed
-- [ ] Query parameters use correct names and formats per the API docs
-
-### Headers
-- [ ] Authorization header uses the correct format:
-  - OAuth: `Authorization: Bearer ${accessToken}`
-  - API Key: correct header name per the service's docs
-- [ ] `Content-Type` is set for POST/PUT/PATCH requests
-- [ ] Any service-specific headers are present (e.g., `Notion-Version`, `Dropbox-API-Arg`)
-- [ ] No headers are sent that the API doesn't support or silently ignores
-
-### Request Bodies
-- [ ] POST/PUT body fields match API parameter names exactly
-- [ ] Required fields are always sent
-- [ ] Optional fields are conditionally included (not sent as `null` or empty unless the API expects that)
-- [ ] Field value types match API expectations (string vs number vs boolean)
-
-### Input Sanitization
-- [ ] User-controlled values interpolated into query strings are properly escaped:
-  - OData `$filter`: single quotes escaped with `''` (e.g., `externalId.replace(/'/g, "''")`)
-  - SOQL: single quotes escaped with `\'`
-  - GraphQL variables: passed as variables, not interpolated into query strings
-  - URL path segments: `encodeURIComponent()` applied
-- [ ] URL-type config fields (e.g., `siteUrl`, `instanceUrl`) are normalized:
-  - Strip `https://` / `http://` prefix if the API expects bare domains
-  - Strip trailing `/`
-  - Apply `.trim()` before validation
-
-### Response Parsing
-- [ ] Response structure is correctly traversed (e.g., `data.results` vs `data.items` vs `data`)
-- [ ] Field names extracted match what the API actually returns
-- [ ] Nullable fields are handled with `?? null` or `|| undefined`
-- [ ] Error responses are checked before accessing data fields
-
-## Step 4: Validate OAuth Scopes (if OAuth connector)
-
-Scopes must be correctly declared and sufficient for all API calls the connector makes.
-
-### Connector requiredScopes
-- [ ] `requiredScopes` in the connector's `auth` config lists all scopes needed by the connector
-- [ ] Each scope in `requiredScopes` is a real, valid scope recognized by the service's API
-- [ ] No invalid, deprecated, or made-up scopes are listed
-- [ ] No unnecessary excess scopes beyond what the connector actually needs
-
-### Scope Subset Validation (CRITICAL)
-- [ ] Every scope in `requiredScopes` exists in the OAuth provider's `scopes` array in `lib/oauth/oauth.ts`
-- [ ] Find the provider in `OAUTH_PROVIDERS[providerGroup].services[serviceId].scopes`
-- [ ] Verify: `requiredScopes` ⊆ `OAUTH_PROVIDERS scopes` (every required scope is present in the provider config)
-- [ ] If a required scope is NOT in the provider config, flag as **critical** — the connector will fail at runtime
-
-### Scope Sufficiency
-For each API endpoint the connector calls:
-- [ ] Identify which scopes are required per the API docs
-- [ ] Verify those scopes are included in the connector's `requiredScopes`
-- [ ] If the connector calls endpoints requiring scopes not in `requiredScopes`, flag as **warning**
-
-### Token Refresh Config
-- [ ] Check the `getOAuthTokenRefreshConfig` function in `lib/oauth/oauth.ts` for this provider
-- [ ] `useBasicAuth` matches the service's token exchange requirements
-- [ ] `supportsRefreshTokenRotation` matches whether the service issues rotating refresh tokens
-- [ ] Token endpoint URL is correct
-
-## Step 5: Validate Pagination
-
-### listDocuments Pagination
-- [ ] Cursor/pagination parameter name matches the API docs
-- [ ] Response pagination field is correctly extracted (e.g., `next_cursor`, `nextPageToken`, `@odata.nextLink`, `offset`)
-- [ ] `hasMore` is correctly determined from the response
-- [ ] `nextCursor` is correctly passed back for the next page
-- [ ] `maxItems` / `maxRecords` cap is correctly applied across pages using `syncContext.totalDocsFetched`
-- [ ] Page size is within the API's allowed range (not exceeding max page size)
-- [ ] Last page precision: when a `maxItems` cap exists, the final page request uses `Math.min(PAGE_SIZE, remaining)` to avoid fetching more records than needed
-- [ ] No off-by-one errors in pagination tracking
-- [ ] The connector does NOT hit known API pagination limits silently (e.g., HubSpot search 10k cap)
-
-### Pagination State Across Pages
-- [ ] `syncContext` is used to cache state across pages (user names, field maps, instance URLs, portal IDs, etc.)
-- [ ] Cached state in `syncContext` is correctly initialized on first page and reused on subsequent pages
-
-## Step 6: Validate Data Transformation
-
-### ExternalDocument Construction
-- [ ] `externalId` is a stable, unique identifier from the source API
-- [ ] `title` is extracted from the correct field and has a sensible fallback (e.g., `'Untitled'`)
-- [ ] `content` is plain text — HTML content is stripped using `htmlToPlainText` from `@/connectors/utils`
-- [ ] `mimeType` is `'text/plain'`
-- [ ] `contentHash` is computed using `computeContentHash` from `@/connectors/utils`
-- [ ] `sourceUrl` is a valid, complete URL back to the original resource (not relative)
-- [ ] `metadata` contains all fields referenced by `mapTags` and `tagDefinitions`
-
-### Content Extraction
-- [ ] Rich text / HTML fields are converted to plain text before indexing
-- [ ] Important content is not silently dropped (e.g., nested blocks, table cells, code blocks)
-- [ ] Content is not silently truncated without logging a warning
-- [ ] Empty/blank documents are properly filtered out
-- [ ] Size checks use `Buffer.byteLength(text, 'utf8')` not `text.length` when comparing against byte-based limits (e.g., `MAX_FILE_SIZE` in bytes)
-
-## Step 7: Validate Tag Definitions and mapTags
-
-### tagDefinitions
-- [ ] Each `tagDefinition` has an `id`, `displayName`, and `fieldType`
-- [ ] `fieldType` matches the actual data type: `'text'` for strings, `'number'` for numbers, `'date'` for dates, `'boolean'` for booleans
-- [ ] Every `id` in `tagDefinitions` is returned by `mapTags`
-- [ ] No `tagDefinition` references a field that `mapTags` never produces
-
-### mapTags
-- [ ] Return keys match `tagDefinition` `id` values exactly
-- [ ] Date values are properly parsed using `parseTagDate` from `@/connectors/utils`
-- [ ] Array values are properly joined using `joinTagArray` from `@/connectors/utils`
-- [ ] Number values are validated (not `NaN`)
-- [ ] Metadata field names accessed in `mapTags` match what `listDocuments`/`getDocument` store in `metadata`
-
-## Step 8: Validate Config Fields and Validation
-
-### configFields
-- [ ] Every field has `id`, `title`, `type`
-- [ ] `required` is set explicitly (not omitted)
-- [ ] Dropdown fields have `options` with `label` and `id` for each option
-- [ ] Selector fields follow the canonical pair pattern:
-  - A `type: 'selector'` field with `selectorKey`, `canonicalParamId`, `mode: 'basic'`
-  - A `type: 'short-input'` field with the same `canonicalParamId`, `mode: 'advanced'`
-  - `required` is identical on both fields in the pair
-- [ ] `selectorKey` values exist in the selector registry
-- [ ] `dependsOn` references selector field `id` values, not `canonicalParamId`
-
-### validateConfig
-- [ ] Validates all required fields are present before making API calls
-- [ ] Validates optional numeric fields (checks `Number.isNaN`, positive values)
-- [ ] Makes a lightweight API call to verify access (e.g., fetch 1 record, get profile)
-- [ ] Uses `VALIDATE_RETRY_OPTIONS` for retry budget
-- [ ] Returns `{ valid: true }` on success
-- [ ] Returns `{ valid: false, error: 'descriptive message' }` on failure
-- [ ] Catches exceptions and returns user-friendly error messages
-- [ ] Does NOT make expensive calls (full data listing, large queries)
-
-## Step 9: Validate getDocument
-
-- [ ] Fetches a single document by `externalId`
-- [ ] Returns `null` for 404 / not found (does not throw)
-- [ ] Returns the same `ExternalDocument` shape as `listDocuments`
-- [ ] Handles all content types that `listDocuments` can produce (e.g., if `listDocuments` returns both pages and blogposts, `getDocument` must handle both — not hardcode one endpoint)
-- [ ] Forwards `syncContext` if it needs cached state (user names, field maps, etc.)
-- [ ] Error handling is graceful (catches, logs, returns null or throws with context)
-- [ ] Does not redundantly re-fetch data already included in the initial API response (e.g., if comments come back with the post, don't fetch them again separately)
-
-## Step 10: Validate General Quality
-
-### fetchWithRetry Usage
-- [ ] All external API calls use `fetchWithRetry` from `@/lib/knowledge/documents/utils`
-- [ ] No raw `fetch()` calls to external APIs
-- [ ] `VALIDATE_RETRY_OPTIONS` used in `validateConfig`
-- [ ] If `validateConfig` calls a shared helper (e.g., `linearGraphQL`, `resolveId`), that helper must accept and forward `retryOptions` to `fetchWithRetry`
-- [ ] Default retry options used in `listDocuments`/`getDocument`
-
-### API Efficiency
-- [ ] APIs that support field selection (e.g., `$select`, `sysparm_fields`, `fields`) should request only the fields the connector needs — in both `listDocuments` AND `getDocument`
-- [ ] No redundant API calls: if a helper already fetches data (e.g., site metadata), callers should reuse the result instead of making a second call for the same information
-- [ ] Sequential per-item API calls (fetching details for each document in a loop) should be batched with `Promise.all` and a concurrency limit of 3-5
-
-### Error Handling
-- [ ] Individual document failures are caught and logged without aborting the sync
-- [ ] API error responses include status codes in error messages
-- [ ] No unhandled promise rejections in concurrent operations
-
-### Concurrency
-- [ ] Concurrent API calls use reasonable batch sizes (3-5 is typical)
-- [ ] No unbounded `Promise.all` over large arrays
-
-### Logging
-- [ ] Uses `createLogger` from `@sim/logger` (not `console.log`)
-- [ ] Logs sync progress at `info` level
-- [ ] Logs errors at `warn` or `error` level with context
-
-### Registry
-- [ ] Connector is exported from `connectors/{service}/index.ts`
-- [ ] Connector is registered in `connectors/registry.ts`
-- [ ] Registry key matches the connector's `id` field
-
-## Step 11: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors, data loss, or auth failures):
-- Wrong API endpoint URL or HTTP method
-- Invalid or missing OAuth scopes (not in provider config)
-- Incorrect response field mapping (accessing wrong path)
-- SOQL/query fields that don't exist on the target object
-- Pagination that silently hits undocumented API limits
-- Missing error handling that would crash the sync
-- `requiredScopes` not a subset of OAuth provider scopes
-- Query/filter injection: user-controlled values interpolated into OData `$filter`, SOQL, or query strings without escaping
-
-**Warning** (incorrect behavior, data quality issues, or convention violations):
-- HTML content not stripped via `htmlToPlainText`
-- `getDocument` not forwarding `syncContext`
-- `getDocument` hardcoded to one content type when `listDocuments` returns multiple (e.g., only pages but not blogposts)
-- Missing `tagDefinition` for metadata fields returned by `mapTags`
-- Incorrect `useBasicAuth` or `supportsRefreshTokenRotation` in token refresh config
-- Invalid scope names that the API doesn't recognize (even if silently ignored)
-- Private resources excluded from name-based lookup despite scopes being available
-- Silent data truncation without logging
-- Size checks using `text.length` (character count) instead of `Buffer.byteLength` (byte count) for byte-based limits
-- URL-type config fields not normalized (protocol prefix, trailing slashes cause API failures)
-- `VALIDATE_RETRY_OPTIONS` not threaded through helper functions called by `validateConfig`
-
-**Suggestion** (minor improvements):
-- Missing incremental sync support despite API supporting it
-- Overly broad scopes that could be narrowed (not wrong, but could be tighter)
-- Source URL format could be more specific
-- Missing `orderBy` for deterministic pagination
-- Redundant API calls that could be cached in `syncContext`
-- Sequential per-item API calls that could be batched with `Promise.all` (concurrency 3-5)
-- API supports field selection but connector fetches all fields (e.g., missing `$select`, `sysparm_fields`, `fields`)
-- `getDocument` re-fetches data already included in the initial API response (e.g., comments returned with post)
-- Last page of pagination requests full `PAGE_SIZE` when fewer records remain (`Math.min(PAGE_SIZE, remaining)`)
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes
-2. TypeScript compiles clean
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read connector implementation, types, utils, registry, and OAuth config
-- [ ] Pulled and read official API documentation for the service
-- [ ] Validated every API endpoint URL, method, headers, and body against API docs
-- [ ] Validated input sanitization: no query/filter injection, URL fields normalized
-- [ ] Validated OAuth scopes: `requiredScopes` ⊆ OAuth provider `scopes` in `oauth.ts`
-- [ ] Validated each scope is real and recognized by the service's API
-- [ ] Validated scopes are sufficient for all API endpoints the connector calls
-- [ ] Validated token refresh config (`useBasicAuth`, `supportsRefreshTokenRotation`)
-- [ ] Validated pagination: cursor names, page sizes, hasMore logic, no silent caps
-- [ ] Validated data transformation: plain text extraction, HTML stripping, content hashing
-- [ ] Validated tag definitions match mapTags output, correct fieldTypes
-- [ ] Validated config fields: canonical pairs, selector keys, required flags
-- [ ] Validated validateConfig: lightweight check, error messages, retry options
-- [ ] Validated getDocument: null on 404, all content types handled, no redundant re-fetches, syncContext forwarding
-- [ ] Validated fetchWithRetry used for all external calls (no raw fetch), VALIDATE_RETRY_OPTIONS threaded through helpers
-- [ ] Validated API efficiency: field selection used, no redundant calls, sequential fetches batched
-- [ ] Validated error handling: graceful failures, no unhandled rejections
-- [ ] Validated logging: createLogger, no console.log
-- [ ] Validated registry: correct export, correct key
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.claude/commands/validate-integration.md

@@ -1,289 +0,0 @@
----
-description: Validate an existing Sim integration (tools, block, registry) against the service's API docs
-argument-hint: <service-name> [api-docs-url]
----
-
-# Validate Integration Skill
-
-You are an expert auditor for Sim integrations. Your job is to thoroughly validate that an existing integration is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate an integration:
-1. Read the service's API documentation (via WebFetch or Context7)
-2. Read every tool, the block, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the integration — do not skip any:
-
-```
-apps/sim/tools/{service}/          # All tool files, types.ts, index.ts
-apps/sim/blocks/blocks/{service}.ts # Block definition
-apps/sim/tools/registry.ts          # Tool registry entries for this service
-apps/sim/blocks/registry.ts         # Block registry entry for this service
-apps/sim/components/icons.tsx        # Icon definition
-apps/sim/lib/auth/auth.ts           # OAuth config — should use getCanonicalScopesForProvider()
-apps/sim/lib/oauth/oauth.ts         # OAuth provider config — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts               # Scope utilities, SCOPE_DESCRIPTIONS for modal UI
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (which param name, which response field)
-- Rate limits and error formats
-
-## Step 3: Validate Tools
-
-For **every** tool file, check:
-
-### Tool ID and Naming
-- [ ] Tool ID uses `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`)
-- [ ] Tool `name` is human-readable (e.g., `'X Create Tweet'`)
-- [ ] Tool `description` is a concise one-liner describing what it does
-- [ ] Tool `version` is set (`'1.0.0'` or `'2.0.0'` for V2)
-
-### Params
-- [ ] All required API params are marked `required: true`
-- [ ] All optional API params are marked `required: false`
-- [ ] Every param has explicit `required: true` or `required: false` — never omitted
-- [ ] Param types match the API (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] Visibility is correct:
-  - `'hidden'` — ONLY for OAuth access tokens and system-injected params
-  - `'user-only'` — for API keys, credentials, and account-specific IDs the user must provide
-  - `'user-or-llm'` — for everything else (search queries, content, filters, IDs that could come from other blocks)
-- [ ] Every param has a `description` that explains what it does
-
-### Request
-- [ ] URL matches the API endpoint exactly (correct base URL, path segments, path params)
-- [ ] HTTP method matches the API spec (GET, POST, PUT, PATCH, DELETE)
-- [ ] Headers include correct auth pattern:
-  - OAuth: `Authorization: Bearer ${params.accessToken}`
-  - API Key: correct header name and format per the service's docs
-- [ ] `Content-Type` header is set for POST/PUT/PATCH requests
-- [ ] Body sends all required fields and only includes optional fields when provided
-- [ ] For GET requests with query params: URL is constructed correctly with query string
-- [ ] ID fields in URL paths are `.trim()`-ed to prevent copy-paste whitespace errors
-- [ ] Path params use template literals correctly: `` `https://api.service.com/v1/${params.id.trim()}` ``
-
-### Response / transformResponse
-- [ ] Correctly parses the API response (`await response.json()`)
-- [ ] Extracts the right fields from the response structure (e.g., `data.data` vs `data` vs `data.results`)
-- [ ] All nullable fields use `?? null`
-- [ ] All optional arrays use `?? []`
-- [ ] Error cases are handled: checks for missing/empty data and returns meaningful error
-- [ ] Does NOT do raw JSON dumps — extracts meaningful, individual fields
-
-### Outputs
-- [ ] All output fields match what the API actually returns
-- [ ] No fields are missing that the API provides and users would commonly need
-- [ ] No phantom fields defined that the API doesn't return
-- [ ] `optional: true` is set on fields that may not exist in all responses
-- [ ] When using `type: 'json'` and the shape is known, `properties` defines the inner fields
-- [ ] When using `type: 'array'`, `items` defines the item structure with `properties`
-- [ ] Field descriptions are accurate and helpful
-
-### Types (types.ts)
-- [ ] Has param interfaces for every tool (e.g., `XCreateTweetParams`)
-- [ ] Has response interfaces for every tool (extending `ToolResponse`)
-- [ ] Optional params use `?` in the interface (e.g., `replyTo?: string`)
-- [ ] Field names in types match actual API field names
-- [ ] Shared response types are properly reused (e.g., `XTweetResponse` shared across tweet tools)
-
-### Barrel Export (index.ts)
-- [ ] Every tool is exported
-- [ ] All types are re-exported (`export * from './types'`)
-- [ ] No orphaned exports (tools that don't exist)
-
-### Tool Registry (tools/registry.ts)
-- [ ] Every tool is imported and registered
-- [ ] Registry keys use snake_case and match tool IDs exactly
-- [ ] Entries are in alphabetical order within the file
-
-## Step 4: Validate Block
-
-### Block ↔ Tool Alignment (CRITICAL)
-
-This is the most important validation — the block must be perfectly aligned with every tool it references.
-
-For **each tool** in `tools.access`:
-- [ ] The operation dropdown has an option whose ID matches the tool ID (or the `tools.config.tool` function correctly maps to it)
-- [ ] Every **required** tool param (except `accessToken`) has a corresponding subBlock input that is:
-  - Shown when that operation is selected (correct `condition`)
-  - Marked as `required: true` (or conditionally required)
-- [ ] Every **optional** tool param has a corresponding subBlock input (or is intentionally omitted if truly never needed)
-- [ ] SubBlock `id` values are unique across the entire block — no duplicates even across different conditions
-- [ ] The `tools.config.tool` function returns the correct tool ID for every possible operation value
-- [ ] The `tools.config.params` function correctly maps subBlock IDs to tool param names when they differ
-
-### SubBlocks
-- [ ] Operation dropdown lists ALL tool operations available in `tools.access`
-- [ ] Dropdown option labels are human-readable and descriptive
-- [ ] Conditions use correct syntax:
-  - Single value: `{ field: 'operation', value: 'x_create_tweet' }`
-  - Multiple values (OR): `{ field: 'operation', value: ['x_create_tweet', 'x_delete_tweet'] }`
-  - Negation: `{ field: 'operation', value: 'delete', not: true }`
-  - Compound: `{ field: 'op', value: 'send', and: { field: 'type', value: 'dm' } }`
-- [ ] Condition arrays include ALL operations that use that field — none missing
-- [ ] `dependsOn` is set for fields that need other values (selectors depending on credential, cascading dropdowns)
-- [ ] SubBlock types match tool param types:
-  - Enum/fixed options → `dropdown`
-  - Free text → `short-input`
-  - Long text/content → `long-input`
-  - True/false → `dropdown` with Yes/No options (not `switch` unless purely UI toggle)
-  - Credentials → `oauth-input` with correct `serviceId`
-- [ ] Dropdown `value: () => 'default'` is set for dropdowns with a sensible default
-
-### Advanced Mode
-- [ ] Optional, rarely-used fields are set to `mode: 'advanced'`:
-  - Pagination tokens / next tokens
-  - Time range filters (start/end time)
-  - Sort order / direction options
-  - Max results / per page limits
-  - Reply settings / threading options
-  - Rarely used IDs (reply-to, quote-tweet, etc.)
-  - Exclude filters
-- [ ] **Required** fields are NEVER set to `mode: 'advanced'`
-- [ ] Fields that users fill in most of the time are NOT set to `mode: 'advanced'`
-
-### WandConfig
-- [ ] Timestamp fields have `wandConfig` with `generationType: 'timestamp'`
-- [ ] Comma-separated list fields have `wandConfig` with a descriptive prompt
-- [ ] Complex filter/query fields have `wandConfig` with format examples in the prompt
-- [ ] All `wandConfig` prompts end with "Return ONLY the [format] - no explanations, no extra text."
-- [ ] `wandConfig.placeholder` describes what to type in natural language
-
-### Tools Config
-- [ ] `tools.access` lists **every** tool ID the block can use — none missing
-- [ ] `tools.config.tool` returns the correct tool ID for each operation
-- [ ] Type coercions are in `tools.config.params` (runs at execution time), NOT in `tools.config.tool` (runs at serialization time before variable resolution)
-- [ ] `tools.config.params` handles:
-  - `Number()` conversion for numeric params that come as strings from inputs
-  - `Boolean` / string-to-boolean conversion for toggle params
-  - Empty string → `undefined` conversion for optional dropdown values
-  - Any subBlock ID → tool param name remapping
-- [ ] No `Number()`, `JSON.parse()`, or other coercions in `tools.config.tool` — these would destroy dynamic references like `<Block.output>`
-
-### Block Outputs
-- [ ] Outputs cover the key fields returned by ALL tools (not just one operation)
-- [ ] Output types are correct (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] `type: 'json'` outputs either:
-  - Describe inner fields in the description string (GOOD): `'User profile (id, name, username, bio)'`
-  - Use nested output definitions (BEST): `{ id: { type: 'string' }, name: { type: 'string' } }`
-- [ ] No opaque `type: 'json'` with vague descriptions like `'Response data'`
-- [ ] Outputs that only appear for certain operations use `condition` if supported, or document which operations return them
-
-### Block Metadata
-- [ ] `type` is snake_case (e.g., `'x'`, `'cloudflare'`)
-- [ ] `name` is human-readable (e.g., `'X'`, `'Cloudflare'`)
-- [ ] `description` is a concise one-liner
-- [ ] `longDescription` provides detail for docs
-- [ ] `docsLink` points to `'https://docs.sim.ai/tools/{service}'`
-- [ ] `category` is `'tools'`
-- [ ] `bgColor` uses the service's brand color hex
-- [ ] `icon` references the correct icon component from `@/components/icons`
-- [ ] `authMode` is set correctly (`AuthMode.OAuth` or `AuthMode.ApiKey`)
-- [ ] Block is registered in `blocks/registry.ts` alphabetically
-
-### Block Inputs
-- [ ] `inputs` section lists all subBlock params that the block accepts
-- [ ] Input types match the subBlock types
-- [ ] When using `canonicalParamId`, inputs list the canonical ID (not the raw subBlock IDs)
-
-## Step 5: Validate OAuth Scopes (if OAuth service)
-
-Scopes are centralized — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-- [ ] Scopes defined in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-- [ ] `auth.ts` uses `getCanonicalScopesForProvider(providerId)` — NOT a hardcoded array
-- [ ] Block `requiredScopes` uses `getScopesForService(serviceId)` — NOT a hardcoded array
-- [ ] No hardcoded scope arrays in `auth.ts` or block files (should all use utility functions)
-- [ ] Each scope has a human-readable description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] No excess scopes that aren't needed by any tool
-
-## Step 6: Validate Pagination Consistency
-
-If any tools support pagination:
-- [ ] Pagination param names match the API docs (e.g., `pagination_token` vs `next_token` vs `cursor`)
-- [ ] Different API endpoints that use different pagination param names have separate subBlocks in the block
-- [ ] Pagination response fields (`nextToken`, `cursor`, etc.) are included in tool outputs
-- [ ] Pagination subBlocks are set to `mode: 'advanced'`
-
-## Step 7: Validate Error Handling
-
-- [ ] `transformResponse` checks for error conditions before accessing data
-- [ ] Error responses include meaningful messages (not just generic "failed")
-- [ ] HTTP error status codes are handled (check `response.ok` or status codes)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors or incorrect behavior):
-- Wrong endpoint URL or HTTP method
-- Missing required params or wrong `required` flag
-- Incorrect response field mapping (accessing wrong path in response)
-- Missing error handling that would cause crashes
-- Tool ID mismatch between tool file, registry, and block `tools.access`
-- OAuth scopes missing in `auth.ts` that tools need
-- `tools.config.tool` returning wrong tool ID for an operation
-- Type coercions in `tools.config.tool` instead of `tools.config.params`
-
-**Warning** (follows conventions incorrectly or has usability issues):
-- Optional field not set to `mode: 'advanced'`
-- Missing `wandConfig` on timestamp/complex fields
-- Wrong `visibility` on params (e.g., `'hidden'` instead of `'user-or-llm'`)
-- Missing `optional: true` on nullable outputs
-- Opaque `type: 'json'` without property descriptions
-- Missing `.trim()` on ID fields in request URLs
-- Missing `?? null` on nullable response fields
-- Block condition array missing an operation that uses that field
-- Hardcoded scope arrays instead of using `getScopesForService()` / `getCanonicalScopesForProvider()`
-- Missing scope description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-
-**Suggestion** (minor improvements):
-- Better description text
-- Inconsistent naming across tools
-- Missing `longDescription` or `docsLink`
-- Pagination fields that could benefit from `wandConfig`
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes with no fixes needed
-2. TypeScript compiles clean (no type errors)
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read ALL tool files, block, types, index, and registries
-- [ ] Pulled and read official API documentation
-- [ ] Validated every tool's ID, params, request, response, outputs, and types against API docs
-- [ ] Validated block ↔ tool alignment (every tool param has a subBlock, every condition is correct)
-- [ ] Validated advanced mode on optional/rarely-used fields
-- [ ] Validated wandConfig on timestamps and complex inputs
-- [ ] Validated tools.config mapping, tool selector, and type coercions
-- [ ] Validated block outputs match what tools return, with typed JSON where possible
-- [ ] Validated OAuth scopes use centralized utilities (getScopesForService, getCanonicalScopesForProvider) — no hardcoded arrays
-- [ ] Validated scope descriptions exist in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for all scopes
-- [ ] Validated pagination consistency across tools and block
-- [ ] Validated error handling (error checks, meaningful messages)
-- [ ] Validated registry entries (tools and block, alphabetical, correct imports)
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.claude/commands/validate-trigger.md

@@ -1,212 +0,0 @@
----
-description: Validate an existing Sim webhook trigger against provider API docs and repository conventions
-argument-hint: <service-name> [api-docs-url]
----
-
-# Validate Trigger
-
-You are an expert auditor for Sim webhook triggers. Your job is to validate that an existing trigger implementation is correct, complete, secure, and aligned across all layers.
-
-## Your Task
-
-1. Read the service's webhook/API documentation (via WebFetch)
-2. Read every trigger file, provider handler, and registry entry
-3. Cross-reference against the API docs and Sim conventions
-4. Report all issues grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the trigger — do not skip any:
-
-```
-apps/sim/triggers/{service}/           # All trigger files, utils.ts, index.ts
-apps/sim/lib/webhooks/providers/{service}.ts  # Provider handler (if exists)
-apps/sim/lib/webhooks/providers/registry.ts   # Handler registry
-apps/sim/triggers/registry.ts                 # Trigger registry
-apps/sim/blocks/blocks/{service}.ts           # Block definition (trigger wiring)
-```
-
-Also read for reference:
-```
-apps/sim/lib/webhooks/providers/types.ts            # WebhookProviderHandler interface
-apps/sim/lib/webhooks/providers/utils.ts            # Shared helpers (createHmacVerifier, etc.)
-apps/sim/lib/webhooks/provider-subscription-utils.ts    # Subscription helpers
-apps/sim/lib/webhooks/processor.ts                  # Central webhook processor
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the service's official webhook documentation. This is the **source of truth** for:
-- Webhook event types and payload shapes
-- Signature/auth verification method (HMAC algorithm, header names, secret format)
-- Challenge/verification handshake requirements
-- Webhook subscription API (create/delete endpoints, if applicable)
-- Retry behavior and delivery guarantees
-
-## Step 3: Validate Trigger Definitions
-
-### utils.ts
-- [ ] `{service}TriggerOptions` lists all trigger IDs accurately
-- [ ] `{service}SetupInstructions` provides clear, correct steps for the service
-- [ ] `build{Service}ExtraFields` includes relevant filter/config fields with correct `condition`
-- [ ] Output builders expose all meaningful fields from the webhook payload
-- [ ] Output builders do NOT use `optional: true` or `items` (tool-output-only features)
-- [ ] Nested output objects correctly model the payload structure
-
-### Trigger Files
-- [ ] Exactly one primary trigger has `includeDropdown: true`
-- [ ] All secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper (not hand-rolled subBlocks)
-- [ ] Every trigger's `id` matches the convention `{service}_{event_name}`
-- [ ] Every trigger's `provider` matches the service name used in the handler registry
-- [ ] `index.ts` barrel exports all triggers
-
-### Trigger ↔ Provider Alignment (CRITICAL)
-- [ ] Every trigger ID referenced in `matchEvent` logic exists in `{service}TriggerOptions`
-- [ ] Event matching logic in the provider correctly maps trigger IDs to service event types
-- [ ] Event matching logic in `is{Service}EventMatch` (if exists) correctly identifies events per the API docs
-
-## Step 4: Validate Provider Handler
-
-### Auth Verification
-- [ ] `verifyAuth` correctly validates webhook signatures per the service's documentation
-- [ ] HMAC algorithm matches (SHA-1, SHA-256, SHA-512)
-- [ ] Signature header name matches the API docs exactly
-- [ ] Signature format is handled (raw hex, `sha256=` prefix, base64, etc.)
-- [ ] Uses `safeCompare` for timing-safe comparison (no `===`)
-- [ ] If `webhookSecret` is required, handler rejects when it's missing (fail-closed)
-- [ ] Signature is computed over raw body (not parsed JSON)
-
-### Event Matching
-- [ ] `matchEvent` returns `boolean` (not `NextResponse` or other values)
-- [ ] Challenge/verification events are excluded from matching (e.g., `endpoint.url_validation`)
-- [ ] When `triggerId` is a generic webhook ID, all events pass through
-- [ ] When `triggerId` is specific, only matching events pass
-- [ ] Event matching logic uses dynamic `await import()` for trigger utils (avoids circular deps)
-
-### formatInput (CRITICAL)
-- [ ] Every key in the `formatInput` return matches a key in the trigger `outputs` schema
-- [ ] Every key in the trigger `outputs` schema is populated by `formatInput`
-- [ ] No extra undeclared keys that users can't discover in the UI
-- [ ] No wrapper objects (`webhook: { ... }`, `{service}: { ... }`)
-- [ ] Nested output paths exist at the correct depth (e.g., `resource.id` actually has `resource: { id: ... }`)
-- [ ] `null` is used for missing optional fields (not empty strings or empty objects)
-- [ ] Returns `{ input: { ... } }` — not a bare object
-
-### Idempotency
-- [ ] `extractIdempotencyId` returns a stable, unique key per delivery
-- [ ] Uses provider-specific delivery IDs when available (e.g., `X-Request-Id`, `Linear-Delivery`, `svix-id`)
-- [ ] Falls back to content-based ID (e.g., `${type}:${id}`) when no delivery header exists
-- [ ] Does NOT include timestamps in the idempotency key (would break dedup on retries)
-
-### Challenge Handling (if applicable)
-- [ ] `handleChallenge` correctly implements the service's URL verification handshake
-- [ ] Returns the expected response format per the API docs
-- [ ] Env-backed secrets are resolved via `resolveEnvVarsInObject` if needed
-
-## Step 5: Validate Automatic Subscription Lifecycle
-
-If the service supports programmatic webhook creation:
-
-### createSubscription
-- [ ] Calls the correct API endpoint to create a webhook
-- [ ] Sends the correct event types/filters
-- [ ] Passes the notification URL from `getNotificationUrl(ctx.webhook)`
-- [ ] Returns `{ providerConfigUpdates: { externalId } }` with the external webhook ID
-- [ ] Throws on failure (orchestration handles rollback)
-- [ ] Provides user-friendly error messages (401 → "Invalid API Key", etc.)
-
-### deleteSubscription
-- [ ] Calls the correct API endpoint to delete the webhook
-- [ ] Handles 404 gracefully (webhook already deleted)
-- [ ] Never throws — catches errors and logs non-fatally
-- [ ] Skips gracefully when `apiKey` or `externalId` is missing
-
-### Orchestration Isolation
-- [ ] NO provider-specific logic in `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] All subscription logic lives on the handler (`createSubscription`/`deleteSubscription`)
-
-## Step 6: Validate Registration and Block Wiring
-
-### Trigger Registry (`triggers/registry.ts`)
-- [ ] All triggers are imported and registered
-- [ ] Registry keys match trigger IDs exactly
-- [ ] No orphaned entries (triggers that don't exist)
-
-### Provider Handler Registry (`providers/registry.ts`)
-- [ ] Handler is imported and registered (if handler exists)
-- [ ] Registry key matches the `provider` field on the trigger configs
-- [ ] Entries are in alphabetical order
-
-### Block Wiring (`blocks/blocks/{service}.ts`)
-- [ ] Block has `triggers.enabled: true`
-- [ ] `triggers.available` lists all trigger IDs
-- [ ] All trigger subBlocks are spread into `subBlocks`: `...getTrigger('id').subBlocks`
-- [ ] No trigger IDs in `triggers.available` that aren't in the registry
-- [ ] No trigger subBlocks spread that aren't in `triggers.available`
-
-## Step 7: Validate Security
-
-- [ ] Webhook secrets are never logged (not even at debug level)
-- [ ] Auth verification runs before any event processing
-- [ ] No secret comparison uses `===` (must use `safeCompare` or `crypto.timingSafeEqual`)
-- [ ] Timestamp/replay protection is reasonable (not too tight for retries, not too loose for security)
-- [ ] Raw body is used for signature verification (not re-serialized JSON)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (runtime errors, security issues, or data loss):
-- Wrong HMAC algorithm or header name
-- `formatInput` keys don't match trigger `outputs`
-- Missing `verifyAuth` when the service sends signed webhooks
-- `matchEvent` returns non-boolean values
-- Provider-specific logic leaking into shared orchestration files
-- Trigger IDs mismatch between trigger files, registry, and block
-- `createSubscription` calling wrong API endpoint
-- Auth comparison using `===` instead of `safeCompare`
-
-**Warning** (convention violations or usability issues):
-- Missing `extractIdempotencyId` when the service provides delivery IDs
-- Timestamps in idempotency keys (breaks dedup on retries)
-- Missing challenge handling when the service requires URL verification
-- Output schema missing fields that `formatInput` returns (undiscoverable data)
-- Overly tight timestamp skew window that rejects legitimate retries
-- `matchEvent` not filtering challenge/verification events
-- Setup instructions missing important steps
-
-**Suggestion** (minor improvements):
-- More specific output field descriptions
-- Additional output fields that could be exposed
-- Better error messages in `createSubscription`
-- Logging improvements
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run type-check` passes
-2. Re-read all modified files to verify fixes are correct
-3. Provider handler tests pass (if they exist): `bun test {service}`
-
-## Checklist Summary
-
-- [ ] Read all trigger files, provider handler, types, registries, and block
-- [ ] Pulled and read official webhook/API documentation
-- [ ] Validated trigger definitions: options, instructions, extra fields, outputs
-- [ ] Validated primary/secondary trigger distinction (`includeDropdown`)
-- [ ] Validated provider handler: auth, matchEvent, formatInput, idempotency
-- [ ] Validated output alignment: every `outputs` key ↔ every `formatInput` key
-- [ ] Validated subscription lifecycle: createSubscription, deleteSubscription, no shared-file edits
-- [ ] Validated registration: trigger registry, handler registry, block wiring
-- [ ] Validated security: safe comparison, no secret logging, replay protection
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] `bun run type-check` passes after fixes

.claude/commands/you-might-not-need-a-callback.md

@@ -1,52 +0,0 @@
----
-description: Analyze and fix useCallback anti-patterns in your code
-argument-hint: [scope] [fix=true|false]
----
-
-# You Might Not Need a Callback
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://react.dev/reference/react/useCallback — official docs on when useCallback is actually needed
-
-## The one rule that matters
-
-`useCallback` is only useful when **something observes the reference**. Ask: does anything care if this function gets a new identity on re-render?
-
-Observers that care about reference stability:
-- A `useEffect` that lists the function in its deps array
-- A `useMemo` that lists the function in its deps array
-- Another `useCallback` that lists the function in its deps array
-- A child component wrapped in `React.memo` that receives the function as a prop
-
-If none of those apply — if the function is only called inline, or passed to a non-memoized child, or assigned to a native element event — the reference is unobserved and `useCallback` adds overhead with zero benefit.
-
-## Anti-patterns to detect
-
-1. **No observer tracks the reference**: The function is only called inline in the same component, or passed to a non-memoized child, or used as a native element handler (`<button onClick={fn}>`). Nothing re-runs or bails out based on reference identity. Remove `useCallback`.
-2. **useCallback with deps that change every render**: If a dep is a plain object/array created inline, or state that changes on every interaction, memoization buys nothing — the function gets a new identity anyway.
-3. **useCallback on handlers passed only to native elements**: `<button onClick={fn}>` — React never does reference equality on native element props. No benefit.
-4. **useCallback wrapping functions that return new objects/arrays**: Stable function identity, unstable return value — memoization is at the wrong level. Use `useMemo` on the return value instead, or restructure.
-5. **useCallback with empty deps when deps are needed**: Stale closure — reads initial values forever. This is a correctness bug, not just a performance issue.
-6. **Pairing useCallback + React.memo on trivially cheap renders**: If the child renders in < 1ms and re-renders rarely, the memo infrastructure costs more than it saves.
-
-## Patterns that ARE correct — do not flag
-
-- `useCallback` whose result is in a `useEffect` dep array — prevents the effect from re-running on every render
-- `useCallback` whose result is in a `useMemo` dep array — prevents the memo from recomputing on every render
-- `useCallback` whose result is a dep of another `useCallback` — stabilises a callback chain
-- `useCallback` passed to a `React.memo`-wrapped child — the whole point of the pattern
-- This codebase's ref pattern: `useRef` + callback with empty deps that reads the ref inside — correct, do not flag
-
-## Steps
-
-1. Read the reference above
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/commands/you-might-not-need-a-memo.md

@@ -1,33 +0,0 @@
----
-description: Analyze and fix useMemo/React.memo anti-patterns in your code
-argument-hint: [scope] [fix=true|false]
----
-
-# You Might Not Need a Memo
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://overreacted.io/before-you-memo/ — two techniques to avoid memo entirely
-
-## Anti-patterns to detect
-
-1. **State can be moved down instead of memoizing**: Move state into a smaller child so the slow component stops re-rendering without memo.
-2. **Children can be lifted up**: Extract stateful part, pass expensive subtree as `children` — children as props don't re-render when parent state changes.
-3. **useMemo on cheap computations**: Small array filters, string concat, arithmetic don't need memoization.
-4. **useMemo with constantly-changing deps**: Deps change every render = useMemo does nothing.
-5. **useMemo to stabilize props for non-memoized children**: If the child isn't wrapped in React.memo, stable references don't matter.
-6. **React.memo on components that always receive new props**: Fix the parent instead.
-7. **useMemo for derived state**: Just compute inline during render.
-
-## Steps
-
-1. Read the reference above
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/commands/you-might-not-need-an-effect.md

@@ -1,17 +0,0 @@
----
-description: Analyze and fix useEffect anti-patterns in your code
-argument-hint: [scope] [fix=true|false]
----
-
-# You Might Not Need an Effect
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-Steps:
-1. Read https://react.dev/learn/you-might-not-need-an-effect to understand the guidelines
-2. Analyze the specified scope for useEffect anti-patterns
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/commands/you-might-not-need-state.md

@@ -1,38 +0,0 @@
----
-description: Analyze and fix unnecessary useState, derived state, and server-state-in-local-state anti-patterns
-argument-hint: [scope] [fix=true|false]
----
-
-# You Might Not Need State
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query for all server state and Zustand for client-only global state. useState should only be used for ephemeral UI concerns (open/closed, hover, local form input). Server data should never be copied into useState or Zustand — React Query is the single source of truth.
-
-## References
-
-Read these before analyzing:
-1. https://react.dev/learn/choosing-the-state-structure — 5 principles for structuring state
-2. https://tkdodo.eu/blog/dont-over-use-state — never store derived/computed values in state
-3. https://tkdodo.eu/blog/putting-props-to-use-state — never mirror props into state via useEffect
-
-## Anti-patterns to detect
-
-1. **Derived state stored in useState**: If a value can be computed from props, other state, or query data, compute it inline during render instead of storing it in state.
-2. **Server state copied into useState**: Never `useState` + `useEffect` to sync React Query data into local state. Use query data directly. The only exception is forms where users edit server data.
-3. **Props mirrored into state**: Never `useState(prop)` + `useEffect(() => setState(prop))`. Use the prop directly, or use a key to reset component state.
-4. **Chained useEffect state updates**: Never chain Effects that set state to trigger other Effects. Calculate all derived values in the event handler or inline during render.
-5. **Storing objects when an ID suffices**: Store `selectedId` not a copy of the selected object. Derive the object: `items.find(i => i.id === selectedId)`.
-6. **State that duplicates Zustand or React Query**: If the data already lives in a store or query cache, don't create a parallel useState.
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.claude/rules/constitution.md

@@ -1,71 +0,0 @@
-# Sim — Language & Positioning
-
-When editing user-facing copy (landing pages, docs, metadata, marketing), follow these rules.
-
-## Identity
-
-Sim is the **AI workspace** where teams build and run AI agents. Not a workflow tool, not an agent framework, not an automation platform.
-
-**Short definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents.
-
-**Full definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. Connect 1,000+ integrations and every major LLM to create agents that automate real work — visually, conversationally, or with code.
-
-## Audience
-
-**Primary:** Teams building AI agents for their organization — IT, operations, and technical teams who need governance, security, lifecycle management, and collaboration.
-
-**Secondary:** Individual builders and developers who care about speed, flexibility, and open source.
-
-## Required Language
-
-| Concept | Use | Never use |
-|---------|-----|-----------|
-| The product | "AI workspace" | "workflow tool", "automation platform", "agent framework" |
-| Building | "build agents", "create agents" | "create workflows" (unless describing the workflow module specifically) |
-| Visual builder | "workflow builder" or "visual builder" | "canvas", "graph editor" |
-| Mothership | "Mothership" (capitalized) | "chat", "AI assistant", "copilot" |
-| Deployment | "deploy", "ship" | "publish", "activate" |
-| Audience | "teams", "builders" | "users", "customers" (in marketing copy) |
-| What agents do | "automate real work" | "automate tasks", "automate workflows" |
-| Our advantage | "open-source AI workspace" | "open-source platform" |
-
-## Tone
-
-- **Direct.** Short sentences. Active voice. Lead with what it does.
-- **Concrete.** Name specific things — "Slack bots, compliance agents, data pipelines" — not abstractions.
-- **Confident, not loud.** No exclamation marks or superlatives.
-- **Simple.** If a 16-year-old can't understand the sentence, rewrite it.
-
-## Claim Hierarchy
-
-When describing Sim, always lead with the most differentiated claim:
-
-1. **What it is:** "The AI workspace for teams"
-2. **What you do:** "Build, deploy, and manage AI agents"
-3. **How:** "Visually, conversationally, or with code"
-4. **Scale:** "1,000+ integrations, every major LLM"
-5. **Trust:** "Open source. SOC2. Trusted by 100,000+ builders."
-
-## Module Descriptions
-
-| Module | One-liner |
-|--------|-----------|
-| **Mothership** | Your AI command center. Build and manage everything in natural language. |
-| **Workflows** | The visual builder. Connect blocks, models, and integrations into agent logic. |
-| **Knowledge Base** | Your agents' memory. Upload docs, sync sources, build vector databases. |
-| **Tables** | A database, built in. Store, query, and wire structured data into agent runs. |
-| **Files** | Upload, create, and share. One store for your team and every agent. |
-| **Logs** | Full visibility, every run. Trace execution block by block. |
-
-## What We Never Say
-
-- Never call Sim "just a workflow tool"
-- Never compare only on integration count — we win on AI-native capabilities
-- Never use "no-code" as the primary descriptor — say "visually, conversationally, or with code"
-- Never promise unshipped features
-- Never use jargon ("RAG", "vector database", "MCP") without plain-English explanation on public pages
-- Avoid "agentic workforce" as a primary term — use "AI agents"
-
-## Vision
-
-Sim becomes the default environment where teams build AI agents — not a tool you visit for one task, but a workspace you live in. Workflows are one module; Mothership is another. The workspace is the constant; the interface adapts.

.claude/rules/emcn-components.md

@@ -1,35 +0,0 @@
----
-paths:
-  - "apps/sim/components/emcn/**"
----
-
-# EMCN Components
-
-Import from `@/components/emcn`, never from subpaths (except CSS files).
-
-## CVA vs Direct Styles
-
-**Use CVA when:** 2+ variants (primary/secondary, sm/md/lg)
-
-```tsx
-const buttonVariants = cva('base-classes', {
-  variants: { variant: { default: '...', primary: '...' } }
-})
-export { Button, buttonVariants }
-```
-
-**Use direct className when:** Single consistent style, no variations
-
-```tsx
-function Label({ className, ...props }) {
-  return <Primitive className={cn('style-classes', className)} {...props} />
-}
-```
-
-## Rules
-
-- Use Radix UI primitives for accessibility
-- Export component and variants (if using CVA)
-- TSDoc with usage examples
-- Consistent tokens: `font-medium`, `text-[12px]`, `rounded-[4px]`
-- `transition-colors` for hover states

.claude/rules/global.md

@@ -1,58 +0,0 @@
-# Global Standards
-
-## Logging
-Import `createLogger` from `@sim/logger`. Use `logger.info`, `logger.warn`, `logger.error` instead of `console.log`. Inside API routes wrapped with `withRouteHandler`, loggers automatically include the request ID.
-
-## API Route Handlers
-All API route handlers must be wrapped with `withRouteHandler` from `@/lib/core/utils/with-route-handler`. Never export a bare `async function GET/POST/...` — always use `export const METHOD = withRouteHandler(...)`.
-
-## Comments
-Use TSDoc for documentation. No `====` separators. No non-TSDoc comments.
-
-## Styling
-Never update global styles. Keep all styling local to components.
-
-## ID Generation
-Never use `crypto.randomUUID()`, `nanoid`, or the `uuid` package directly. Use the utilities from `@sim/utils/id`:
-
-- `generateId()` — UUID v4, use by default
-- `generateShortId(size?)` — short URL-safe ID (default 21 chars), for compact identifiers
-
-Both use `crypto.getRandomValues()` under the hood and work in all contexts including non-secure (HTTP) browsers.
-
-```typescript
-// ✗ Bad
-import { nanoid } from 'nanoid'
-import { v4 as uuidv4 } from 'uuid'
-const id = crypto.randomUUID()
-
-// ✓ Good
-import { generateId, generateShortId } from '@sim/utils/id'
-const uuid = generateId()
-const shortId = generateShortId()
-const tiny = generateShortId(8)
-```
-
-## Common Utilities
-Use shared helpers from `@sim/utils` instead of writing inline implementations:
-
-- `sleep(ms)` — async delay. Never write `new Promise(resolve => setTimeout(resolve, ms))`
-- `toError(value)` — normalize unknown caught values to `Error`. Never write `e instanceof Error ? e : new Error(String(e))`
-- `toError(value).message` — get error message safely. Never write `e instanceof Error ? e.message : String(e)`
-
-```typescript
-// ✗ Bad
-await new Promise(resolve => setTimeout(resolve, 1000))
-const msg = error instanceof Error ? error.message : String(error)
-const err = error instanceof Error ? error : new Error(String(error))
-
-// ✓ Good
-import { sleep } from '@sim/utils/helpers'
-import { toError } from '@sim/utils/errors'
-await sleep(1000)
-const msg = toError(error).message
-const err = toError(error)
-```
-
-## Package Manager
-Use `bun` and `bunx`, not `npm` and `npx`.

.claude/rules/landing-seo-geo.md

@@ -1,26 +0,0 @@
----
-paths:
-  - "apps/sim/app/(home)/**/*.tsx"
----
-
-# Landing Page — SEO / GEO
-
-## SEO
-
-- One `<h1>` per page, in Hero only — never add another.
-- Strict heading hierarchy: H1 (Hero) → H2 (section titles) → H3 (feature names).
-- Every section: `<section id="…" aria-labelledby="…-heading">`.
-- Decorative/animated elements: `aria-hidden="true"`.
-- All internal routes use Next.js `<Link>` (crawlable). External links get `rel="noopener noreferrer"`.
-- Navbar is a Server Component (no `'use client'`) for immediate crawlability. Logo `<Image>` has `priority` (LCP element).
-- Navbar `<nav>` carries `SiteNavigationElement` schema.org markup.
-- Feature lists must stay in sync with `WebApplication.featureList` in `structured-data.tsx`.
-
-## GEO (Generative Engine Optimisation)
-
-- **Answer-first pattern**: each section's H2 + subtitle should directly answer a user question (e.g. "What is Sim?", "How fast can I deploy?").
-- **Atomic answer blocks**: each feature / template card should be independently extractable by an AI summariser.
-- **Entity consistency**: always write "Sim" by name — never "the platform" or "our tool".
-- **Keyword density**: first 150 visible chars of Hero must name "Sim", "AI agents", "agentic workflows".
-- **sr-only summaries**: Hero and Templates each have a `<p className="sr-only">` (~50 words) as an atomic product/catalog summary for AI citation.
-- **Specific numbers**: prefer concrete figures ("1,000+ integrations", "15+ AI providers") over vague claims.

.claude/rules/sim-architecture.md

@@ -1,56 +0,0 @@
----
-paths:
-  - "apps/sim/**"
----
-
-# Sim App Architecture
-
-## Core Principles
-1. **Single Responsibility**: Each component, hook, store has one clear purpose
-2. **Composition Over Complexity**: Break down complex logic into smaller pieces
-3. **Type Safety First**: TypeScript interfaces for all props, state, return types
-4. **Predictable State**: Zustand for global state, useState for UI-only concerns
-
-## Root-Level Structure
-
-```
-apps/sim/
-├── app/                 # Next.js app router (pages, API routes)
-├── blocks/              # Block definitions and registry
-├── components/          # Shared UI (emcn/, ui/)
-├── executor/            # Workflow execution engine
-├── hooks/               # Shared hooks (queries/, selectors/)
-├── lib/                 # App-wide utilities
-├── providers/           # LLM provider integrations
-├── stores/              # Zustand stores
-├── tools/               # Tool definitions
-└── triggers/            # Trigger definitions
-```
-
-## Feature Organization
-
-Features live under `app/workspace/[workspaceId]/`:
-
-```
-feature/
-├── components/          # Feature components
-├── hooks/               # Feature-scoped hooks
-├── utils/               # Feature-scoped utilities (2+ consumers)
-├── feature.tsx          # Main component
-└── page.tsx             # Next.js page entry
-```
-
-## Naming Conventions
-- **Components**: PascalCase (`WorkflowList`)
-- **Hooks**: `use` prefix (`useWorkflowOperations`)
-- **Files**: kebab-case (`workflow-list.tsx`)
-- **Stores**: `stores/feature/store.ts`
-- **Constants**: SCREAMING_SNAKE_CASE
-- **Interfaces**: PascalCase with suffix (`WorkflowListProps`)
-
-## Utils Rules
-
-- **Never create `utils.ts` for single consumer** - inline it
-- **Create `utils.ts` when** 2+ files need the same helper
-- **Check existing sources** before duplicating (`lib/` has many utilities)
-- **Location**: `lib/` (app-wide) → `feature/utils/` (feature-scoped) → inline (single-use)

.claude/rules/sim-components.md

@@ -1,48 +0,0 @@
----
-paths:
-  - "apps/sim/**/*.tsx"
----
-
-# Component Patterns
-
-## Structure Order
-
-```typescript
-'use client' // Only if using hooks
-
-// Imports (external → internal)
-// Constants at module level
-const CONFIG = { SPACING: 8 } as const
-
-// Props interface
-interface ComponentProps {
-  requiredProp: string
-  optionalProp?: boolean
-}
-
-export function Component({ requiredProp, optionalProp = false }: ComponentProps) {
-  // a. Refs
-  // b. External hooks (useParams, useRouter)
-  // c. Store hooks
-  // d. Custom hooks
-  // e. Local state
-  // f. useMemo
-  // g. useCallback
-  // h. useEffect
-  // i. Return JSX
-}
-```
-
-## Rules
-
-1. `'use client'` only when using React hooks
-2. Always define props interface
-3. Extract constants with `as const`
-4. Semantic HTML (`aside`, `nav`, `article`)
-5. Optional chain callbacks: `onAction?.(id)`
-
-## Component Extraction
-
-**Extract when:** 50+ lines, used in 2+ files, or has own state/logic
-
-**Keep inline when:** < 10 lines, single use, purely presentational

.claude/rules/sim-hooks.md

@@ -1,55 +0,0 @@
----
-paths:
-  - "apps/sim/**/use-*.ts"
-  - "apps/sim/**/hooks/**/*.ts"
----
-
-# Hook Patterns
-
-## Structure
-
-```typescript
-interface UseFeatureProps {
-  id: string
-  onSuccess?: (result: Result) => void
-}
-
-export function useFeature({ id, onSuccess }: UseFeatureProps) {
-  // 1. Refs for stable dependencies
-  const idRef = useRef(id)
-  const onSuccessRef = useRef(onSuccess)
-
-  // 2. State
-  const [data, setData] = useState<Data | null>(null)
-  const [isLoading, setIsLoading] = useState(false)
-
-  // 3. Sync refs
-  useEffect(() => {
-    idRef.current = id
-    onSuccessRef.current = onSuccess
-  }, [id, onSuccess])
-
-  // 4. Operations (useCallback with empty deps when using refs)
-  const fetchData = useCallback(async () => {
-    setIsLoading(true)
-    try {
-      const result = await fetch(`/api/${idRef.current}`).then(r => r.json())
-      setData(result)
-      onSuccessRef.current?.(result)
-    } finally {
-      setIsLoading(false)
-    }
-  }, [])
-
-  return { data, isLoading, fetchData }
-}
-```
-
-## Rules
-
-1. Single responsibility per hook
-2. Props interface required
-3. Refs for stable callback dependencies
-4. Wrap returned functions in useCallback
-5. Always try/catch async operations
-6. Track loading/error states

.claude/rules/sim-imports.md

@@ -1,62 +0,0 @@
----
-paths:
-  - "apps/sim/**/*.ts"
-  - "apps/sim/**/*.tsx"
----
-
-# Import Patterns
-
-## Absolute Imports
-
-**Always use absolute imports.** Never use relative imports.
-
-```typescript
-// ✓ Good
-import { useWorkflowStore } from '@/stores/workflows/store'
-import { Button } from '@/components/ui/button'
-
-// ✗ Bad
-import { useWorkflowStore } from '../../../stores/workflows/store'
-```
-
-## Barrel Exports
-
-Use barrel exports (`index.ts`) when a folder has 3+ exports. Import from barrel, not individual files.
-
-```typescript
-// ✓ Good
-import { Dashboard, Sidebar } from '@/app/workspace/[workspaceId]/logs/components'
-
-// ✗ Bad
-import { Dashboard } from '@/app/workspace/[workspaceId]/logs/components/dashboard/dashboard'
-```
-
-## No Re-exports
-
-Do not re-export from non-barrel files. Import directly from the source.
-
-```typescript
-// ✓ Good - import from where it's declared
-import { CORE_TRIGGER_TYPES } from '@/stores/logs/filters/types'
-
-// ✗ Bad - re-exporting in utils.ts then importing from there
-import { CORE_TRIGGER_TYPES } from '@/app/workspace/.../utils'
-```
-
-## Import Order
-
-1. React/core libraries
-2. External libraries
-3. UI components (`@/components/emcn`, `@/components/ui`)
-4. Utilities (`@/lib/...`)
-5. Stores (`@/stores/...`)
-6. Feature imports
-7. CSS imports
-
-## Type Imports
-
-Use `type` keyword for type-only imports:
-
-```typescript
-import type { WorkflowLog } from '@/stores/logs/types'
-```

.claude/rules/sim-integrations.md

@@ -1,287 +0,0 @@
----
-paths:
-  - "apps/sim/tools/**"
-  - "apps/sim/blocks/**"
-  - "apps/sim/triggers/**"
----
-
-# Adding Integrations
-
-## Overview
-
-Adding a new integration typically requires:
-1. **Tools** - API operations (`tools/{service}/`)
-2. **Block** - UI component (`blocks/blocks/{service}.ts`)
-3. **Icon** - SVG icon (`components/icons.tsx`)
-4. **Trigger** (optional) - Webhooks/polling (`triggers/{service}/`)
-
-Always look up the service's API docs first.
-
-## 1. Tools (`tools/{service}/`)
-
-```
-tools/{service}/
-├── index.ts           # Export all tools
-├── types.ts           # Params/response types
-├── {action}.ts        # Individual tool (e.g., send_message.ts)
-└── ...
-```
-
-**Tool file structure:**
-
-```typescript
-// tools/{service}/{action}.ts
-import type { {Service}Params, {Service}Response } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-export const {service}{Action}Tool: ToolConfig<{Service}Params, {Service}Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: 'What this tool does',
-  version: '1.0.0',
-  oauth: { required: true, provider: '{service}' }, // if OAuth
-  params: { /* param definitions */ },
-  request: {
-    url: '/api/tools/{service}/{action}',
-    method: 'POST',
-    headers: () => ({ 'Content-Type': 'application/json' }),
-    body: (params) => ({ ...params }),
-  },
-  transformResponse: async (response) => {
-    const data = await response.json()
-    if (!data.success) throw new Error(data.error)
-    return { success: true, output: data.output }
-  },
-  outputs: { /* output definitions */ },
-}
-```
-
-**Register in `tools/registry.ts`:**
-
-```typescript
-import { {service}{Action}Tool } from '@/tools/{service}'
-// Add to registry object
-{service}_{action}: {service}{Action}Tool,
-```
-
-## 2. Block (`blocks/blocks/{service}.ts`)
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import type { {Service}Response } from '@/tools/{service}/types'
-
-export const {Service}Block: BlockConfig<{Service}Response> = {
-  type: '{service}',
-  name: '{Service}',
-  description: 'Short description',
-  longDescription: 'Detailed description',
-  category: 'tools',
-  bgColor: '#hexcolor',
-  icon: {Service}Icon,
-  subBlocks: [ /* see SubBlock Properties below */ ],
-  tools: {
-    access: ['{service}_{action}', ...],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-      params: (params) => ({ ...params }),
-    },
-  },
-  inputs: { /* input definitions */ },
-  outputs: { /* output definitions */ },
-}
-```
-
-### SubBlock Properties
-
-```typescript
-{
-  id: 'fieldName',           // Unique identifier
-  title: 'Field Label',      // UI label
-  type: 'short-input',       // See SubBlock Types below
-  placeholder: 'Hint text',
-  required: true,            // See Required below
-  condition: { ... },        // See Condition below
-  dependsOn: ['otherField'], // See DependsOn below
-  mode: 'basic',             // 'basic' | 'advanced' | 'both' | 'trigger'
-}
-```
-
-**SubBlock Types:** `short-input`, `long-input`, `dropdown`, `code`, `switch`, `slider`, `oauth-input`, `channel-selector`, `user-selector`, `file-upload`, etc.
-
-### `condition` - Show/hide based on another field
-
-```typescript
-// Show when operation === 'send'
-condition: { field: 'operation', value: 'send' }
-
-// Show when operation is 'send' OR 'read'
-condition: { field: 'operation', value: ['send', 'read'] }
-
-// Show when operation !== 'send'
-condition: { field: 'operation', value: 'send', not: true }
-
-// Complex: NOT in list AND another condition
-condition: {
-  field: 'operation',
-  value: ['list_channels', 'list_users'],
-  not: true,
-  and: { field: 'destinationType', value: 'dm', not: true }
-}
-```
-
-### `required` - Field validation
-
-```typescript
-// Always required
-required: true
-
-// Conditionally required (same syntax as condition)
-required: { field: 'operation', value: 'send' }
-```
-
-### `dependsOn` - Clear field when dependencies change
-
-```typescript
-// Clear when credential changes
-dependsOn: ['credential']
-
-// Clear when authMethod changes AND (credential OR botToken) changes
-dependsOn: { all: ['authMethod'], any: ['credential', 'botToken'] }
-```
-
-### `mode` - When to show field
-
-- `'basic'` - Only in basic mode (default UI)
-- `'advanced'` - Only in advanced mode (manual input)
-- `'both'` - Show in both modes (default)
-- `'trigger'` - Only when block is used as trigger
-
-### `canonicalParamId` - Link basic/advanced alternatives
-
-Use to map multiple UI inputs to a single logical parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'fileSelector',
-  type: 'file-selector',
-  mode: 'basic',
-  canonicalParamId: 'fileId',
-  required: true,
-},
-// Advanced mode: Manual input
-{
-  id: 'manualFileId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'fileId',
-  required: true,
-},
-```
-
-**Critical Rules:**
-- `canonicalParamId` must NOT match any subblock's `id`
-- `canonicalParamId` must be unique per operation/condition context
-- **Required consistency:** All subblocks in a canonical group must have the same `required` status
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs
-- **Params function:** Must use canonical param IDs (raw IDs are deleted after canonical transformation)
-
-**Register in `blocks/registry.ts`:**
-
-```typescript
-import { {Service}Block } from '@/blocks/blocks/{service}'
-// Add to registry object (alphabetically)
-{service}: {Service}Block,
-```
-
-## 3. Icon (`components/icons.tsx`)
-
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg {...props} viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
-      {/* SVG path from service's brand assets */}
-    </svg>
-  )
-}
-```
-
-## 4. Trigger (`triggers/{service}/`) - Optional
-
-```
-triggers/{service}/
-├── index.ts           # Export all triggers
-├── webhook.ts         # Webhook handler
-├── utils.ts           # Shared utilities
-└── {event}.ts         # Specific event handlers
-```
-
-**Register in `triggers/registry.ts`:**
-
-```typescript
-import { {service}WebhookTrigger } from '@/triggers/{service}'
-// Add to TRIGGER_REGISTRY
-{service}_webhook: {service}WebhookTrigger,
-```
-
-## File Handling
-
-When integrations handle file uploads/downloads, use `UserFile` objects consistently.
-
-### File Input (Uploads)
-
-1. **Block subBlocks:** Use basic/advanced mode pattern with `canonicalParamId`
-2. **Normalize in block config:** Use `normalizeFileInput` from `@/blocks/utils`
-3. **Internal API route:** Create route that uses `downloadFileFromStorage` to get file content
-4. **Tool routes to internal API:** Don't call external APIs directly with files
-
-```typescript
-// In block tools.config:
-import { normalizeFileInput } from '@/blocks/utils'
-
-const normalizedFile = normalizeFileInput(
-  params.uploadFile || params.fileRef || params.fileContent,
-  { single: true }
-)
-if (normalizedFile) params.file = normalizedFile
-```
-
-### File Output (Downloads)
-
-Use `FileToolProcessor` in tool `transformResponse` to store files:
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-const processor = new FileToolProcessor(context)
-const file = await processor.processFileData({
-  data: base64Content,
-  mimeType: 'application/pdf',
-  filename: 'doc.pdf',
-})
-```
-
-### Key Helpers
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-
-## Checklist
-
-- [ ] Look up API docs for the service
-- [ ] Create `tools/{service}/types.ts` with proper types
-- [ ] Create tool files for each operation
-- [ ] Create `tools/{service}/index.ts` barrel export
-- [ ] Register tools in `tools/registry.ts`
-- [ ] Add icon to `components/icons.tsx`
-- [ ] Create block in `blocks/blocks/{service}.ts`
-- [ ] Register block in `blocks/registry.ts`
-- [ ] (Optional) Create triggers in `triggers/{service}/`
-- [ ] (Optional) Register triggers in `triggers/registry.ts`
-- [ ] (If file uploads) Create internal API route with `downloadFileFromStorage`
-- [ ] (If file uploads) Use `normalizeFileInput` in block config

.claude/rules/sim-queries.md

@@ -1,126 +0,0 @@
----
-paths:
-  - "apps/sim/hooks/queries/**/*.ts"
----
-
-# React Query Patterns
-
-All React Query hooks live in `hooks/queries/`. All server state must go through React Query — never use `useState` + `fetch` in components for data fetching or mutations.
-
-## Query Key Factory
-
-Every query file defines a hierarchical keys factory with an `all` root key and intermediate plural keys for prefix-level invalidation:
-
-```typescript
-export const entityKeys = {
-  all: ['entity'] as const,
-  lists: () => [...entityKeys.all, 'list'] as const,
-  list: (workspaceId?: string) => [...entityKeys.lists(), workspaceId ?? ''] as const,
-  details: () => [...entityKeys.all, 'detail'] as const,
-  detail: (id?: string) => [...entityKeys.details(), id ?? ''] as const,
-}
-```
-
-Never use inline query keys — always use the factory.
-
-## File Structure
-
-```typescript
-// 1. Query keys factory
-// 2. Types (if needed)
-// 3. Private fetch functions (accept signal parameter)
-// 4. Exported hooks
-```
-
-## Query Hook
-
-- Every `queryFn` must destructure and forward `signal` for request cancellation
-- Every query must have an explicit `staleTime`
-- Use `keepPreviousData` only on variable-key queries (where params change), never on static keys
-
-```typescript
-async function fetchEntities(workspaceId: string, signal?: AbortSignal) {
-  const response = await fetch(`/api/entities?workspaceId=${workspaceId}`, { signal })
-  if (!response.ok) throw new Error('Failed to fetch entities')
-  return response.json()
-}
-
-export function useEntityList(workspaceId?: string, options?: { enabled?: boolean }) {
-  return useQuery({
-    queryKey: entityKeys.list(workspaceId),
-    queryFn: ({ signal }) => fetchEntities(workspaceId as string, signal),
-    enabled: Boolean(workspaceId) && (options?.enabled ?? true),
-    staleTime: 60 * 1000,
-    placeholderData: keepPreviousData, // OK: workspaceId varies
-  })
-}
-```
-
-## Mutation Hook
-
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- Invalidation must cover all affected query key prefixes (lists, details, related views)
-
-```typescript
-export function useCreateEntity() {
-  const queryClient = useQueryClient()
-  return useMutation({
-    mutationFn: async (variables) => { /* fetch POST */ },
-    onSuccess: () => {
-      queryClient.invalidateQueries({ queryKey: entityKeys.lists() })
-    },
-  })
-}
-```
-
-## Optimistic Updates
-
-For optimistic mutations, use `onSettled` (not `onSuccess`) for cache reconciliation — `onSettled` fires on both success and error, ensuring the cache is always reconciled with the server.
-
-```typescript
-export function useUpdateEntity() {
-  const queryClient = useQueryClient()
-  return useMutation({
-    mutationFn: async (variables) => { /* ... */ },
-    onMutate: async (variables) => {
-      await queryClient.cancelQueries({ queryKey: entityKeys.detail(variables.id) })
-      const previous = queryClient.getQueryData(entityKeys.detail(variables.id))
-      queryClient.setQueryData(entityKeys.detail(variables.id), /* optimistic value */)
-      return { previous }
-    },
-    onError: (_err, variables, context) => {
-      queryClient.setQueryData(entityKeys.detail(variables.id), context?.previous)
-    },
-    onSettled: (_data, _error, variables) => {
-      queryClient.invalidateQueries({ queryKey: entityKeys.lists() })
-      queryClient.invalidateQueries({ queryKey: entityKeys.detail(variables.id) })
-    },
-  })
-}
-```
-
-For optimistic mutations syncing with Zustand, use `createOptimisticMutationHandlers` from `@/hooks/queries/utils/optimistic-mutation`.
-
-## useCallback Dependencies
-
-Never include mutation objects (e.g., `createEntity`) in `useCallback` dependency arrays — the mutation object is not referentially stable and changes on every state update. The `.mutate()` and `.mutateAsync()` functions are stable in TanStack Query v5.
-
-```typescript
-// ✗ Bad — causes unnecessary recreations
-const handler = useCallback(() => {
-  createEntity.mutate(data)
-}, [createEntity]) // unstable reference
-
-// ✓ Good — omit from deps, mutate is stable
-const handler = useCallback(() => {
-  createEntity.mutate(data)
-  // eslint-disable-next-line react-hooks/exhaustive-deps
-}, [data])
-```
-
-## Naming
-
-- **Keys**: `entityKeys`
-- **Query hooks**: `useEntity`, `useEntityList`
-- **Mutation hooks**: `useCreateEntity`, `useUpdateEntity`, `useDeleteEntity`
-- **Fetch functions**: `fetchEntity`, `fetchEntities` (private)

.claude/rules/sim-stores.md

@@ -1,71 +0,0 @@
----
-paths:
-  - "apps/sim/**/store.ts"
-  - "apps/sim/**/stores/**/*.ts"
----
-
-# Zustand Store Patterns
-
-Stores live in `stores/`. Complex stores split into `store.ts` + `types.ts`.
-
-## Basic Store
-
-```typescript
-import { create } from 'zustand'
-import { devtools } from 'zustand/middleware'
-import type { FeatureState } from '@/stores/feature/types'
-
-const initialState = { items: [] as Item[], activeId: null as string | null }
-
-export const useFeatureStore = create<FeatureState>()(
-  devtools(
-    (set, get) => ({
-      ...initialState,
-      setItems: (items) => set({ items }),
-      addItem: (item) => set((state) => ({ items: [...state.items, item] })),
-      reset: () => set(initialState),
-    }),
-    { name: 'feature-store' }
-  )
-)
-```
-
-## Persisted Store
-
-```typescript
-import { create } from 'zustand'
-import { persist } from 'zustand/middleware'
-
-export const useFeatureStore = create<FeatureState>()(
-  persist(
-    (set) => ({
-      width: 300,
-      setWidth: (width) => set({ width }),
-      _hasHydrated: false,
-      setHasHydrated: (v) => set({ _hasHydrated: v }),
-    }),
-    {
-      name: 'feature-state',
-      partialize: (state) => ({ width: state.width }),
-      onRehydrateStorage: () => (state) => state?.setHasHydrated(true),
-    }
-  )
-)
-```
-
-## Rules
-
-1. Use `devtools` middleware (named stores)
-2. Use `persist` only when data should survive reload
-3. `partialize` to persist only necessary state
-4. `_hasHydrated` pattern for persisted stores needing hydration tracking
-5. Immutable updates only
-6. `set((state) => ...)` when depending on previous state
-7. Provide `reset()` action
-
-## Outside React
-
-```typescript
-const items = useFeatureStore.getState().items
-useFeatureStore.setState({ items: newItems })
-```

.claude/rules/sim-styling.md

@@ -1,41 +0,0 @@
----
-paths:
-  - "apps/sim/**/*.tsx"
-  - "apps/sim/**/*.css"
----
-
-# Styling Rules
-
-## Tailwind
-
-1. **No inline styles** - Use Tailwind classes
-2. **No duplicate dark classes** - Skip `dark:` when value matches light mode
-3. **Exact values** - `text-[14px]`, `h-[26px]`
-4. **Transitions** - `transition-colors` for interactive states
-
-## Conditional Classes
-
-```typescript
-import { cn } from '@/lib/utils'
-
-<div className={cn(
-  'base-classes',
-  isActive && 'active-classes',
-  disabled ? 'opacity-60' : 'hover:bg-accent'
-)} />
-```
-
-## CSS Variables
-
-For dynamic values (widths, heights) synced with stores:
-
-```typescript
-// In store
-setWidth: (width) => {
-  set({ width })
-  document.documentElement.style.setProperty('--sidebar-width', `${width}px`)
-}
-
-// In component
-<aside style={{ width: 'var(--sidebar-width)' }} />
-```

.claude/rules/sim-testing.md

@@ -1,263 +0,0 @@
----
-paths:
-  - "apps/sim/**/*.test.ts"
-  - "apps/sim/**/*.test.tsx"
----
-
-# Testing Patterns
-
-Use Vitest. Test files: `feature.ts` → `feature.test.ts`
-
-## Global Mocks (vitest.setup.ts)
-
-These modules are mocked globally — do NOT re-mock them in test files unless you need to override behavior:
-
-- `@sim/db` → `databaseMock`
-- `@sim/db/schema` → `schemaMock`
-- `drizzle-orm` → `drizzleOrmMock`
-- `@sim/logger` → `loggerMock`
-- `@/lib/auth` → `authMock`
-- `@/lib/auth/hybrid` → `hybridAuthMock` (with default session-delegating behavior)
-- `@/lib/core/utils/request` → `requestUtilsMock`
-- `@/stores/console/store`, `@/stores/terminal`, `@/stores/execution/store`
-- `@/blocks/registry`
-- `@trigger.dev/sdk`
-
-## Structure
-
-```typescript
-/**
- * @vitest-environment node
- */
-import { createMockRequest } from '@sim/testing'
-import { beforeEach, describe, expect, it, vi } from 'vitest'
-
-const { mockGetSession } = vi.hoisted(() => ({
-  mockGetSession: vi.fn(),
-}))
-
-vi.mock('@/lib/auth', () => ({
-  auth: { api: { getSession: vi.fn() } },
-  getSession: mockGetSession,
-}))
-
-import { GET, POST } from '@/app/api/my-route/route'
-
-describe('my route', () => {
-  beforeEach(() => {
-    vi.clearAllMocks()
-    mockGetSession.mockResolvedValue({ user: { id: 'user-1' } })
-  })
-
-  it('returns data', async () => {
-    const req = createMockRequest('GET')
-    const res = await GET(req)
-    expect(res.status).toBe(200)
-  })
-})
-```
-
-## Performance Rules (Critical)
-
-### NEVER use `vi.resetModules()` + `vi.doMock()` + `await import()`
-
-This is the #1 cause of slow tests. It forces complete module re-evaluation per test.
-
-```typescript
-// BAD — forces module re-evaluation every test (~50-100ms each)
-beforeEach(() => {
-  vi.resetModules()
-  vi.doMock('@/lib/auth', () => ({ getSession: vi.fn() }))
-})
-it('test', async () => {
-  const { GET } = await import('./route')  // slow dynamic import
-})
-
-// GOOD — module loaded once, mocks reconfigured per test (~1ms each)
-const { mockGetSession } = vi.hoisted(() => ({
-  mockGetSession: vi.fn(),
-}))
-vi.mock('@/lib/auth', () => ({ getSession: mockGetSession }))
-import { GET } from '@/app/api/my-route/route'
-
-beforeEach(() => { vi.clearAllMocks() })
-it('test', () => {
-  mockGetSession.mockResolvedValue({ user: { id: '1' } })
-})
-```
-
-**Only exception:** Singleton modules that cache state at module scope (e.g., Redis clients, connection pools). These genuinely need `vi.resetModules()` + dynamic import to get a fresh instance per test.
-
-### NEVER use `vi.importActual()`
-
-This defeats the purpose of mocking by loading the real module and all its dependencies.
-
-```typescript
-// BAD — loads real module + all transitive deps
-vi.mock('@/lib/workspaces/utils', async () => {
-  const actual = await vi.importActual('@/lib/workspaces/utils')
-  return { ...actual, myFn: vi.fn() }
-})
-
-// GOOD — mock everything, only implement what tests need
-vi.mock('@/lib/workspaces/utils', () => ({
-  myFn: vi.fn(),
-  otherFn: vi.fn(),
-}))
-```
-
-### Mock heavy transitive dependencies
-
-If a module under test imports `@/blocks` (200+ files), `@/tools/registry`, or other heavy modules, mock them:
-
-```typescript
-vi.mock('@/blocks', () => ({
-  getBlock: () => null,
-  getAllBlocks: () => ({}),
-  getAllBlockTypes: () => [],
-  registry: {},
-}))
-```
-
-### Use `@vitest-environment node` unless DOM is needed
-
-Only use `@vitest-environment jsdom` if the test uses `window`, `document`, `FormData`, or other browser APIs. Node environment is significantly faster.
-
-### Avoid real timers in tests
-
-```typescript
-// BAD
-await new Promise(r => setTimeout(r, 500))
-
-// GOOD — use minimal delays or fake timers
-await new Promise(r => setTimeout(r, 1))
-// or
-vi.useFakeTimers()
-```
-
-## Centralized Mocks (prefer over local declarations)
-
-`@sim/testing` exports ready-to-use mock modules for common dependencies. Import and pass directly to `vi.mock()` — no `vi.hoisted()` boilerplate needed. Each paired `*MockFns` object exposes the underlying `vi.fn()`s for per-test overrides.
-
-| Module mocked | Import | Factory form |
-|---|---|---|
-| `@/app/api/auth/oauth/utils` | `authOAuthUtilsMock`, `authOAuthUtilsMockFns` | `vi.mock('@/app/api/auth/oauth/utils', () => authOAuthUtilsMock)` |
-| `@/app/api/knowledge/utils` | `knowledgeApiUtilsMock`, `knowledgeApiUtilsMockFns` | `vi.mock('@/app/api/knowledge/utils', () => knowledgeApiUtilsMock)` |
-| `@/app/api/workflows/utils` | `workflowsApiUtilsMock`, `workflowsApiUtilsMockFns` | `vi.mock('@/app/api/workflows/utils', () => workflowsApiUtilsMock)` |
-| `@/lib/audit/log` | `auditMock`, `auditMockFns` | `vi.mock('@/lib/audit/log', () => auditMock)` |
-| `@/lib/auth` | `authMock`, `authMockFns` | `vi.mock('@/lib/auth', () => authMock)` |
-| `@/lib/auth/hybrid` | `hybridAuthMock`, `hybridAuthMockFns` | `vi.mock('@/lib/auth/hybrid', () => hybridAuthMock)` |
-| `@/lib/copilot/request/http` | `copilotHttpMock`, `copilotHttpMockFns` | `vi.mock('@/lib/copilot/request/http', () => copilotHttpMock)` |
-| `@/lib/core/config/env` | `envMock`, `createEnvMock(overrides)` | `vi.mock('@/lib/core/config/env', () => envMock)` |
-| `@/lib/core/config/feature-flags` | `featureFlagsMock` | `vi.mock('@/lib/core/config/feature-flags', () => featureFlagsMock)` |
-| `@/lib/core/config/redis` | `redisConfigMock`, `redisConfigMockFns` | `vi.mock('@/lib/core/config/redis', () => redisConfigMock)` |
-| `@/lib/core/security/encryption` | `encryptionMock`, `encryptionMockFns` | `vi.mock('@/lib/core/security/encryption', () => encryptionMock)` |
-| `@/lib/core/security/input-validation.server` | `inputValidationMock`, `inputValidationMockFns` | `vi.mock('@/lib/core/security/input-validation.server', () => inputValidationMock)` |
-| `@/lib/core/utils/request` | `requestUtilsMock`, `requestUtilsMockFns` | `vi.mock('@/lib/core/utils/request', () => requestUtilsMock)` |
-| `@/lib/core/utils/urls` | `urlsMock`, `urlsMockFns` | `vi.mock('@/lib/core/utils/urls', () => urlsMock)` |
-| `@/lib/execution/preprocessing` | `executionPreprocessingMock`, `executionPreprocessingMockFns` | `vi.mock('@/lib/execution/preprocessing', () => executionPreprocessingMock)` |
-| `@/lib/logs/execution/logging-session` | `loggingSessionMock`, `loggingSessionMockFns`, `LoggingSessionMock` | `vi.mock('@/lib/logs/execution/logging-session', () => loggingSessionMock)` |
-| `@/lib/workflows/orchestration` | `workflowsOrchestrationMock`, `workflowsOrchestrationMockFns` | `vi.mock('@/lib/workflows/orchestration', () => workflowsOrchestrationMock)` |
-| `@/lib/workflows/persistence/utils` | `workflowsPersistenceUtilsMock`, `workflowsPersistenceUtilsMockFns` | `vi.mock('@/lib/workflows/persistence/utils', () => workflowsPersistenceUtilsMock)` |
-| `@/lib/workflows/utils` | `workflowsUtilsMock`, `workflowsUtilsMockFns` | `vi.mock('@/lib/workflows/utils', () => workflowsUtilsMock)` |
-| `@/lib/workspaces/permissions/utils` | `permissionsMock`, `permissionsMockFns` | `vi.mock('@/lib/workspaces/permissions/utils', () => permissionsMock)` |
-| `@sim/db/schema` | `schemaMock` | `vi.mock('@sim/db/schema', () => schemaMock)` |
-
-### Auth mocking (API routes)
-
-```typescript
-import { authMock, authMockFns } from '@sim/testing'
-import { beforeEach, describe, expect, it, vi } from 'vitest'
-
-vi.mock('@/lib/auth', () => authMock)
-
-import { GET } from '@/app/api/my-route/route'
-
-beforeEach(() => {
-  vi.clearAllMocks()
-  authMockFns.mockGetSession.mockResolvedValue({ user: { id: 'user-1' } })
-})
-```
-
-Only define a local `vi.mock('@/lib/auth', ...)` if the module under test consumes exports outside the centralized shape (e.g., `auth.api.verifyOneTimeToken`, `auth.api.resetPassword`).
-
-### Hybrid auth mocking
-
-```typescript
-import { hybridAuthMock, hybridAuthMockFns } from '@sim/testing'
-
-vi.mock('@/lib/auth/hybrid', () => hybridAuthMock)
-
-// In tests:
-hybridAuthMockFns.mockCheckSessionOrInternalAuth.mockResolvedValue({
-  success: true, userId: 'user-1', authType: 'session',
-})
-```
-
-### Database chain mocking
-
-Use the centralized `dbChainMock` + `dbChainMockFns` helpers — no `vi.hoisted()` or chain-wiring boilerplate needed.
-
-```typescript
-import { dbChainMock, dbChainMockFns, resetDbChainMock } from '@sim/testing'
-
-vi.mock('@sim/db', () => dbChainMock)
-// Spread for custom exports: vi.mock('@sim/db', () => ({ ...dbChainMock, myTable: {...} }))
-
-beforeEach(() => {
-  vi.clearAllMocks()
-  resetDbChainMock() // only needed if tests use permanent (non-`Once`) overrides
-})
-
-it('reads a row', async () => {
-  dbChainMockFns.limit.mockResolvedValueOnce([{ id: '1', name: 'test' }])
-  // exercise code that hits db.select().from().where().limit()
-  expect(dbChainMockFns.where).toHaveBeenCalled()
-})
-```
-
-**Default chains supported:**
-- `select()/selectDistinct()/selectDistinctOn() → from() → where()/innerJoin()/leftJoin() → where() → limit()/orderBy()/returning()/groupBy()/for()`
-- `insert() → values() → returning()/onConflictDoUpdate()/onConflictDoNothing()`
-- `update() → set() → where() → limit()/orderBy()/returning()/for()`
-- `delete() → where() → limit()/orderBy()/returning()/for()`
-- `db.execute()` resolves `[]`
-- `db.transaction(cb)` calls cb with `dbChainMock.db`
-
-`.for('update')` (Postgres row-level locking) is supported on `where`
-builders. It returns a thenable with `.limit` / `.orderBy` / `.returning` /
-`.groupBy` attached, so both `await .where().for('update')` (terminal) and
-`await .where().for('update').limit(1)` (chained) work. Override the terminal
-result with `dbChainMockFns.for.mockResolvedValueOnce([...])`; for the chained
-form, mock the downstream terminal (e.g. `dbChainMockFns.limit.mockResolvedValueOnce([...])`).
-
-All terminals default to `Promise.resolve([])`. Override per-test with `dbChainMockFns.<terminal>.mockResolvedValueOnce(...)`.
-
-Use `resetDbChainMock()` in `beforeEach` only when tests replace wiring with `.mockReturnValue` / `.mockResolvedValue` (permanent). Tests using only `...Once` variants don't need it.
-
-## @sim/testing Package
-
-Always prefer over local test data.
-
-| Category | Utilities |
-|----------|-----------|
-| **Module mocks** | See "Centralized Mocks" table above |
-| **Logger helpers** | `loggerMock`, `createMockLogger()`, `getLoggerCalls()`, `clearLoggerMocks()` |
-| **Database helpers** | `databaseMock`, `drizzleOrmMock`, `createMockDb()`, `createMockSql()`, `createMockSqlOperators()` |
-| **Fetch helpers** | `setupGlobalFetchMock()`, `createMockFetch()`, `createMockResponse()`, `mockFetchError()` |
-| **Factories** | `createSession()`, `createWorkflowRecord()`, `createBlock()`, `createExecutionContext()` |
-| **Builders** | `WorkflowBuilder`, `ExecutionContextBuilder` |
-| **Assertions** | `expectWorkflowAccessGranted()`, `expectBlockExecuted()` |
-| **Requests** | `createMockRequest()`, `createMockFormDataRequest()` |
-
-## Rules Summary
-
-1. `@vitest-environment node` unless DOM is required
-2. Prefer centralized mocks from `@sim/testing` (see table above) over local `vi.hoisted()` + `vi.mock()` boilerplate
-3. `vi.hoisted()` + `vi.mock()` + static imports — never `vi.resetModules()` + `vi.doMock()` + dynamic imports
-4. `vi.mock()` calls before importing mocked modules
-5. `beforeEach(() => vi.clearAllMocks())` to reset state — no redundant `afterEach`
-6. No `vi.importActual()` — mock everything explicitly
-7. Mock heavy deps (`@/blocks`, `@/tools/registry`, `@/triggers`) in tests that don't need them
-8. Use absolute imports in test files
-9. Avoid real timers — use 1ms delays or `vi.useFakeTimers()`

.claude/rules/sim-typescript.md

@@ -1,21 +0,0 @@
----
-paths:
-  - "apps/sim/**/*.ts"
-  - "apps/sim/**/*.tsx"
----
-
-# TypeScript Rules
-
-1. **No `any`** - Use proper types or `unknown` with type guards
-2. **Props interface** - Always define for components
-3. **Const assertions** - `as const` for constant objects/arrays
-4. **Ref types** - Explicit: `useRef<HTMLDivElement>(null)`
-5. **Type imports** - `import type { X }` for type-only imports
-
-```typescript
-// ✗ Bad
-const handleClick = (e: any) => {}
-
-// ✓ Good
-const handleClick = (e: React.MouseEvent<HTMLButtonElement>) => {}
-```

.cursor/commands/add-block.md

@@ -1,826 +0,0 @@
-# Add Block Skill
-
-You are an expert at creating block configurations for Sim. You understand the serializer, subBlock types, conditions, dependsOn, modes, and all UI patterns.
-
-## Your Task
-
-When the user asks you to create a block:
-1. Create the block file in `apps/sim/blocks/blocks/{service}.ts`
-2. Configure all subBlocks with proper types, conditions, and dependencies
-3. Wire up tools correctly
-
-## Block Configuration Structure
-
-```typescript
-import { {ServiceName}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {ServiceName}Block: BlockConfig = {
-  type: '{service}',                    // snake_case identifier
-  name: '{Service Name}',               // Human readable
-  description: 'Brief description',     // One sentence
-  longDescription: 'Detailed description for docs',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',                    // 'tools' | 'blocks' | 'triggers'
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
-  bgColor: '#HEXCOLOR',                 // Brand color
-  icon: {ServiceName}Icon,
-
-  // Auth mode
-  authMode: AuthMode.OAuth,             // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Define all UI fields here
-  ],
-
-  tools: {
-    access: ['tool_id_1', 'tool_id_2'], // Array of tool IDs this block can use
-    config: {
-      tool: (params) => `{service}_${params.operation}`,  // Tool selector function
-      params: (params) => ({
-        // Transform subBlock values to tool params
-      }),
-    },
-  },
-
-  inputs: {
-    // Optional: define expected inputs from other blocks
-  },
-
-  outputs: {
-    // Define outputs available to downstream blocks
-  },
-}
-```
-
-## SubBlock Types Reference
-
-**Critical:** Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions.
-
-### Text Inputs
-```typescript
-// Single-line input
-{ id: 'field', title: 'Label', type: 'short-input', placeholder: '...' }
-
-// Multi-line input
-{ id: 'field', title: 'Label', type: 'long-input', placeholder: '...', rows: 6 }
-
-// Password input
-{ id: 'apiKey', title: 'API Key', type: 'short-input', password: true }
-```
-
-### Selection Inputs
-```typescript
-// Dropdown (static options)
-{
-  id: 'operation',
-  title: 'Operation',
-  type: 'dropdown',
-  options: [
-    { label: 'Create', id: 'create' },
-    { label: 'Update', id: 'update' },
-  ],
-  value: () => 'create',  // Default value function
-}
-
-// Combobox (searchable dropdown)
-{
-  id: 'field',
-  title: 'Label',
-  type: 'combobox',
-  options: [...],
-  searchable: true,
-}
-```
-
-### Code/JSON Inputs
-```typescript
-{
-  id: 'code',
-  title: 'Code',
-  type: 'code',
-  language: 'javascript',  // 'javascript' | 'json' | 'python'
-  placeholder: '// Enter code...',
-}
-```
-
-### OAuth/Credentials
-```typescript
-{
-  id: 'credential',
-  title: 'Account',
-  type: 'oauth-input',
-  serviceId: '{service}',  // Must match OAuth provider service key
-  requiredScopes: getScopesForService('{service}'),  // Import from @/lib/oauth/utils
-  placeholder: 'Select account',
-  required: true,
-}
-```
-
-**Scopes:** Always use `getScopesForService(serviceId)` from `@/lib/oauth/utils` for `requiredScopes`. Never hardcode scope arrays — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-**Scope descriptions:** When adding a new OAuth provider, also add human-readable descriptions for all scopes in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`.
-
-### Selectors (with dynamic options)
-```typescript
-// Channel selector (Slack, Discord, etc.)
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  serviceId: '{service}',
-  placeholder: 'Select channel',
-  dependsOn: ['credential'],
-}
-
-// Project selector (Jira, etc.)
-{
-  id: 'project',
-  title: 'Project',
-  type: 'project-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-
-// File selector (Google Drive, etc.)
-{
-  id: 'file',
-  title: 'File',
-  type: 'file-selector',
-  serviceId: '{service}',
-  mimeType: 'application/pdf',
-  dependsOn: ['credential'],
-}
-
-// User selector
-{
-  id: 'user',
-  title: 'User',
-  type: 'user-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-```
-
-### Other Types
-```typescript
-// Switch/toggle
-{ id: 'enabled', type: 'switch' }
-
-// Slider
-{ id: 'temperature', title: 'Temperature', type: 'slider', min: 0, max: 2, step: 0.1 }
-
-// Table (key-value pairs)
-{ id: 'headers', title: 'Headers', type: 'table', columns: ['Key', 'Value'] }
-
-// File upload
-{
-  id: 'files',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,
-  acceptedTypes: 'image/*,application/pdf',
-}
-```
-
-## File Input Handling
-
-When your block accepts file uploads, use the basic/advanced mode pattern with `normalizeFileInput`.
-
-### Basic/Advanced File Pattern
-
-```typescript
-// Basic mode: Visual file upload
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from other blocks
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any subblock's `id` in the same block
-- Values are stored under subblock `id`, not `canonicalParamId`
-
-### Normalizing File Input in tools.config
-
-Use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  access: ['service_upload'],
-  config: {
-    tool: (params) => {
-      // Check all field IDs: uploadFile (basic), fileRef (advanced), fileContent (legacy)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `service_${params.operation}`
-    },
-  },
-}
-```
-
-**Why this pattern?**
-- Values come through as `params.uploadFile` or `params.fileRef` (the subblock IDs)
-- `canonicalParamId` only controls UI/schema mapping, not runtime values
-- `normalizeFileInput` handles JSON strings from advanced mode template resolution
-
-### File Input Types in `inputs`
-
-Use `type: 'json'` for file inputs:
-
-```typescript
-inputs: {
-  uploadFile: { type: 'json', description: 'Uploaded file (UserFile)' },
-  fileRef: { type: 'json', description: 'File reference from previous block' },
-  // Legacy field for backwards compatibility
-  fileContent: { type: 'string', description: 'Legacy: base64 encoded content' },
-}
-```
-
-### Multiple Files
-
-For multiple file uploads:
-
-```typescript
-{
-  id: 'attachments',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,  // Allow multiple files
-  maxSize: 25,     // Max size in MB per file
-  acceptedTypes: 'image/*,application/pdf,.doc,.docx',
-}
-
-// In tools.config:
-const normalizedFiles = normalizeFileInput(
-  params.attachments || params.attachmentRefs,
-  // No { single: true } - returns array
-)
-if (normalizedFiles) {
-  params.files = normalizedFiles
-}
-```
-
-## Condition Syntax
-
-Controls when a field is shown based on other field values.
-
-### Simple Condition
-```typescript
-condition: { field: 'operation', value: 'create' }
-// Shows when operation === 'create'
-```
-
-### Multiple Values (OR)
-```typescript
-condition: { field: 'operation', value: ['create', 'update'] }
-// Shows when operation is 'create' OR 'update'
-```
-
-### Negation
-```typescript
-condition: { field: 'operation', value: 'delete', not: true }
-// Shows when operation !== 'delete'
-```
-
-### Compound (AND)
-```typescript
-condition: {
-  field: 'operation',
-  value: 'send',
-  and: {
-    field: 'type',
-    value: 'dm',
-    not: true,
-  }
-}
-// Shows when operation === 'send' AND type !== 'dm'
-```
-
-### Complex Example
-```typescript
-condition: {
-  field: 'operation',
-  value: ['list', 'search'],
-  not: true,
-  and: {
-    field: 'authMethod',
-    value: 'oauth',
-  }
-}
-// Shows when operation NOT in ['list', 'search'] AND authMethod === 'oauth'
-```
-
-## DependsOn Pattern
-
-Controls when a field is enabled and when its options are refetched.
-
-### Simple Array (all must be set)
-```typescript
-dependsOn: ['credential']
-// Enabled only when credential has a value
-// Options refetch when credential changes
-
-dependsOn: ['credential', 'projectId']
-// Enabled only when BOTH have values
-```
-
-### Complex (all + any)
-```typescript
-dependsOn: {
-  all: ['authMethod'],           // All must be set
-  any: ['credential', 'apiKey']  // At least one must be set
-}
-// Enabled when authMethod is set AND (credential OR apiKey is set)
-```
-
-## Required Pattern
-
-Can be boolean or condition-based.
-
-### Simple Boolean
-```typescript
-required: true
-required: false
-```
-
-### Conditional Required
-```typescript
-required: { field: 'operation', value: 'create' }
-// Required only when operation === 'create'
-
-required: { field: 'operation', value: ['create', 'update'] }
-// Required when operation is 'create' OR 'update'
-```
-
-## Mode Pattern (Basic vs Advanced)
-
-Controls which UI view shows the field.
-
-### Mode Options
-- `'basic'` - Only in basic view (default UI)
-- `'advanced'` - Only in advanced view
-- `'both'` - Both views (default if not specified)
-- `'trigger'` - Only in trigger configuration
-
-### canonicalParamId Pattern
-
-Maps multiple UI fields to a single serialized parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  dependsOn: ['credential'],
-}
-
-// Advanced mode: Manual input
-{
-  id: 'channelId',
-  title: 'Channel ID',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  placeholder: 'Enter channel ID manually',
-}
-```
-
-**How it works:**
-- In basic mode: `channel` selector value → `params.channel`
-- In advanced mode: `channelId` input value → `params.channel`
-- The serializer consolidates based on current mode
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any other subblock's `id` in the same block (causes conflicts)
-- `canonicalParamId` must be unique per block (only one basic/advanced pair per canonicalParamId)
-- ONLY use `canonicalParamId` to link basic/advanced mode alternatives for the same logical parameter
-- Do NOT use it for any other purpose
-
-## WandConfig Pattern
-
-Enables AI-assisted field generation.
-
-```typescript
-{
-  id: 'query',
-  title: 'Query',
-  type: 'code',
-  language: 'json',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a query based on the user request. Return ONLY the JSON.',
-    placeholder: 'Describe what you want to query...',
-    generationType: 'json-object',  // Optional: affects AI behavior
-    maintainHistory: true,          // Optional: keeps conversation context
-  },
-}
-```
-
-### Generation Types
-- `'javascript-function-body'` - JS code generation
-- `'json-object'` - Raw JSON (adds "no markdown" instruction)
-- `'json-schema'` - JSON Schema definitions
-- `'sql-query'` - SQL statements
-- `'timestamp'` - Adds current date/time context
-
-## Tools Configuration
-
-**Important:** `tools.config.tool` runs during serialization before variable resolution. Put `Number()` and other type coercions in `tools.config.params` instead, which runs at execution time after variables are resolved.
-
-**Preferred:** Use tool names directly as dropdown option IDs to avoid switch cases:
-```typescript
-// Dropdown options use tool IDs directly
-options: [
-  { label: 'Create', id: 'service_create' },
-  { label: 'Read', id: 'service_read' },
-]
-
-// Tool selector just returns the operation value
-tool: (params) => params.operation,
-```
-
-### With Parameter Transformation
-```typescript
-tools: {
-  access: ['service_action'],
-  config: {
-    tool: (params) => 'service_action',
-    params: (params) => ({
-      id: params.resourceId,
-      data: typeof params.data === 'string' ? JSON.parse(params.data) : params.data,
-    }),
-  },
-}
-```
-
-### V2 Versioned Tool Selector
-```typescript
-import { createVersionedToolSelector } from '@/blocks/utils'
-
-tools: {
-  access: [
-    'service_create_v2',
-    'service_read_v2',
-    'service_update_v2',
-  ],
-  config: {
-    tool: createVersionedToolSelector({
-      baseToolSelector: (params) => `service_${params.operation}`,
-      suffix: '_v2',
-      fallbackToolId: 'service_create_v2',
-    }),
-  },
-}
-```
-
-## Outputs Definition
-
-**IMPORTANT:** Block outputs have a simpler schema than tool outputs. Block outputs do NOT support:
-- `optional: true` - This is only for tool outputs
-- `items` property - This is only for tool outputs with array types
-
-Block outputs only support:
-- `type` - The data type ('string', 'number', 'boolean', 'json', 'array')
-- `description` - Human readable description
-- Nested object structure (for complex types)
-
-```typescript
-outputs: {
-  // Simple outputs
-  id: { type: 'string', description: 'Resource ID' },
-  success: { type: 'boolean', description: 'Whether operation succeeded' },
-
-  // Use type: 'json' for complex objects or arrays (NOT type: 'array' with items)
-  items: { type: 'json', description: 'List of items' },
-  metadata: { type: 'json', description: 'Response metadata' },
-
-  // Nested outputs (for structured data)
-  user: {
-    id: { type: 'string', description: 'User ID' },
-    name: { type: 'string', description: 'User name' },
-    email: { type: 'string', description: 'User email' },
-  },
-}
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **describe the inner fields in the description** so downstream blocks know what properties are available. For well-known, stable objects, use nested output definitions instead:
-
-```typescript
-outputs: {
-  // BAD: Opaque json with no info about what's inside
-  plan: { type: 'json', description: 'Zone plan information' },
-
-  // GOOD: Describe the known fields in the description
-  plan: {
-    type: 'json',
-    description: 'Zone plan information (id, name, price, currency, frequency, is_subscribed)',
-  },
-
-  // BEST: Use nested output definition when the shape is stable and well-known
-  plan: {
-    id: { type: 'string', description: 'Plan identifier' },
-    name: { type: 'string', description: 'Plan name' },
-    price: { type: 'number', description: 'Plan price' },
-    currency: { type: 'string', description: 'Price currency' },
-  },
-}
-```
-
-Use the nested pattern when:
-- The object has a small, stable set of fields (< 10)
-- Downstream blocks will commonly access specific properties
-- The API response shape is well-documented and unlikely to change
-
-Use `type: 'json'` with a descriptive string when:
-- The object has many fields or a dynamic shape
-- It represents a list/array of items
-- The shape varies by operation
-
-## V2 Block Pattern
-
-When creating V2 blocks (alongside legacy V1):
-
-```typescript
-// V1 Block - mark as legacy
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service (Legacy)',
-  hideFromToolbar: true,  // Hide from toolbar
-  // ... rest of config
-}
-
-// V2 Block - visible, uses V2 tools
-export const ServiceV2Block: BlockConfig = {
-  type: 'service_v2',
-  name: 'Service',              // Clean name
-  hideFromToolbar: false,       // Visible
-  subBlocks: ServiceBlock.subBlocks,  // Reuse UI
-  tools: {
-    access: ServiceBlock.tools?.access?.map(id => `${id}_v2`) || [],
-    config: {
-      tool: createVersionedToolSelector({
-        baseToolSelector: (params) => (ServiceBlock.tools?.config as any)?.tool(params),
-        suffix: '_v2',
-        fallbackToolId: 'service_default_v2',
-      }),
-      params: ServiceBlock.tools?.config?.params,
-    },
-  },
-  outputs: {
-    // Flat, API-aligned outputs (not wrapped in content/metadata)
-  },
-}
-```
-
-## Registering Blocks
-
-After creating the block, remind the user to:
-1. Import in `apps/sim/blocks/registry.ts`
-2. Add to the `registry` object (alphabetically):
-
-```typescript
-import { ServiceBlock } from '@/blocks/blocks/service'
-
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  service: ServiceBlock,
-}
-```
-
-## Complete Example
-
-```typescript
-import { ServiceIcon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service',
-  description: 'Integrate with Service API',
-  longDescription: 'Full description for documentation...',
-  docsLink: 'https://docs.sim.ai/tools/service',
-  category: 'tools',
-  integrationType: IntegrationType.DeveloperTools,
-  tags: ['oauth', 'api'],
-  bgColor: '#FF6B6B',
-  icon: ServiceIcon,
-  authMode: AuthMode.OAuth,
-
-  subBlocks: [
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Create', id: 'create' },
-        { label: 'Read', id: 'read' },
-        { label: 'Update', id: 'update' },
-        { label: 'Delete', id: 'delete' },
-      ],
-      value: () => 'create',
-    },
-    {
-      id: 'credential',
-      title: 'Service Account',
-      type: 'oauth-input',
-      serviceId: 'service',
-      requiredScopes: getScopesForService('service'),
-      placeholder: 'Select account',
-      required: true,
-    },
-    {
-      id: 'resourceId',
-      title: 'Resource ID',
-      type: 'short-input',
-      placeholder: 'Enter resource ID',
-      condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-      required: { field: 'operation', value: ['read', 'update', 'delete'] },
-    },
-    {
-      id: 'name',
-      title: 'Name',
-      type: 'short-input',
-      placeholder: 'Resource name',
-      condition: { field: 'operation', value: ['create', 'update'] },
-      required: { field: 'operation', value: 'create' },
-    },
-  ],
-
-  tools: {
-    access: ['service_create', 'service_read', 'service_update', 'service_delete'],
-    config: {
-      tool: (params) => `service_${params.operation}`,
-    },
-  },
-
-  outputs: {
-    id: { type: 'string', description: 'Resource ID' },
-    name: { type: 'string', description: 'Resource name' },
-    createdAt: { type: 'string', description: 'Creation timestamp' },
-  },
-}
-```
-
-## Connecting Blocks with Triggers
-
-If the service supports webhooks, connect the block to its triggers.
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const ServiceBlock: BlockConfig = {
-  // ... basic config ...
-
-  triggers: {
-    enabled: true,
-    available: ['service_event_a', 'service_event_b', 'service_webhook'],
-  },
-
-  subBlocks: [
-    // Tool subBlocks first...
-    { id: 'operation', /* ... */ },
-
-    // Then spread trigger subBlocks
-    ...getTrigger('service_event_a').subBlocks,
-    ...getTrigger('service_event_b').subBlocks,
-    ...getTrigger('service_webhook').subBlocks,
-  ],
-}
-```
-
-See the `/add-trigger` skill for creating triggers.
-
-## Icon Requirement
-
-If the icon doesn't already exist in `@/components/icons.tsx`, **do NOT search for it yourself**. After completing the block, ask the user to provide the SVG:
-
-```
-The block is complete, but I need an icon for {Service}.
-Please provide the SVG and I'll convert it to a React component.
-
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-```
-
-## Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. This includes:
-- Pagination tokens
-- Time range filters (start/end time)
-- Sort order options
-- Reply settings
-- Rarely used IDs (e.g., reply-to tweet ID, quote tweet ID)
-- Max results / limits
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  placeholder: 'ISO 8601 timestamp',
-  condition: { field: 'operation', value: ['search', 'list'] },
-  mode: 'advanced',  // Rarely used, hide from basic view
-}
-```
-
-## WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually, such as timestamps, comma-separated lists, and complex query strings. This gives users an AI-assisted input experience.
-
-```typescript
-// Timestamps - use generationType: 'timestamp' to inject current date context
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp based on the user description. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-
-// Comma-separated lists - simple prompt without generationType
-{
-  id: 'mediaIds',
-  title: 'Media IDs',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a comma-separated list of media IDs. Return ONLY the comma-separated values.',
-  },
-}
-```
-
-## Naming Convention
-
-All tool IDs referenced in `tools.access` and returned by `tools.config.tool` MUST use `snake_case` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase.
-
-## Checklist Before Finishing
-
-- [ ] `integrationType` is set to the correct `IntegrationType` enum value
-- [ ] `tags` array includes all applicable `IntegrationTag` values
-- [ ] All subBlocks have `id`, `title` (except switch), and `type`
-- [ ] Conditions use correct syntax (field, value, not, and)
-- [ ] DependsOn set for fields that need other values
-- [ ] Required fields marked correctly (boolean or condition)
-- [ ] OAuth inputs have correct `serviceId` and `requiredScopes: getScopesForService(serviceId)`
-- [ ] Scope descriptions added to `SCOPE_DESCRIPTIONS` in `lib/oauth/utils.ts` for any new scopes
-- [ ] Tools.access lists all tool IDs (snake_case)
-- [ ] Tools.config.tool returns correct tool ID (snake_case)
-- [ ] Outputs match tool outputs
-- [ ] Block registered in registry.ts
-- [ ] If icon missing: asked user to provide SVG
-- [ ] If triggers exist: `triggers` config set, trigger subBlocks spread
-- [ ] Optional/rarely-used fields set to `mode: 'advanced'`
-- [ ] Timestamps and complex inputs have `wandConfig` enabled
-
-## Final Validation (Required)
-
-After creating the block, you MUST validate it against every tool it references:
-
-1. **Read every tool definition** that appears in `tools.access` — do not skip any
-2. **For each tool, verify the block has correct:**
-   - SubBlock inputs that cover all required tool params (with correct `condition` to show for that operation)
-   - SubBlock input types that match the tool param types (e.g., dropdown for enums, short-input for strings)
-   - `tools.config.params` correctly maps subBlock IDs to tool param names (if they differ)
-   - Type coercions in `tools.config.params` for any params that need conversion (Number(), Boolean(), JSON.parse())
-3. **Verify block outputs** cover the key fields returned by all tools
-4. **Verify conditions** — each subBlock should only show for the operations that actually use it

.cursor/commands/add-connector.md

@@ -1,523 +0,0 @@
-# Add Connector Skill
-
-You are an expert at adding knowledge base connectors to Sim. A connector syncs documents from an external source (Confluence, Google Drive, Notion, etc.) into a knowledge base.
-
-## Your Task
-
-When the user asks you to create a connector:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Determine the auth mode: **OAuth** (if Sim already has an OAuth provider for the service) or **API key** (if the service uses API key / Bearer token auth)
-3. Create the connector directory and config
-4. Register it in the connector registry
-
-## Directory Structure
-
-Create files in `apps/sim/connectors/{service}/`:
-```
-connectors/{service}/
-├── index.ts          # Barrel export
-└── {service}.ts      # ConnectorConfig definition
-```
-
-## Authentication
-
-Connectors use a discriminated union for auth config (`ConnectorAuthConfig` in `connectors/types.ts`):
-
-```typescript
-type ConnectorAuthConfig =
-  | { mode: 'oauth'; provider: OAuthService; requiredScopes?: string[] }
-  | { mode: 'apiKey'; label?: string; placeholder?: string }
-```
-
-### OAuth mode
-For services with existing OAuth providers in `apps/sim/lib/oauth/types.ts`. The `provider` must match an `OAuthService`. The modal shows a credential picker and handles token refresh automatically.
-
-### API key mode
-For services that use API key / Bearer token auth. The modal shows a password input with the configured `label` and `placeholder`. The API key is encrypted at rest using AES-256-GCM and stored in a dedicated `encryptedApiKey` column on the connector record. The sync engine decrypts it automatically — connectors receive the raw access token in `listDocuments`, `getDocument`, and `validateConfig`.
-
-## ConnectorConfig Structure
-
-### OAuth connector example
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { {Service}Icon } from '@/components/icons'
-import { fetchWithRetry } from '@/lib/knowledge/documents/utils'
-import type { ConnectorConfig, ExternalDocument, ExternalDocumentList } from '@/connectors/types'
-
-const logger = createLogger('{Service}Connector')
-
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'oauth',
-    provider: '{service}',          // Must match OAuthService in lib/oauth/types.ts
-    requiredScopes: ['read:...'],
-  },
-
-  configFields: [
-    // Rendered dynamically by the add-connector modal UI
-    // Supports 'short-input' and 'dropdown' types
-  ],
-
-  listDocuments: async (accessToken, sourceConfig, cursor) => {
-    // Return metadata stubs with contentDeferred: true (if per-doc content fetch needed)
-    // Or full documents with content (if list API returns content inline)
-    // Return { documents: ExternalDocument[], nextCursor?, hasMore }
-  },
-
-  getDocument: async (accessToken, sourceConfig, externalId) => {
-    // Fetch full content for a single document
-    // Return ExternalDocument with contentDeferred: false, or null
-  },
-
-  validateConfig: async (accessToken, sourceConfig) => {
-    // Return { valid: true } or { valid: false, error: 'message' }
-  },
-
-  // Optional: map source metadata to semantic tag keys (translated to slots by sync engine)
-  mapTags: (metadata) => {
-    // Return Record<string, unknown> with keys matching tagDefinitions[].id
-  },
-}
-```
-
-### API key connector example
-
-```typescript
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'apiKey',
-    label: 'API Key',                       // Shown above the input field
-    placeholder: 'Enter your {Service} API key',  // Input placeholder
-  },
-
-  configFields: [ /* ... */ ],
-  listDocuments: async (accessToken, sourceConfig, cursor) => { /* ... */ },
-  getDocument: async (accessToken, sourceConfig, externalId) => { /* ... */ },
-  validateConfig: async (accessToken, sourceConfig) => { /* ... */ },
-}
-```
-
-## ConfigField Types
-
-The add-connector modal renders these automatically — no custom UI needed.
-
-Three field types are supported: `short-input`, `dropdown`, and `selector`.
-
-```typescript
-// Text input
-{
-  id: 'domain',
-  title: 'Domain',
-  type: 'short-input',
-  placeholder: 'yoursite.example.com',
-  required: true,
-}
-
-// Dropdown (static options)
-{
-  id: 'contentType',
-  title: 'Content Type',
-  type: 'dropdown',
-  required: false,
-  options: [
-    { label: 'Pages only', id: 'page' },
-    { label: 'Blog posts only', id: 'blogpost' },
-    { label: 'All content', id: 'all' },
-  ],
-}
-```
-
-## Dynamic Selectors (Canonical Pairs)
-
-Use `type: 'selector'` to fetch options dynamically from the existing selector registry (`hooks/selectors/registry.ts`). Selectors are always paired with a manual fallback input using the **canonical pair** pattern — a `selector` field (basic mode) and a `short-input` field (advanced mode) linked by `canonicalParamId`.
-
-The user sees a toggle button (ArrowLeftRight) to switch between the selector dropdown and manual text input. On submit, the modal resolves each canonical pair to the active mode's value, keyed by `canonicalParamId`.
-
-### Rules
-
-1. **Every selector field MUST have a canonical pair** — a corresponding `short-input` (or `dropdown`) field with the same `canonicalParamId` and `mode: 'advanced'`.
-2. **`required` must be set identically on both fields** in a pair. If the selector is required, the manual input must also be required.
-3. **`canonicalParamId` must match the key the connector expects in `sourceConfig`** (e.g. `baseId`, `channel`, `teamId`). The advanced field's `id` should typically match `canonicalParamId`.
-4. **`dependsOn` references the selector field's `id`**, not the `canonicalParamId`. The modal propagates dependency clearing across canonical siblings automatically — changing either field in a parent pair clears dependent children.
-
-### Selector canonical pair example (Airtable base → table cascade)
-
-```typescript
-configFields: [
-  // Base: selector (basic) + manual (advanced)
-  {
-    id: 'baseSelector',
-    title: 'Base',
-    type: 'selector',
-    selectorKey: 'airtable.bases',     // Must exist in hooks/selectors/registry.ts
-    canonicalParamId: 'baseId',
-    mode: 'basic',
-    placeholder: 'Select a base',
-    required: true,
-  },
-  {
-    id: 'baseId',
-    title: 'Base ID',
-    type: 'short-input',
-    canonicalParamId: 'baseId',
-    mode: 'advanced',
-    placeholder: 'e.g. appXXXXXXXXXXXXXX',
-    required: true,
-  },
-  // Table: selector depends on base (basic) + manual (advanced)
-  {
-    id: 'tableSelector',
-    title: 'Table',
-    type: 'selector',
-    selectorKey: 'airtable.tables',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'basic',
-    dependsOn: ['baseSelector'],       // References the selector field ID
-    placeholder: 'Select a table',
-    required: true,
-  },
-  {
-    id: 'tableIdOrName',
-    title: 'Table Name or ID',
-    type: 'short-input',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'advanced',
-    placeholder: 'e.g. Tasks',
-    required: true,
-  },
-  // Non-selector fields stay as-is
-  { id: 'maxRecords', title: 'Max Records', type: 'short-input', ... },
-]
-```
-
-### Selector with domain dependency (Jira/Confluence pattern)
-
-When a selector depends on a plain `short-input` field (no canonical pair), `dependsOn` references that field's `id` directly. The `domain` field's value maps to `SelectorContext.domain` automatically via `SELECTOR_CONTEXT_FIELDS`.
-
-```typescript
-configFields: [
-  {
-    id: 'domain',
-    title: 'Jira Domain',
-    type: 'short-input',
-    placeholder: 'yoursite.atlassian.net',
-    required: true,
-  },
-  {
-    id: 'projectSelector',
-    title: 'Project',
-    type: 'selector',
-    selectorKey: 'jira.projects',
-    canonicalParamId: 'projectKey',
-    mode: 'basic',
-    dependsOn: ['domain'],
-    placeholder: 'Select a project',
-    required: true,
-  },
-  {
-    id: 'projectKey',
-    title: 'Project Key',
-    type: 'short-input',
-    canonicalParamId: 'projectKey',
-    mode: 'advanced',
-    placeholder: 'e.g. ENG, PROJ',
-    required: true,
-  },
-]
-```
-
-### How `dependsOn` maps to `SelectorContext`
-
-The connector selector field builds a `SelectorContext` from dependency values. For the mapping to work, each dependency's `canonicalParamId` (or field `id` for non-canonical fields) must exist in `SELECTOR_CONTEXT_FIELDS` (`lib/workflows/subblocks/context.ts`):
-
-```
-oauthCredential, domain, teamId, projectId, knowledgeBaseId, planId,
-siteId, collectionId, spreadsheetId, fileId, baseId, datasetId, serviceDeskId
-```
-
-### Available selector keys
-
-Check `hooks/selectors/types.ts` for the full `SelectorKey` union. Common ones for connectors:
-
-| SelectorKey | Context Deps | Returns |
-|-------------|-------------|---------|
-| `airtable.bases` | credential | Base ID + name |
-| `airtable.tables` | credential, `baseId` | Table ID + name |
-| `slack.channels` | credential | Channel ID + name |
-| `gmail.labels` | credential | Label ID + name |
-| `google.calendar` | credential | Calendar ID + name |
-| `linear.teams` | credential | Team ID + name |
-| `linear.projects` | credential, `teamId` | Project ID + name |
-| `jira.projects` | credential, `domain` | Project key + name |
-| `confluence.spaces` | credential, `domain` | Space key + name |
-| `notion.databases` | credential | Database ID + name |
-| `asana.workspaces` | credential | Workspace GID + name |
-| `microsoft.teams` | credential | Team ID + name |
-| `microsoft.channels` | credential, `teamId` | Channel ID + name |
-| `webflow.sites` | credential | Site ID + name |
-| `outlook.folders` | credential | Folder ID + name |
-
-## ExternalDocument Shape
-
-Every document returned from `listDocuments`/`getDocument` must include:
-
-```typescript
-{
-  externalId: string          // Source-specific unique ID
-  title: string               // Document title
-  content: string             // Extracted plain text (or '' if contentDeferred)
-  contentDeferred?: boolean   // true = content will be fetched via getDocument
-  mimeType: 'text/plain'     // Always text/plain (content is extracted)
-  contentHash: string         // Metadata-based hash for change detection
-  sourceUrl?: string          // Link back to original (stored on document record)
-  metadata?: Record<string, unknown>  // Source-specific data (fed to mapTags)
-}
-```
-
-## Content Deferral (Required for file/content-download connectors)
-
-**All connectors that require per-document API calls to fetch content MUST use `contentDeferred: true`.** This is the standard pattern — `listDocuments` returns lightweight metadata stubs, and content is fetched lazily by the sync engine via `getDocument` only for new/changed documents.
-
-This pattern is critical for reliability: the sync engine processes documents in batches and enqueues each batch for processing immediately. If a sync times out, all previously-batched documents are already queued. Without deferral, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-### When to use `contentDeferred: true`
-
-- The service's list API does NOT return document content (only metadata)
-- Content requires a separate download/export API call per document
-- Examples: Google Drive, OneDrive, SharePoint, Dropbox, Notion, Confluence, Gmail, Obsidian, Evernote, GitHub
-
-### When NOT to use `contentDeferred`
-
-- The list API already returns the full content inline (e.g., Slack messages, Reddit posts, HubSpot notes)
-- No per-document API call is needed to get content
-
-### Content Hash Strategy
-
-Use a **metadata-based** `contentHash` — never a content-based hash. The hash must be derivable from the list response metadata alone, so the sync engine can detect changes without downloading content.
-
-Good metadata hash sources:
-- `modifiedTime` / `lastModifiedDateTime` — changes when file is edited
-- Git blob SHA — unique per content version
-- API-provided content hash (e.g., Dropbox `content_hash`)
-- Version number (e.g., Confluence page version)
-
-Format: `{service}:{id}:{changeIndicator}`
-
-```typescript
-// Google Drive: modifiedTime changes on edit
-contentHash: `gdrive:${file.id}:${file.modifiedTime ?? ''}`
-
-// GitHub: blob SHA is a content-addressable hash
-contentHash: `gitsha:${item.sha}`
-
-// Dropbox: API provides content_hash
-contentHash: `dropbox:${entry.id}:${entry.content_hash ?? entry.server_modified}`
-
-// Confluence: version number increments on edit
-contentHash: `confluence:${page.id}:${page.version.number}`
-```
-
-**Critical invariant:** The `contentHash` MUST be identical whether produced by `listDocuments` (stub) or `getDocument` (full doc). Both should use the same stub function to guarantee this.
-
-### Implementation Pattern
-
-```typescript
-// 1. Create a stub function (sync, no API calls)
-function fileToStub(file: ServiceFile): ExternalDocument {
-  return {
-    externalId: file.id,
-    title: file.name || 'Untitled',
-    content: '',
-    contentDeferred: true,
-    mimeType: 'text/plain',
-    sourceUrl: `https://service.com/file/${file.id}`,
-    contentHash: `service:${file.id}:${file.modifiedTime ?? ''}`,
-    metadata: { /* fields needed by mapTags */ },
-  }
-}
-
-// 2. listDocuments returns stubs (fast, metadata only)
-listDocuments: async (accessToken, sourceConfig, cursor) => {
-  const response = await fetchWithRetry(listUrl, { ... })
-  const files = (await response.json()).files
-  const documents = files.map(fileToStub)
-  return { documents, nextCursor, hasMore }
-}
-
-// 3. getDocument fetches content and returns full doc with SAME contentHash
-getDocument: async (accessToken, sourceConfig, externalId) => {
-  const metadata = await fetchWithRetry(metadataUrl, { ... })
-  const file = await metadata.json()
-  if (file.trashed) return null
-
-  try {
-    const content = await fetchContent(accessToken, file)
-    if (!content.trim()) return null
-    const stub = fileToStub(file)
-    return { ...stub, content, contentDeferred: false }
-  } catch (error) {
-    logger.warn(`Failed to fetch content for: ${file.name}`, { error })
-    return null
-  }
-}
-```
-
-### Reference Implementations
-
-- **Google Drive**: `connectors/google-drive/google-drive.ts` — file download/export with `modifiedTime` hash
-- **GitHub**: `connectors/github/github.ts` — git blob SHA hash
-- **Notion**: `connectors/notion/notion.ts` — blocks API with `last_edited_time` hash
-- **Confluence**: `connectors/confluence/confluence.ts` — version number hash
-
-## tagDefinitions — Declared Tag Definitions
-
-Declare which tags the connector populates using semantic IDs. Shown in the add-connector modal as opt-out checkboxes.
-On connector creation, slots are **dynamically assigned** via `getNextAvailableSlot` — connectors never hardcode slot names.
-
-```typescript
-tagDefinitions: [
-  { id: 'labels', displayName: 'Labels', fieldType: 'text' },
-  { id: 'version', displayName: 'Version', fieldType: 'number' },
-  { id: 'lastModified', displayName: 'Last Modified', fieldType: 'date' },
-],
-```
-
-Each entry has:
-- `id`: Semantic key matching a key returned by `mapTags` (e.g. `'labels'`, `'version'`)
-- `displayName`: Human-readable name shown in the UI (e.g. "Labels", "Last Modified")
-- `fieldType`: `'text'` | `'number'` | `'date'` | `'boolean'` — determines which slot pool to draw from
-
-Users can opt out of specific tags in the modal. Disabled IDs are stored in `sourceConfig.disabledTagIds`.
-The assigned mapping (`semantic id → slot`) is stored in `sourceConfig.tagSlotMapping`.
-
-## mapTags — Metadata to Semantic Keys
-
-Maps source metadata to semantic tag keys. Required if `tagDefinitions` is set.
-The sync engine calls this automatically and translates semantic keys to actual DB slots
-using the `tagSlotMapping` stored on the connector.
-
-Return keys must match the `id` values declared in `tagDefinitions`.
-
-```typescript
-mapTags: (metadata: Record<string, unknown>): Record<string, unknown> => {
-  const result: Record<string, unknown> = {}
-
-  // Validate arrays before casting — metadata may be malformed
-  const labels = Array.isArray(metadata.labels) ? (metadata.labels as string[]) : []
-  if (labels.length > 0) result.labels = labels.join(', ')
-
-  // Validate numbers — guard against NaN
-  if (metadata.version != null) {
-    const num = Number(metadata.version)
-    if (!Number.isNaN(num)) result.version = num
-  }
-
-  // Validate dates — guard against Invalid Date
-  if (typeof metadata.lastModified === 'string') {
-    const date = new Date(metadata.lastModified)
-    if (!Number.isNaN(date.getTime())) result.lastModified = date
-  }
-
-  return result
-}
-```
-
-## External API Calls — Use `fetchWithRetry`
-
-All external API calls must use `fetchWithRetry` from `@/lib/knowledge/documents/utils` instead of raw `fetch()`. This provides exponential backoff with retries on 429/502/503/504 errors. It returns a standard `Response` — all `.ok`, `.json()`, `.text()` checks work unchanged.
-
-For `validateConfig` (user-facing, called on save), pass `VALIDATE_RETRY_OPTIONS` to cap wait time at ~7s. Background operations (`listDocuments`, `getDocument`) use the built-in defaults (5 retries, ~31s max).
-
-```typescript
-import { VALIDATE_RETRY_OPTIONS, fetchWithRetry } from '@/lib/knowledge/documents/utils'
-
-// Background sync — use defaults
-const response = await fetchWithRetry(url, {
-  method: 'GET',
-  headers: { Authorization: `Bearer ${accessToken}` },
-})
-
-// validateConfig — tighter retry budget
-const response = await fetchWithRetry(url, { ... }, VALIDATE_RETRY_OPTIONS)
-```
-
-## sourceUrl
-
-If `ExternalDocument.sourceUrl` is set, the sync engine stores it on the document record. Always construct the full URL (not a relative path).
-
-## Sync Engine Behavior (Do Not Modify)
-
-The sync engine (`lib/knowledge/connectors/sync-engine.ts`) is connector-agnostic. It:
-1. Calls `listDocuments` with pagination until `hasMore` is false
-2. Compares `contentHash` to detect new/changed/unchanged documents
-3. Stores `sourceUrl` and calls `mapTags` on insert/update automatically
-4. Handles soft-delete of removed documents
-5. Resolves access tokens automatically — OAuth tokens are refreshed, API keys are decrypted from the `encryptedApiKey` column
-
-You never need to modify the sync engine when adding a connector.
-
-## Icon
-
-The `icon` field on `ConnectorConfig` is used throughout the UI — in the connector list, the add-connector modal, and as the document icon in the knowledge base table (replacing the generic file type icon for connector-sourced documents). The icon is read from `CONNECTOR_REGISTRY[connectorType].icon` at runtime — no separate icon map to maintain.
-
-If the service already has an icon in `apps/sim/components/icons.tsx` (from a tool integration), reuse it. Otherwise, ask the user to provide the SVG.
-
-## Registering
-
-Add one line to `apps/sim/connectors/registry.ts`:
-
-```typescript
-import { {service}Connector } from '@/connectors/{service}'
-
-export const CONNECTOR_REGISTRY: ConnectorRegistry = {
-  // ... existing connectors ...
-  {service}: {service}Connector,
-}
-```
-
-## Reference Implementations
-
-- **OAuth + contentDeferred**: `apps/sim/connectors/google-drive/google-drive.ts` — file download with metadata-based hash, `orderBy` for deterministic pagination
-- **OAuth + contentDeferred (blocks API)**: `apps/sim/connectors/notion/notion.ts` — complex block content extraction deferred to `getDocument`
-- **OAuth + contentDeferred (git)**: `apps/sim/connectors/github/github.ts` — blob SHA hash, tree listing
-- **OAuth + inline content**: `apps/sim/connectors/confluence/confluence.ts` — multiple config field types, `mapTags`, label fetching
-- **API key**: `apps/sim/connectors/fireflies/fireflies.ts` — GraphQL API with Bearer token auth
-
-## Checklist
-
-- [ ] Created `connectors/{service}/{service}.ts` with full ConnectorConfig
-- [ ] Created `connectors/{service}/index.ts` barrel export
-- [ ] **Auth configured correctly:**
-  - OAuth: `auth.provider` matches an existing `OAuthService` in `lib/oauth/types.ts`
-  - API key: `auth.label` and `auth.placeholder` set appropriately
-- [ ] **Selector fields configured correctly (if applicable):**
-  - Every `type: 'selector'` field has a canonical pair (`short-input` or `dropdown` with same `canonicalParamId` and `mode: 'advanced'`)
-  - `required` is identical on both fields in each canonical pair
-  - `selectorKey` exists in `hooks/selectors/registry.ts`
-  - `dependsOn` references selector field IDs (not `canonicalParamId`)
-  - Dependency `canonicalParamId` values exist in `SELECTOR_CONTEXT_FIELDS`
-- [ ] `listDocuments` handles pagination with metadata-based content hashes
-- [ ] `contentDeferred: true` used if content requires per-doc API calls (file download, export, blocks fetch)
-- [ ] `contentHash` is metadata-based (not content-based) and identical between stub and `getDocument`
-- [ ] `sourceUrl` set on each ExternalDocument (full URL, not relative)
-- [ ] `metadata` includes source-specific data for tag mapping
-- [ ] `tagDefinitions` declared for each semantic key returned by `mapTags`
-- [ ] `mapTags` implemented if source has useful metadata (labels, dates, versions)
-- [ ] `validateConfig` verifies the source is accessible
-- [ ] All external API calls use `fetchWithRetry` (not raw `fetch`)
-- [ ] All optional config fields validated in `validateConfig`
-- [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
-- [ ] Registered in `connectors/registry.ts`

.cursor/commands/add-hosted-key.md

@@ -1,291 +0,0 @@
-# Adding Hosted Key Support to a Tool
-
-When a tool has hosted key support, Sim provides its own API key if the user hasn't configured one (via BYOK or env var). Usage is metered and billed to the workspace.
-
-## Overview
-
-| Step | What | Where |
-|------|------|-------|
-| 1 | Register BYOK provider ID | `tools/types.ts`, `app/api/workspaces/[id]/byok-keys/route.ts` |
-| 2 | Research the API's pricing and rate limits | API docs / pricing page (before writing any code) |
-| 3 | Add `hosting` config to the tool | `tools/{service}/{action}.ts` |
-| 4 | Hide API key field when hosted | `blocks/blocks/{service}.ts` |
-| 5 | Add to BYOK settings UI | BYOK settings component (`byok.tsx`) |
-| 6 | Summarize pricing and throttling comparison | Output to user (after all code changes) |
-
-## Step 1: Register the BYOK Provider ID
-
-Add the new provider to the `BYOKProviderId` union in `tools/types.ts`:
-
-```typescript
-export type BYOKProviderId =
-  | 'openai'
-  | 'anthropic'
-  // ...existing providers
-  | 'your_service'
-```
-
-Then add it to `VALID_PROVIDERS` in `app/api/workspaces/[id]/byok-keys/route.ts`:
-
-```typescript
-const VALID_PROVIDERS = ['openai', 'anthropic', 'google', 'mistral', 'your_service'] as const
-```
-
-## Step 2: Research the API's Pricing Model and Rate Limits
-
-**Before writing any `getCost` or `rateLimit` code**, look up the service's official documentation for both pricing and rate limits. You need to understand:
-
-### Pricing
-
-1. **How the API charges** — per request, per credit, per token, per step, per minute, etc.
-2. **Whether the API reports cost in its response** — look for fields like `creditsUsed`, `costDollars`, `tokensUsed`, or similar in the response body or headers
-3. **Whether cost varies by endpoint/options** — some APIs charge more for certain features (e.g., Firecrawl charges 1 credit/page base but +4 for JSON format, +4 for enhanced mode)
-4. **The dollar-per-unit rate** — what each credit/token/unit costs in dollars on our plan
-
-### Rate Limits
-
-1. **What rate limits the API enforces** — requests per minute/second, tokens per minute, concurrent requests, etc.
-2. **Whether limits vary by plan tier** — free vs paid vs enterprise often have different ceilings
-3. **Whether limits are per-key or per-account** — determines whether adding more hosted keys actually increases total throughput
-4. **What the API returns when rate limited** — HTTP 429, `Retry-After` header, error body format, etc.
-5. **Whether there are multiple dimensions** — some APIs limit both requests/min AND tokens/min independently
-
-Search the API's docs/pricing page (use WebSearch/WebFetch). Capture the pricing model as a comment in `getCost` so future maintainers know the source of truth.
-
-### Setting Our Rate Limits
-
-Our rate limiter (`lib/core/rate-limiter/hosted-key/`) uses a token-bucket algorithm applied **per billing actor** (workspace). It supports two modes:
-
-- **`per_request`** — simple; just `requestsPerMinute`. Good when the API charges flat per-request or cost doesn't vary much.
-- **`custom`** — `requestsPerMinute` plus additional `dimensions` (e.g., `tokens`, `search_units`). Each dimension has its own `limitPerMinute` and an `extractUsage` function that reads actual usage from the response. Use when the API charges on a variable metric (tokens, credits) and you want to cap that metric too.
-
-When choosing values for `requestsPerMinute` and any dimension limits:
-
-- **Stay well below the API's per-key limit** — our keys are shared across all workspaces. If the API allows 60 RPM per key and we have 3 keys, the global ceiling is ~180 RPM. Set the per-workspace limit low enough (e.g., 20-60 RPM) that many workspaces can coexist without collectively hitting the API's ceiling.
-- **Account for key pooling** — our round-robin distributes requests across `N` hosted keys, so the effective API-side rate per key is `(total requests) / N`. But per-workspace limits are enforced *before* key selection, so they apply regardless of key count.
-- **Prefer conservative defaults** — it's easy to raise limits later but hard to claw back after users depend on high throughput.
-
-## Step 3: Add `hosting` Config to the Tool
-
-Add a `hosting` object to the tool's `ToolConfig`. This tells the execution layer how to acquire hosted keys, calculate cost, and rate-limit.
-
-```typescript
-hosting: {
-  envKeyPrefix: 'YOUR_SERVICE_API_KEY',
-  apiKeyParam: 'apiKey',
-  byokProviderId: 'your_service',
-  pricing: {
-    type: 'custom',
-    getCost: (_params, output) => {
-      if (output.creditsUsed == null) {
-        throw new Error('Response missing creditsUsed field')
-      }
-      const creditsUsed = output.creditsUsed as number
-      const cost = creditsUsed * 0.001 // dollars per credit
-      return { cost, metadata: { creditsUsed } }
-    },
-  },
-  rateLimit: {
-    mode: 'per_request',
-    requestsPerMinute: 100,
-  },
-},
-```
-
-### Hosted Key Env Var Convention
-
-Keys use a numbered naming pattern driven by a count env var:
-
-```
-YOUR_SERVICE_API_KEY_COUNT=3
-YOUR_SERVICE_API_KEY_1=sk-...
-YOUR_SERVICE_API_KEY_2=sk-...
-YOUR_SERVICE_API_KEY_3=sk-...
-```
-
-The `envKeyPrefix` value (`YOUR_SERVICE_API_KEY`) determines which env vars are read at runtime. Adding more keys only requires bumping the count and adding the new env var.
-
-### Pricing: Prefer API-Reported Cost
-
-Always prefer using cost data returned by the API (e.g., `creditsUsed`, `costDollars`). This is the most accurate because it accounts for variable pricing tiers, feature modifiers, and plan-level discounts.
-
-**When the API reports cost** — use it directly and throw if missing:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (output.creditsUsed == null) {
-      throw new Error('Response missing creditsUsed field')
-    }
-    // $0.001 per credit — from https://example.com/pricing
-    const cost = (output.creditsUsed as number) * 0.001
-    return { cost, metadata: { creditsUsed: output.creditsUsed } }
-  },
-},
-```
-
-**When the API does NOT report cost** — compute it from params/output based on the pricing docs, but still validate the data you depend on:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (!Array.isArray(output.searchResults)) {
-      throw new Error('Response missing searchResults, cannot determine cost')
-    }
-    // Serper: 1 credit for <=10 results, 2 credits for >10 — from https://serper.dev/pricing
-    const credits = Number(params.num) > 10 ? 2 : 1
-    return { cost: credits * 0.001, metadata: { credits } }
-  },
-},
-```
-
-**`getCost` must always throw** if it cannot determine cost. Never silently fall back to a default — this would hide billing inaccuracies.
-
-### Capturing Cost Data from the API
-
-If the API returns cost info, capture it in `transformResponse` so `getCost` can read it from the output:
-
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      results: data.results,
-      creditsUsed: data.creditsUsed,  // pass through for getCost
-    },
-  }
-},
-```
-
-For async/polling tools, capture it in `postProcess` when the job completes:
-
-```typescript
-if (jobData.status === 'completed') {
-  result.output = {
-    data: jobData.data,
-    creditsUsed: jobData.creditsUsed,
-  }
-}
-```
-
-## Step 4: Hide the API Key Field When Hosted
-
-In the block config (`blocks/blocks/{service}.ts`), add `hideWhenHosted: true` to the API key subblock. This hides the field on hosted Sim since the platform provides the key:
-
-```typescript
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-},
-```
-
-The visibility is controlled by `isSubBlockHidden()` in `lib/workflows/subblocks/visibility.ts`, which checks both the `isHosted` feature flag (`hideWhenHosted`) and optional env var conditions (`hideWhenEnvSet`).
-
-### Excluding Specific Operations from Hosted Key Support
-
-When a block has multiple operations but some operations should **not** use a hosted key (e.g., the underlying API is deprecated, unsupported, or too expensive), use the **duplicate apiKey subblock** pattern. This is the same pattern Exa uses for its `research` operation:
-
-1. **Remove the `hosting` config** from the tool definition for that operation — it must not have a `hosting` object at all.
-2. **Duplicate the `apiKey` subblock** in the block config with opposing conditions:
-
-```typescript
-// API Key — hidden when hosted for operations with hosted key support
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-  condition: { field: 'operation', value: 'unsupported_op', not: true },
-},
-// API Key — always visible for unsupported_op (no hosted key support)
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  condition: { field: 'operation', value: 'unsupported_op' },
-},
-```
-
-Both subblocks share the same `id: 'apiKey'`, so the same value flows to the tool. The conditions ensure only one is visible at a time. The first has `hideWhenHosted: true` and shows for all hosted operations; the second has no `hideWhenHosted` and shows only for the excluded operation — meaning users must always provide their own key for that operation.
-
-To exclude multiple operations, use an array: `{ field: 'operation', value: ['op_a', 'op_b'] }`.
-
-**Reference implementations:**
-- **Exa** (`blocks/blocks/exa.ts`): `research` operation excluded from hosting — lines 309-329
-- **Google Maps** (`blocks/blocks/google_maps.ts`): `speed_limits` operation excluded from hosting (deprecated Roads API)
-
-## Step 5: Add to the BYOK Settings UI
-
-Add an entry to the `PROVIDERS` array in the BYOK settings component so users can bring their own key. You need the service icon from `components/icons.tsx`:
-
-```typescript
-{
-  id: 'your_service',
-  name: 'Your Service',
-  icon: YourServiceIcon,
-  description: 'What this service does',
-  placeholder: 'Enter your API key',
-},
-```
-
-## Step 6: Summarize Pricing and Throttling Comparison
-
-After all code changes are complete, output a detailed summary to the user covering:
-
-### What to include
-
-1. **API's pricing model** — how the service charges (per token, per credit, per request, etc.), the specific rates found in docs, and whether the API reports cost in responses.
-2. **Our `getCost` approach** — how we calculate cost, what fields we depend on, and any assumptions or estimates (especially when the API doesn't report exact dollar cost).
-3. **API's rate limits** — the documented limits (RPM, TPM, concurrent, etc.), which plan tier they apply to, and whether they're per-key or per-account.
-4. **Our `rateLimit` config** — what we set for `requestsPerMinute` (and dimensions if custom mode), why we chose those values, and how they compare to the API's limits.
-5. **Key pooling impact** — how many hosted keys we expect, and how round-robin distribution affects the effective per-key rate at the API.
-6. **Gaps or risks** — anything the API charges for that we don't meter, rate limit dimensions we chose not to enforce, or pricing that may be inaccurate due to variable model/tier costs.
-
-### Format
-
-Present this as a structured summary with clear headings. Example:
-
-```
-### Pricing
-- **API charges**: $X per 1M tokens (input), $Y per 1M tokens (output) — varies by model
-- **Response reports cost?**: No — only token counts in `usage` field
-- **Our getCost**: Estimates cost at $Z per 1M total tokens based on median model pricing
-- **Risk**: Actual cost varies by model; our estimate may over/undercharge for cheap/expensive models
-
-### Throttling
-- **API limits**: 300 RPM per key (paid tier), 60 RPM (free tier)
-- **Per-key or per-account**: Per key — more keys = more throughput
-- **Our config**: 60 RPM per workspace (per_request mode)
-- **With N keys**: Effective per-key rate is (total RPM across workspaces) / N
-- **Headroom**: Comfortable — even 10 active workspaces at full rate = 600 RPM / 3 keys = 200 RPM per key, under the 300 RPM API limit
-```
-
-This summary helps reviewers verify that the pricing and rate limiting are well-calibrated and surfaces any risks that need monitoring.
-
-## Checklist
-
-- [ ] Provider added to `BYOKProviderId` in `tools/types.ts`
-- [ ] Provider added to `VALID_PROVIDERS` in the BYOK keys API route
-- [ ] API pricing docs researched — understand per-unit cost and whether the API reports cost in responses
-- [ ] API rate limits researched — understand RPM/TPM limits, per-key vs per-account, and plan tiers
-- [ ] `hosting` config added to the tool with `envKeyPrefix`, `apiKeyParam`, `byokProviderId`, `pricing`, and `rateLimit`
-- [ ] `getCost` throws if required cost data is missing from the response
-- [ ] Cost data captured in `transformResponse` or `postProcess` if API provides it
-- [ ] `hideWhenHosted: true` added to the API key subblock in the block config
-- [ ] Provider entry added to the BYOK settings UI with icon and description
-- [ ] Env vars documented: `{PREFIX}_COUNT` and `{PREFIX}_1..N`
-- [ ] Pricing and throttling summary provided to reviewer

.cursor/commands/add-integration.md

@@ -1,759 +0,0 @@
-# Add Integration Skill
-
-You are an expert at adding complete integrations to Sim. This skill orchestrates the full process of adding a new service integration.
-
-## Overview
-
-Adding an integration involves these steps in order:
-1. **Research** - Read the service's API documentation
-2. **Create Tools** - Build tool configurations for each API operation
-3. **Create Block** - Build the block UI configuration
-4. **Add Icon** - Add the service's brand icon
-5. **Create Triggers** (optional) - If the service supports webhooks
-6. **Register** - Register tools, block, and triggers in their registries
-7. **Generate Docs** - Run the docs generation script
-
-## Step 1: Research the API
-
-Before writing any code:
-1. Use Context7 to find official documentation: `mcp__plugin_context7_context7__resolve-library-id`
-2. Or use WebFetch to read API docs directly
-3. Identify:
-   - Authentication method (OAuth, API Key, both)
-   - Available operations (CRUD, search, etc.)
-   - Required vs optional parameters
-   - Response structures
-
-## Step 2: Create Tools
-
-### Directory Structure
-```
-apps/sim/tools/{service}/
-├── index.ts          # Barrel exports
-├── types.ts          # TypeScript interfaces
-├── {action1}.ts      # Tool for action 1
-├── {action2}.ts      # Tool for action 2
-└── ...
-```
-
-### Key Patterns
-
-**types.ts:**
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-export interface {Service}{Action}Params {
-  accessToken: string      // For OAuth services
-  // OR
-  apiKey: string          // For API key services
-
-  requiredParam: string
-  optionalParam?: string
-}
-
-export interface {Service}Response extends ToolResponse {
-  output: {
-    // Define output structure
-  }
-}
-```
-
-**Tool file pattern:**
-```typescript
-export const {service}{Action}Tool: ToolConfig<Params, Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: '...',
-  version: '1.0.0',
-
-  oauth: { required: true, provider: '{service}' },  // If OAuth
-
-  params: {
-    accessToken: { type: 'string', required: true, visibility: 'hidden', description: '...' },
-    // ... other params
-  },
-
-  request: { url, method, headers, body },
-
-  transformResponse: async (response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        field: data.field ?? null,  // Always handle nullables
-      },
-    }
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Critical Rules
-- `visibility: 'hidden'` for OAuth tokens
-- `visibility: 'user-only'` for API keys and user credentials
-- `visibility: 'user-or-llm'` for operation parameters
-- Always use `?? null` for nullable API response fields
-- Always use `?? []` for optional array fields
-- Set `optional: true` for outputs that may not exist
-- Never output raw JSON dumps - extract meaningful fields
-- When using `type: 'json'` and you know the object shape, define `properties` with the inner fields so downstream consumers know the structure. Only use bare `type: 'json'` when the shape is truly dynamic
-
-## Step 3: Create Block
-
-### File Location
-`apps/sim/blocks/blocks/{service}.ts`
-
-### Block Structure
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {Service}Block: BlockConfig = {
-  type: '{service}',
-  name: '{Service}',
-  description: '...',
-  longDescription: '...',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
-  bgColor: '#HEXCOLOR',
-  icon: {Service}Icon,
-  authMode: AuthMode.OAuth,  // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Operation dropdown
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Operation 1', id: 'action1' },
-        { label: 'Operation 2', id: 'action2' },
-      ],
-      value: () => 'action1',
-    },
-    // Credential field
-    {
-      id: 'credential',
-      title: '{Service} Account',
-      type: 'oauth-input',
-      serviceId: '{service}',
-      requiredScopes: getScopesForService('{service}'),
-      required: true,
-    },
-    // Conditional fields per operation
-    // ...
-  ],
-
-  tools: {
-    access: ['{service}_action1', '{service}_action2'],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-    },
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Key SubBlock Patterns
-
-**Condition-based visibility:**
-```typescript
-{
-  id: 'resourceId',
-  title: 'Resource ID',
-  type: 'short-input',
-  condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-  required: { field: 'operation', value: ['read', 'update', 'delete'] },
-}
-```
-
-**DependsOn for cascading selectors:**
-```typescript
-{
-  id: 'project',
-  type: 'project-selector',
-  dependsOn: ['credential'],
-},
-{
-  id: 'issue',
-  type: 'file-selector',
-  dependsOn: ['credential', 'project'],
-}
-```
-
-**Basic/Advanced mode for dual UX:**
-```typescript
-// Basic: Visual selector
-{
-  id: 'channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',
-  dependsOn: ['credential'],
-},
-// Advanced: Manual input
-{
-  id: 'channelId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',
-}
-```
-
-**Critical Canonical Param Rules:**
-- `canonicalParamId` must NOT match any subblock's `id` in the block
-- `canonicalParamId` must be unique per operation/condition context
-- Only use `canonicalParamId` to link basic/advanced alternatives for the same logical parameter
-- `mode` only controls UI visibility, NOT serialization. Without `canonicalParamId`, both basic and advanced field values would be sent
-- Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions
-- **Required consistency:** If one subblock in a canonical group has `required: true`, ALL subblocks in that group must have `required: true` (prevents bypassing validation by switching modes)
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs (e.g., `fileSelector`, `manualFileId`)
-- **Params function:** Must use canonical param IDs, NOT raw subblock IDs (raw IDs are deleted after canonical transformation)
-
-## Step 4: Add Icon
-
-### File Location
-`apps/sim/components/icons.tsx`
-
-### Pattern
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg
-      {...props}
-      viewBox="0 0 24 24"
-      fill="none"
-      xmlns="http://www.w3.org/2000/svg"
-    >
-      {/* SVG paths from user-provided SVG */}
-    </svg>
-  )
-}
-```
-
-### Getting Icons
-**Do NOT search for icons yourself.** At the end of implementation, ask the user to provide the SVG:
-
-```
-I've completed the integration. Before I can add the icon, please provide the SVG for {Service}.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-Once the user provides the SVG:
-1. Extract the SVG paths/content
-2. Create a React component that spreads props
-3. Ensure viewBox is preserved from the original SVG
-
-## Step 5: Create Triggers (Optional)
-
-If the service supports webhooks, create triggers using the generic `buildTriggerSubBlocks` helper.
-
-### Directory Structure
-```
-apps/sim/triggers/{service}/
-├── index.ts      # Barrel exports
-├── utils.ts      # Trigger options, setup instructions, extra fields
-├── {event_a}.ts  # Primary trigger (includes dropdown)
-├── {event_b}.ts  # Secondary triggers (no dropdown)
-└── webhook.ts    # Generic webhook (optional)
-```
-
-### Key Pattern
-
-```typescript
-import { buildTriggerSubBlocks } from '@/triggers'
-import { {service}TriggerOptions, {service}SetupInstructions, build{Service}ExtraFields } from './utils'
-
-// Primary trigger - includeDropdown: true
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,  // Only for primary trigger!
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  // ...
-}
-
-// Secondary triggers - no dropdown
-export const {service}EventBTrigger: TriggerConfig = {
-  id: '{service}_event_b',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_b',
-    triggerOptions: {service}TriggerOptions,
-    // No includeDropdown!
-    setupInstructions: {service}SetupInstructions('Event B'),
-    extraFields: build{Service}ExtraFields('{service}_event_b'),
-  }),
-  // ...
-}
-```
-
-### Connect to Block
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-  subBlocks: [
-    // Tool fields...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-}
-```
-
-See `/add-trigger` skill for complete documentation.
-
-## Step 6: Register Everything
-
-### Tools Registry (`apps/sim/tools/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}Action1Tool,
-  {service}Action2Tool,
-} from '@/tools/{service}'
-
-// Add to tools object (alphabetically)
-export const tools: Record<string, ToolConfig> = {
-  // ... existing tools ...
-  {service}_action1: {service}Action1Tool,
-  {service}_action2: {service}Action2Tool,
-}
-```
-
-### Block Registry (`apps/sim/blocks/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import { {Service}Block } from '@/blocks/blocks/{service}'
-
-// Add to registry (alphabetically)
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  {service}: {Service}Block,
-}
-```
-
-### Trigger Registry (`apps/sim/triggers/registry.ts`) - If triggers exist
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}EventATrigger,
-  {service}EventBTrigger,
-  {service}WebhookTrigger,
-} from '@/triggers/{service}'
-
-// Add to TRIGGER_REGISTRY (alphabetically)
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing triggers ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-  {service}_webhook: {service}WebhookTrigger,
-}
-```
-
-## Step 7: Generate Docs
-
-Run the documentation generator:
-```bash
-bun run scripts/generate-docs.ts
-```
-
-This creates `apps/docs/content/docs/en/tools/{service}.mdx`
-
-## V2 Integration Pattern
-
-If creating V2 versions (API-aligned outputs):
-
-1. **V2 Tools** - Add `_v2` suffix, version `2.0.0`, flat outputs
-2. **V2 Block** - Add `_v2` type, use `createVersionedToolSelector`
-3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`
-4. **Registry** - Register both versions
-
-```typescript
-// In registry
-{service}: {Service}Block,        // V1 (legacy, hidden)
-{service}_v2: {Service}V2Block,   // V2 (visible)
-```
-
-## Complete Checklist
-
-### Tools
-- [ ] Created `tools/{service}/` directory
-- [ ] Created `types.ts` with all interfaces
-- [ ] Created tool file for each operation
-- [ ] All params have correct visibility
-- [ ] All nullable fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all tools in `tools/registry.ts`
-
-### Block
-- [ ] Created `blocks/blocks/{service}.ts`
-- [ ] Set `integrationType` to the correct `IntegrationType` enum value
-- [ ] Set `tags` array with all applicable `IntegrationTag` values
-- [ ] Defined operation dropdown with all operations
-- [ ] Added credential field with `requiredScopes: getScopesForService('{service}')`
-- [ ] Added conditional fields per operation
-- [ ] Set up dependsOn for cascading selectors
-- [ ] Configured tools.access with all tool IDs
-- [ ] Configured tools.config.tool selector
-- [ ] Defined outputs matching tool outputs
-- [ ] Registered block in `blocks/registry.ts`
-- [ ] If triggers: set `triggers.enabled` and `triggers.available`
-- [ ] If triggers: spread trigger subBlocks with `getTrigger()`
-
-### OAuth Scopes (if OAuth service)
-- [ ] Defined scopes in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS`
-- [ ] Added scope descriptions in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] Used `getCanonicalScopesForProvider()` in `auth.ts` (never hardcode)
-- [ ] Used `getScopesForService()` in block `requiredScopes` (never hardcode)
-
-### Icon
-- [ ] Asked user to provide SVG
-- [ ] Added icon to `components/icons.tsx`
-- [ ] Icon spreads props correctly
-
-### Triggers (if service supports webhooks)
-- [ ] Created `triggers/{service}/` directory
-- [ ] Created `utils.ts` with options, instructions, and extra fields helpers
-- [ ] Primary trigger uses `includeDropdown: true`
-- [ ] Secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all triggers in `triggers/registry.ts`
-
-### Docs
-- [ ] Ran `bun run scripts/generate-docs.ts`
-- [ ] Verified docs file created
-
-### Final Validation (Required)
-- [ ] Read every tool file and cross-referenced inputs/outputs against the API docs
-- [ ] Verified block subBlocks cover all required tool params with correct conditions
-- [ ] Verified block outputs match what the tools actually return
-- [ ] Verified `tools.config.params` correctly maps and coerces all param types
-
-## Example Command
-
-When the user asks to add an integration:
-
-```
-User: Add a Stripe integration
-
-You: I'll add the Stripe integration. Let me:
-
-1. First, research the Stripe API using Context7
-2. Create the tools for key operations (payments, subscriptions, etc.)
-3. Create the block with operation dropdown
-4. Register everything
-5. Generate docs
-6. Ask you for the Stripe icon SVG
-
-[Proceed with implementation...]
-
-[After completing steps 1-5...]
-
-I've completed the Stripe integration. Before I can add the icon, please provide the SVG for Stripe.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-## File Handling
-
-When your integration handles file uploads or downloads, follow these patterns to work with `UserFile` objects consistently.
-
-### What is a UserFile?
-
-A `UserFile` is the standard file representation in Sim:
-
-```typescript
-interface UserFile {
-  id: string       // Unique identifier
-  name: string     // Original filename
-  url: string      // Presigned URL for download
-  size: number     // File size in bytes
-  type: string     // MIME type (e.g., 'application/pdf')
-  base64?: string  // Optional base64 content (if small file)
-  key?: string     // Internal storage key
-  context?: object // Storage context metadata
-}
-```
-
-### File Input Pattern (Uploads)
-
-For tools that accept file uploads, **always route through an internal API endpoint** rather than calling external APIs directly. This ensures proper file content retrieval.
-
-#### 1. Block SubBlocks for File Input
-
-Use the basic/advanced mode pattern:
-
-```typescript
-// Basic mode: File upload UI
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Maps to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from previous block
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Same canonical param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical:** `canonicalParamId` must NOT match any subblock `id`.
-
-#### 2. Normalize File Input in Block Config
-
-In `tools.config.tool`, use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  config: {
-    tool: (params) => {
-      // Normalize file from basic (uploadFile), advanced (fileRef), or legacy (fileContent)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `{service}_${params.operation}`
-    },
-  },
-}
-```
-
-#### 3. Create Internal API Route
-
-Create `apps/sim/app/api/tools/{service}/{action}/route.ts`:
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { NextResponse, type NextRequest } from 'next/server'
-import { z } from 'zod'
-import { checkInternalAuth } from '@/lib/auth/hybrid'
-import { generateRequestId } from '@/lib/core/utils/request'
-import { FileInputSchema, type RawFileInput } from '@/lib/uploads/utils/file-schemas'
-import { processFilesToUserFiles } from '@/lib/uploads/utils/file-utils'
-import { downloadFileFromStorage } from '@/lib/uploads/utils/file-utils.server'
-
-const logger = createLogger('{Service}UploadAPI')
-
-const RequestSchema = z.object({
-  accessToken: z.string(),
-  file: FileInputSchema.optional().nullable(),
-  // Legacy field for backwards compatibility
-  fileContent: z.string().optional().nullable(),
-  // ... other params
-})
-
-export async function POST(request: NextRequest) {
-  const requestId = generateRequestId()
-
-  const authResult = await checkInternalAuth(request, { requireWorkflowId: false })
-  if (!authResult.success) {
-    return NextResponse.json({ success: false, error: 'Unauthorized' }, { status: 401 })
-  }
-
-  const body = await request.json()
-  const data = RequestSchema.parse(body)
-
-  let fileBuffer: Buffer
-  let fileName: string
-
-  // Prefer UserFile input, fall back to legacy base64
-  if (data.file) {
-    const userFiles = processFilesToUserFiles([data.file as RawFileInput], requestId, logger)
-    if (userFiles.length === 0) {
-      return NextResponse.json({ success: false, error: 'Invalid file' }, { status: 400 })
-    }
-    const userFile = userFiles[0]
-    fileBuffer = await downloadFileFromStorage(userFile, requestId, logger)
-    fileName = userFile.name
-  } else if (data.fileContent) {
-    // Legacy: base64 string (backwards compatibility)
-    fileBuffer = Buffer.from(data.fileContent, 'base64')
-    fileName = 'file'
-  } else {
-    return NextResponse.json({ success: false, error: 'File required' }, { status: 400 })
-  }
-
-  // Now call external API with fileBuffer
-  const response = await fetch('https://api.{service}.com/upload', {
-    method: 'POST',
-    headers: { Authorization: `Bearer ${data.accessToken}` },
-    body: new Uint8Array(fileBuffer),  // Convert Buffer for fetch
-  })
-
-  // ... handle response
-}
-```
-
-#### 4. Update Tool to Use Internal Route
-
-```typescript
-export const {service}UploadTool: ToolConfig<Params, Response> = {
-  id: '{service}_upload',
-  // ...
-  params: {
-    file: { type: 'file', required: false, visibility: 'user-or-llm' },
-    fileContent: { type: 'string', required: false, visibility: 'hidden' }, // Legacy
-  },
-  request: {
-    url: '/api/tools/{service}/upload',  // Internal route
-    method: 'POST',
-    body: (params) => ({
-      accessToken: params.accessToken,
-      file: params.file,
-      fileContent: params.fileContent,
-    }),
-  },
-}
-```
-
-### File Output Pattern (Downloads)
-
-For tools that return files, use `FileToolProcessor` to store files and return `UserFile` objects.
-
-#### In Tool transformResponse
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-transformResponse: async (response, context) => {
-  const data = await response.json()
-
-  // Process file outputs to UserFile objects
-  const fileProcessor = new FileToolProcessor(context)
-  const file = await fileProcessor.processFileData({
-    data: data.content,      // base64 or buffer
-    mimeType: data.mimeType,
-    filename: data.filename,
-  })
-
-  return {
-    success: true,
-    output: { file },
-  }
-}
-```
-
-#### In API Route (for complex file handling)
-
-```typescript
-// Return file data that FileToolProcessor can handle
-return NextResponse.json({
-  success: true,
-  output: {
-    file: {
-      data: base64Content,
-      mimeType: 'application/pdf',
-      filename: 'document.pdf',
-    },
-  },
-})
-```
-
-### Key Helpers Reference
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get file Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-| `isUserFile` | `@/lib/core/utils/user-file` | Type guard for UserFile objects |
-| `FileInputSchema` | `@/lib/uploads/utils/file-schemas` | Zod schema for file validation |
-
-### Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. Examples: pagination tokens, time range filters, sort order, max results, reply settings.
-
-### WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually:
-- **Timestamps**: Use `generationType: 'timestamp'` to inject current date context into the AI prompt
-- **JSON arrays**: Use `generationType: 'json-object'` for structured data
-- **Complex queries**: Use a descriptive prompt explaining the expected format
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-```
-
-### OAuth Scopes (Centralized System)
-
-Scopes are maintained in a single source of truth and reused everywhere:
-
-1. **Define scopes** in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-2. **Add descriptions** in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for the OAuth modal UI
-3. **Reference in auth.ts** using `getCanonicalScopesForProvider(providerId)` from `@/lib/oauth/utils`
-4. **Reference in blocks** using `getScopesForService(serviceId)` from `@/lib/oauth/utils`
-
-**Never hardcode scope arrays** in `auth.ts` or block `requiredScopes`. Always import from the centralized source.
-
-```typescript
-// In auth.ts (Better Auth config)
-scopes: getCanonicalScopesForProvider('{service}'),
-
-// In block credential sub-block
-requiredScopes: getScopesForService('{service}'),
-```
-
-### Common Gotchas
-
-1. **OAuth serviceId must match** - The `serviceId` in oauth-input must match the OAuth provider configuration
-2. **All tool IDs MUST be snake_case** - `stripe_create_payment`, not `stripeCreatePayment`. This applies to tool `id` fields, registry keys, `tools.access` arrays, and `tools.config.tool` return values
-3. **Block type is snake_case** - `type: 'stripe'`, not `type: 'Stripe'`
-4. **Alphabetical ordering** - Keep imports and registry entries alphabetically sorted
-5. **Required can be conditional** - Use `required: { field: 'op', value: 'create' }` instead of always true
-6. **DependsOn clears options** - When a dependency changes, selector options are refetched
-7. **Never pass Buffer directly to fetch** - Convert to `new Uint8Array(buffer)` for TypeScript compatibility
-8. **Always handle legacy file params** - Keep hidden `fileContent` params for backwards compatibility
-9. **Optional fields use advanced mode** - Set `mode: 'advanced'` on rarely-used optional fields
-10. **Complex inputs need wandConfig** - Timestamps, JSON arrays, and other hard-to-type values should have `wandConfig` enabled
-11. **Never hardcode scopes** - Use `getScopesForService()` in blocks and `getCanonicalScopesForProvider()` in auth.ts
-12. **Always add scope descriptions** - New scopes must have entries in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`

.cursor/commands/add-tools.md

@@ -1,316 +0,0 @@
-# Add Tools Skill
-
-You are an expert at creating tool configurations for Sim integrations. Your job is to read API documentation and create properly structured tool files.
-
-## Your Task
-
-When the user asks you to create tools for a service:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Create the tools directory structure
-3. Generate properly typed tool configurations
-
-## Directory Structure
-
-Create files in `apps/sim/tools/{service}/`:
-```
-tools/{service}/
-├── index.ts      # Barrel export
-├── types.ts      # Parameter & response types
-└── {action}.ts   # Individual tool files (one per operation)
-```
-
-## Tool Configuration Structure
-
-Every tool MUST follow this exact structure:
-
-```typescript
-import type { {ServiceName}{Action}Params } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-interface {ServiceName}{Action}Response {
-  success: boolean
-  output: {
-    // Define output structure here
-  }
-}
-
-export const {serviceName}{Action}Tool: ToolConfig<
-  {ServiceName}{Action}Params,
-  {ServiceName}{Action}Response
-> = {
-  id: '{service}_{action}',           // snake_case, matches tool name
-  name: '{Service} {Action}',         // Human readable
-  description: 'Brief description',   // One sentence
-  version: '1.0.0',
-
-  // OAuth config (if service uses OAuth)
-  oauth: {
-    required: true,
-    provider: '{service}',            // Must match OAuth provider ID
-  },
-
-  params: {
-    // Hidden params (system-injected, only use hidden for oauth accessToken)
-    accessToken: {
-      type: 'string',
-      required: true,
-      visibility: 'hidden',
-      description: 'OAuth access token',
-    },
-    // User-only params (credentials, api key, IDs user must provide)
-    someId: {
-      type: 'string',
-      required: true,
-      visibility: 'user-only',
-      description: 'The ID of the resource',
-    },
-    // User-or-LLM params (everything else, can be provided by user OR computed by LLM)
-    query: {
-      type: 'string',
-      required: false,                // Use false for optional
-      visibility: 'user-or-llm',
-      description: 'Search query',
-    },
-  },
-
-  request: {
-    url: (params) => `https://api.service.com/v1/resource/${params.id}`,
-    method: 'POST',
-    headers: (params) => ({
-      Authorization: `Bearer ${params.accessToken}`,
-      'Content-Type': 'application/json',
-    }),
-    body: (params) => ({
-      // Request body - only for POST/PUT/PATCH
-      // Trim ID fields to prevent copy-paste whitespace errors:
-      // userId: params.userId?.trim(),
-    }),
-  },
-
-  transformResponse: async (response: Response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        // Map API response to output
-        // Use ?? null for nullable fields
-        // Use ?? [] for optional arrays
-      },
-    }
-  },
-
-  outputs: {
-    // Define each output field
-  },
-}
-```
-
-## Critical Rules for Parameters
-
-### Visibility Options
-- `'hidden'` - System-injected (OAuth tokens, internal params). User never sees.
-- `'user-only'` - User must provide (credentials, api keys, account-specific IDs)
-- `'user-or-llm'` - User provides OR LLM can compute (search queries, content, filters, most fall into this category)
-
-### Parameter Types
-- `'string'` - Text values
-- `'number'` - Numeric values
-- `'boolean'` - True/false
-- `'json'` - Complex objects (NOT 'object', use 'json')
-- `'file'` - Single file
-- `'file[]'` - Multiple files
-
-### Required vs Optional
-- Always explicitly set `required: true` or `required: false`
-- Optional params should have `required: false`
-
-## Critical Rules for Outputs
-
-### Output Types
-- `'string'`, `'number'`, `'boolean'` - Primitives
-- `'json'` - Complex objects (use this, NOT 'object')
-- `'array'` - Arrays with `items` property
-- `'object'` - Objects with `properties` property
-
-### Optional Outputs
-Add `optional: true` for fields that may not exist in the response:
-```typescript
-closedAt: {
-  type: 'string',
-  description: 'When the issue was closed',
-  optional: true,
-},
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **always define the inner structure** using `properties` so downstream consumers know what fields are available:
-
-```typescript
-// BAD: Opaque json with no info about what's inside
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-},
-
-// GOOD: Define the known properties
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-  properties: {
-    id: { type: 'string', description: 'Unique ID' },
-    status: { type: 'string', description: 'Current status' },
-    count: { type: 'number', description: 'Total count' },
-  },
-},
-```
-
-For arrays of objects, define the item structure:
-```typescript
-items: {
-  type: 'array',
-  description: 'List of items',
-  items: {
-    type: 'object',
-    properties: {
-      id: { type: 'string', description: 'Item ID' },
-      name: { type: 'string', description: 'Item name' },
-    },
-  },
-},
-```
-
-Only use bare `type: 'json'` without `properties` when the shape is truly dynamic or unknown.
-
-## Critical Rules for transformResponse
-
-### Handle Nullable Fields
-ALWAYS use `?? null` for fields that may be undefined:
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      id: data.id,
-      title: data.title,
-      body: data.body ?? null,           // May be undefined
-      assignee: data.assignee ?? null,   // May be undefined
-      labels: data.labels ?? [],         // Default to empty array
-      closedAt: data.closed_at ?? null,  // May be undefined
-    },
-  }
-}
-```
-
-### Never Output Raw JSON Dumps
-DON'T do this:
-```typescript
-output: {
-  data: data,  // BAD - raw JSON dump
-}
-```
-
-DO this instead - extract meaningful fields:
-```typescript
-output: {
-  id: data.id,
-  name: data.name,
-  status: data.status,
-  metadata: {
-    createdAt: data.created_at,
-    updatedAt: data.updated_at,
-  },
-}
-```
-
-## Types File Pattern
-
-Create `types.ts` with interfaces for all params and responses:
-
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-// Parameter interfaces
-export interface {Service}{Action}Params {
-  accessToken: string
-  requiredField: string
-  optionalField?: string
-}
-
-// Response interfaces (extend ToolResponse)
-export interface {Service}{Action}Response extends ToolResponse {
-  output: {
-    field1: string
-    field2: number
-    optionalField?: string | null
-  }
-}
-```
-
-## Index.ts Barrel Export Pattern
-
-```typescript
-// Export all tools
-export { serviceTool1 } from './{action1}'
-export { serviceTool2 } from './{action2}'
-
-// Export types
-export * from './types'
-```
-
-## Registering Tools
-
-After creating tools, remind the user to:
-1. Import tools in `apps/sim/tools/registry.ts`
-2. Add to the `tools` object with snake_case keys:
-```typescript
-import { serviceActionTool } from '@/tools/{service}'
-
-export const tools = {
-  // ... existing tools ...
-  {service}_{action}: serviceActionTool,
-}
-```
-
-## V2 Tool Pattern
-
-If creating V2 tools (API-aligned outputs), use `_v2` suffix:
-- Tool ID: `{service}_{action}_v2`
-- Variable name: `{action}V2Tool`
-- Version: `'2.0.0'`
-- Outputs: Flat, API-aligned (no content/metadata wrapper)
-
-## Naming Convention
-
-All tool IDs MUST use `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase for tool IDs.
-
-## Checklist Before Finishing
-
-- [ ] All tool IDs use snake_case
-- [ ] All params have explicit `required: true` or `required: false`
-- [ ] All params have appropriate `visibility`
-- [ ] All nullable response fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] No raw JSON dumps in outputs
-- [ ] Types file has all interfaces
-- [ ] Index.ts exports all tools
-
-## Final Validation (Required)
-
-After creating all tools, you MUST validate every tool before finishing:
-
-1. **Read every tool file** you created — do not skip any
-2. **Cross-reference with the API docs** to verify:
-   - All required params are marked `required: true`
-   - All optional params are marked `required: false`
-   - Param types match the API (string, number, boolean, json)
-   - Request URL, method, headers, and body match the API spec
-   - `transformResponse` extracts the correct fields from the API response
-   - All output fields match what the API actually returns
-   - No fields are missing from outputs that the API provides
-   - No extra fields are defined in outputs that the API doesn't return
-3. **Verify consistency** across tools:
-   - Shared types in `types.ts` match all tools that use them
-   - Tool IDs in the barrel export match the tool file definitions
-   - Error handling is consistent (error checks, meaningful messages)

.cursor/commands/add-trigger.md

@@ -1,492 +0,0 @@
-# Add Trigger
-
-You are an expert at creating webhook and polling triggers for Sim. You understand the trigger system, the generic `buildTriggerSubBlocks` helper, polling infrastructure, and how triggers connect to blocks.
-
-## Your Task
-
-1. Research what webhook events the service supports — if the service lacks reliable webhooks, use polling
-2. Create the trigger files using the generic builder (webhook) or manual config (polling)
-3. Create a provider handler (webhook) or polling handler (polling)
-4. Register triggers and connect them to the block
-
-## Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel exports
-├── utils.ts              # Service-specific helpers (options, instructions, extra fields, outputs)
-├── {event_a}.ts          # Primary trigger (includes dropdown)
-├── {event_b}.ts          # Secondary trigger (no dropdown)
-└── webhook.ts            # Generic webhook trigger (optional, for "all events")
-
-apps/sim/lib/webhooks/
-├── provider-subscription-utils.ts  # Shared subscription helpers (getProviderConfig, getNotificationUrl)
-├── providers/
-│   ├── {service}.ts       # Provider handler (auth, formatInput, matchEvent, subscriptions)
-│   ├── types.ts           # WebhookProviderHandler interface
-│   ├── utils.ts           # Shared helpers (createHmacVerifier, verifyTokenAuth, skipByEventTypes)
-│   └── registry.ts        # Handler map + default handler
-```
-
-## Step 1: Create `utils.ts`
-
-This file contains all service-specific helpers used by triggers.
-
-```typescript
-import type { SubBlockConfig } from '@/blocks/types'
-import type { TriggerOutput } from '@/triggers/types'
-
-export const {service}TriggerOptions = [
-  { label: 'Event A', id: '{service}_event_a' },
-  { label: 'Event B', id: '{service}_event_b' },
-]
-
-export function {service}SetupInstructions(eventType: string): string {
-  const instructions = [
-    'Copy the <strong>Webhook URL</strong> above',
-    'Go to <strong>{Service} Settings > Webhooks</strong>',
-    `Select the <strong>${eventType}</strong> event type`,
-    'Paste the webhook URL and save',
-    'Click "Save" above to activate your trigger',
-  ]
-  return instructions
-    .map((instruction, index) =>
-      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
-    )
-    .join('')
-}
-
-export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
-  return [
-    {
-      id: 'projectId',
-      title: 'Project ID (Optional)',
-      type: 'short-input',
-      placeholder: 'Leave empty for all projects',
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-  ]
-}
-
-export function build{Service}Outputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'The type of event' },
-    resourceId: { type: 'string', description: 'ID of the affected resource' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Step 2: Create Trigger Files
-
-**Primary trigger** — MUST include `includeDropdown: true`:
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { buildTriggerSubBlocks } from '@/triggers'
-import { build{Service}ExtraFields, build{Service}Outputs, {service}SetupInstructions, {service}TriggerOptions } from '@/triggers/{service}/utils'
-import type { TriggerConfig } from '@/triggers/types'
-
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  name: '{Service} Event A',
-  provider: '{service}',
-  description: 'Trigger workflow when Event A occurs',
-  version: '1.0.0',
-  icon: {Service}Icon,
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  outputs: build{Service}Outputs(),
-  webhook: { method: 'POST', headers: { 'Content-Type': 'application/json' } },
-}
-```
-
-**Secondary triggers** — NO `includeDropdown` (it's already in the primary):
-
-```typescript
-export const {service}EventBTrigger: TriggerConfig = {
-  // Same as above but: id: '{service}_event_b', no includeDropdown
-}
-```
-
-## Step 3: Register and Wire
-
-### `apps/sim/triggers/{service}/index.ts`
-
-```typescript
-export { {service}EventATrigger } from './event_a'
-export { {service}EventBTrigger } from './event_b'
-```
-
-### `apps/sim/triggers/registry.ts`
-
-```typescript
-import { {service}EventATrigger, {service}EventBTrigger } from '@/triggers/{service}'
-
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-}
-```
-
-### Block file (`apps/sim/blocks/blocks/{service}.ts`)
-
-Wire triggers into the block so the trigger UI appears and `generate-docs.ts` discovers them. Two changes are needed:
-
-1. **Spread trigger subBlocks** at the end of the block's `subBlocks` array
-2. **Add `triggers` property** after `outputs` with `enabled: true` and `available: [...]`
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  // ...
-  subBlocks: [
-    // Regular tool subBlocks first...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-  // ... tools, inputs, outputs ...
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-}
-```
-
-**Versioned blocks (V1 + V2):** Many integrations have a hidden V1 block and a visible V2 block. Where you add the trigger wiring depends on how V2 inherits from V1:
-
-- **V2 uses `...V1Block` spread** (e.g., Google Calendar): Add trigger to V1 — V2 inherits both `subBlocks` and `triggers` automatically.
-- **V2 defines its own `subBlocks`** (e.g., Google Sheets): Add trigger to V2 (the visible block). V1 is hidden and doesn't need it.
-- **Single block, no V2** (e.g., Google Drive): Add trigger directly.
-
-`generate-docs.ts` deduplicates by base type (first match wins). If V1 is processed first without triggers, the V2 triggers won't appear in `integrations.json`. Always verify by checking the output after running the script.
-
-## Provider Handler
-
-All provider-specific webhook logic lives in a single handler file: `apps/sim/lib/webhooks/providers/{service}.ts`.
-
-### When to Create a Handler
-
-| Behavior | Method | Examples |
-|---|---|---|
-| HMAC signature auth | `verifyAuth` via `createHmacVerifier` | Ashby, Jira, Linear, Typeform |
-| Custom token auth | `verifyAuth` via `verifyTokenAuth` | Generic, Google Forms |
-| Event filtering | `matchEvent` | GitHub, Jira, Attio, HubSpot |
-| Idempotency dedup | `extractIdempotencyId` | Slack, Stripe, Linear, Jira |
-| Custom input formatting | `formatInput` | Slack, Teams, Attio, Ashby |
-| Auto webhook creation | `createSubscription` | Ashby, Grain, Calendly, Airtable |
-| Auto webhook deletion | `deleteSubscription` | Ashby, Grain, Calendly, Airtable |
-| Challenge/verification | `handleChallenge` | Slack, WhatsApp, Teams |
-| Custom success response | `formatSuccessResponse` | Slack, Twilio Voice, Teams |
-
-If none apply, you don't need a handler. The default handler provides bearer token auth.
-
-### Example Handler
-
-```typescript
-import crypto from 'crypto'
-import { createLogger } from '@sim/logger'
-import { safeCompare } from '@/lib/core/security/encryption'
-import type { EventMatchContext, FormatInputContext, FormatInputResult, WebhookProviderHandler } from '@/lib/webhooks/providers/types'
-import { createHmacVerifier } from '@/lib/webhooks/providers/utils'
-
-const logger = createLogger('WebhookProvider:{Service}')
-
-function validate{Service}Signature(secret: string, signature: string, body: string): boolean {
-  if (!secret || !signature || !body) return false
-  const computed = crypto.createHmac('sha256', secret).update(body, 'utf8').digest('hex')
-  return safeCompare(computed, signature)
-}
-
-export const {service}Handler: WebhookProviderHandler = {
-  verifyAuth: createHmacVerifier({
-    configKey: 'webhookSecret',
-    headerName: 'X-{Service}-Signature',
-    validateFn: validate{Service}Signature,
-    providerLabel: '{Service}',
-  }),
-
-  async matchEvent({ body, requestId, providerConfig }: EventMatchContext) {
-    const triggerId = providerConfig.triggerId as string | undefined
-    if (triggerId && triggerId !== '{service}_webhook') {
-      const { is{Service}EventMatch } = await import('@/triggers/{service}/utils')
-      if (!is{Service}EventMatch(triggerId, body as Record<string, unknown>)) return false
-    }
-    return true
-  },
-
-  async formatInput({ body }: FormatInputContext): Promise<FormatInputResult> {
-    const b = body as Record<string, unknown>
-    return {
-      input: {
-        eventType: b.type,
-        resourceId: (b.data as Record<string, unknown>)?.id || '',
-        resource: b.data,
-      },
-    }
-  },
-
-  extractIdempotencyId(body: unknown) {
-    const obj = body as Record<string, unknown>
-    return obj.id && obj.type ? `${obj.type}:${obj.id}` : null
-  },
-}
-```
-
-### Register the Handler
-
-In `apps/sim/lib/webhooks/providers/registry.ts`:
-
-```typescript
-import { {service}Handler } from '@/lib/webhooks/providers/{service}'
-
-const PROVIDER_HANDLERS: Record<string, WebhookProviderHandler> = {
-  // ... existing (alphabetical) ...
-  {service}: {service}Handler,
-}
-```
-
-## Output Alignment (Critical)
-
-There are two sources of truth that **MUST be aligned**:
-
-1. **Trigger `outputs`** — schema defining what fields SHOULD be available (UI tag dropdown)
-2. **`formatInput` on the handler** — implementation that transforms raw payload into actual data
-
-If they differ: the tag dropdown shows fields that don't exist, or actual data has fields users can't discover.
-
-**Rules for `formatInput`:**
-- Return `{ input: { ... } }` where inner keys match trigger `outputs` exactly
-- Return `{ input: ..., skip: { message: '...' } }` to skip execution
-- No wrapper objects or duplication
-- Use `null` for missing optional data
-
-## Automatic Webhook Registration
-
-If the service API supports programmatic webhook creation, implement `createSubscription` and `deleteSubscription` on the handler. The orchestration layer calls these automatically — **no code touches `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`**.
-
-```typescript
-import { getNotificationUrl, getProviderConfig } from '@/lib/webhooks/provider-subscription-utils'
-import type { DeleteSubscriptionContext, SubscriptionContext, SubscriptionResult } from '@/lib/webhooks/providers/types'
-
-export const {service}Handler: WebhookProviderHandler = {
-  async createSubscription(ctx: SubscriptionContext): Promise<SubscriptionResult | undefined> {
-    const config = getProviderConfig(ctx.webhook)
-    const apiKey = config.apiKey as string
-    if (!apiKey) throw new Error('{Service} API Key is required.')
-
-    const res = await fetch('https://api.{service}.com/webhooks', {
-      method: 'POST',
-      headers: { Authorization: `Bearer ${apiKey}`, 'Content-Type': 'application/json' },
-      body: JSON.stringify({ url: getNotificationUrl(ctx.webhook) }),
-    })
-
-    if (!res.ok) throw new Error(`{Service} error: ${res.status}`)
-    const { id } = (await res.json()) as { id: string }
-    return { providerConfigUpdates: { externalId: id } }
-  },
-
-  async deleteSubscription(ctx: DeleteSubscriptionContext): Promise<void> {
-    const config = getProviderConfig(ctx.webhook)
-    const { apiKey, externalId } = config as { apiKey?: string; externalId?: string }
-    if (!apiKey || !externalId) return
-    await fetch(`https://api.{service}.com/webhooks/${externalId}`, {
-      method: 'DELETE',
-      headers: { Authorization: `Bearer ${apiKey}` },
-    }).catch(() => {})
-  },
-}
-```
-
-**Key points:**
-- Throw from `createSubscription` — orchestration rolls back the DB webhook
-- Never throw from `deleteSubscription` — log non-fatally
-- Return `{ providerConfigUpdates: { externalId } }` — orchestration merges into `providerConfig`
-- Add `apiKey` field to `build{Service}ExtraFields` with `password: true`
-
-## Trigger Outputs Schema
-
-Trigger outputs use the same schema as block outputs (NOT tool outputs).
-
-**Supported:** `type` + `description` for leaf fields, nested objects for complex data.
-**NOT supported:** `optional: true`, `items` (those are tool-output-only features).
-
-```typescript
-export function buildOutputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'Event type' },
-    timestamp: { type: 'string', description: 'When it occurred' },
-    payload: { type: 'json', description: 'Full event payload' },
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Polling Triggers
-
-Use polling when the service lacks reliable webhooks (e.g., Google Sheets, Google Drive, Google Calendar, Gmail, RSS, IMAP). Polling triggers do NOT use `buildTriggerSubBlocks` — they define subBlocks manually.
-
-### Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel export
-└── poller.ts             # TriggerConfig with polling: true
-
-apps/sim/lib/webhooks/polling/
-└── {service}.ts           # PollingProviderHandler implementation
-```
-
-### Polling Handler (`apps/sim/lib/webhooks/polling/{service}.ts`)
-
-```typescript
-import { pollingIdempotency } from '@/lib/core/idempotency/service'
-import type { PollingProviderHandler, PollWebhookContext } from '@/lib/webhooks/polling/types'
-import { markWebhookFailed, markWebhookSuccess, resolveOAuthCredential, updateWebhookProviderConfig } from '@/lib/webhooks/polling/utils'
-import { processPolledWebhookEvent } from '@/lib/webhooks/processor'
-
-export const {service}PollingHandler: PollingProviderHandler = {
-  provider: '{service}',
-  label: '{Service}',
-
-  async pollWebhook(ctx: PollWebhookContext): Promise<'success' | 'failure'> {
-    const { webhookData, workflowData, requestId, logger } = ctx
-    const webhookId = webhookData.id
-
-    try {
-      // For OAuth services:
-      const accessToken = await resolveOAuthCredential(webhookData, '{service}', requestId, logger)
-      const config = webhookData.providerConfig as unknown as {Service}WebhookConfig
-
-      // First poll: seed state, emit nothing
-      if (!config.lastCheckedTimestamp) {
-        await updateWebhookProviderConfig(webhookId, { lastCheckedTimestamp: new Date().toISOString() }, logger)
-        await markWebhookSuccess(webhookId, logger)
-        return 'success'
-      }
-
-      // Fetch changes since last poll, process with idempotency
-      // ...
-
-      await markWebhookSuccess(webhookId, logger)
-      return 'success'
-    } catch (error) {
-      logger.error(`[${requestId}] Error processing {service} webhook ${webhookId}:`, error)
-      await markWebhookFailed(webhookId, logger)
-      return 'failure'
-    }
-  },
-}
-```
-
-**Key patterns:**
-- First poll seeds state and emits nothing (avoids flooding with existing data)
-- Use `pollingIdempotency.executeWithIdempotency(provider, key, callback)` for dedup
-- Use `processPolledWebhookEvent(webhookData, workflowData, payload, requestId)` to fire the workflow
-- Use `updateWebhookProviderConfig(webhookId, partialConfig, logger)` for read-merge-write on state
-- Use the latest server-side timestamp from API responses (not wall clock) to avoid clock skew
-
-### Trigger Config (`apps/sim/triggers/{service}/poller.ts`)
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { TriggerConfig } from '@/triggers/types'
-
-export const {service}PollingTrigger: TriggerConfig = {
-  id: '{service}_poller',
-  name: '{Service} Trigger',
-  provider: '{service}',
-  description: 'Triggers when ...',
-  version: '1.0.0',
-  icon: {Service}Icon,
-  polling: true,               // REQUIRED — routes to polling infrastructure
-
-  subBlocks: [
-    { id: 'triggerCredentials', type: 'oauth-input', title: 'Credentials', serviceId: '{service}', requiredScopes: [], required: true, mode: 'trigger', supportsCredentialSets: true },
-    // ... service-specific config fields (dropdowns, inputs, switches) ...
-    { id: 'triggerInstructions', type: 'text', title: 'Setup Instructions', hideFromPreview: true, mode: 'trigger', defaultValue: '...' },
-  ],
-
-  outputs: {
-    // Must match the payload shape from processPolledWebhookEvent
-  },
-}
-```
-
-### Registration (3 places)
-
-1. **`apps/sim/triggers/constants.ts`** — add provider to `POLLING_PROVIDERS` Set
-2. **`apps/sim/lib/webhooks/polling/registry.ts`** — import handler, add to `POLLING_HANDLERS`
-3. **`apps/sim/triggers/registry.ts`** — import trigger config, add to `TRIGGER_REGISTRY`
-
-### Helm Cron Job
-
-Add to `helm/sim/values.yaml` under the existing polling cron jobs:
-
-```yaml
-{service}WebhookPoll:
-  schedule: "*/1 * * * *"
-  concurrencyPolicy: Forbid
-  url: "http://sim:3000/api/webhooks/poll/{service}"
-```
-
-### Reference Implementations
-
-- Simple: `apps/sim/lib/webhooks/polling/rss.ts` + `apps/sim/triggers/rss/poller.ts`
-- Complex (OAuth, attachments): `apps/sim/lib/webhooks/polling/gmail.ts` + `apps/sim/triggers/gmail/poller.ts`
-- Cursor-based (changes API): `apps/sim/lib/webhooks/polling/google-drive.ts`
-- Timestamp-based: `apps/sim/lib/webhooks/polling/google-calendar.ts`
-
-## Checklist
-
-### Trigger Definition
-- [ ] Created `utils.ts` with options, instructions, extra fields, and output builders
-- [ ] Primary trigger has `includeDropdown: true`; secondary triggers do NOT
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-
-### Registration
-- [ ] All triggers in `triggers/registry.ts` → `TRIGGER_REGISTRY`
-- [ ] Block has `triggers.enabled: true` and lists all trigger IDs in `triggers.available`
-- [ ] Block spreads all trigger subBlocks: `...getTrigger('id').subBlocks`
-
-### Provider Handler (if needed)
-- [ ] Handler file at `apps/sim/lib/webhooks/providers/{service}.ts`
-- [ ] Registered in `providers/registry.ts` (alphabetical)
-- [ ] Signature validator is a private function inside the handler file
-- [ ] `formatInput` output keys match trigger `outputs` exactly
-- [ ] Event matching uses dynamic `await import()` for trigger utils
-
-### Auto Registration (if supported)
-- [ ] `createSubscription` and `deleteSubscription` on the handler
-- [ ] NO changes to `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] API key field uses `password: true`
-
-### Polling Trigger (if applicable)
-- [ ] Handler implements `PollingProviderHandler` at `lib/webhooks/polling/{service}.ts`
-- [ ] Trigger config has `polling: true` and defines subBlocks manually (no `buildTriggerSubBlocks`)
-- [ ] Provider string matches across: trigger config, handler, `POLLING_PROVIDERS`, polling registry
-- [ ] First poll seeds state and emits nothing
-- [ ] Added provider to `POLLING_PROVIDERS` in `triggers/constants.ts`
-- [ ] Added handler to `POLLING_HANDLERS` in `lib/webhooks/polling/registry.ts`
-- [ ] Added cron job to `helm/sim/values.yaml`
-- [ ] Payload shape matches trigger `outputs` schema
-
-### Testing
-- [ ] `bun run type-check` passes
-- [ ] Manually verify output keys match trigger `outputs` keys
-- [ ] Trigger UI shows correctly in the block

.cursor/commands/cleanup.md

@@ -1,20 +0,0 @@
-# Cleanup
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Steps
-
-Run each of these skills in order on the specified scope, passing through the scope and fix arguments. After each skill completes, move to the next. Do not skip any.
-
-1. `/you-might-not-need-an-effect $ARGUMENTS`
-2. `/you-might-not-need-a-memo $ARGUMENTS`
-3. `/you-might-not-need-a-callback $ARGUMENTS`
-4. `/you-might-not-need-state $ARGUMENTS`
-5. `/react-query-best-practices $ARGUMENTS`
-6. `/emcn-design-review $ARGUMENTS`
-
-After all skills have run, output a summary of what was found and fixed (or proposed) across all six passes.

.cursor/commands/council.md

@@ -1,7 +0,0 @@
-Based on the given area of interest, please:
-
-1. Dig around the codebase in terms of that given area of interest, gather general information such as keywords and architecture overview.
-2. Spawn off n=10 (unless specified otherwise) task agents to dig deeper into the codebase in terms of that given area of interest, some of them should be out of the box for variance.
-3. Once the task agents are done, use the information to do what the user wants.
-
-If user is in plan mode, use the information to create the plan.

.cursor/commands/emcn-design-review.md

@@ -1,74 +0,0 @@
-# EMCN Design Review
-
-Arguments:
-- scope: what to review (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses **emcn**, a custom component library built on Radix UI primitives with CVA variants and CSS variable design tokens. All UI must use emcn components and tokens.
-
-## Steps
-
-1. Read the emcn barrel export at `apps/sim/components/emcn/components/index.ts` to know what's available
-2. Read `apps/sim/app/_styles/globals.css` for CSS variable tokens
-3. Analyze the specified scope against every rule below
-4. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.
-
----
-
-## Imports
-
-- Import from `@/components/emcn` barrel, never subpaths
-- Icons from `@/components/emcn/icons` or `lucide-react`
-- Use `cn` from `@/lib/core/utils/cn` for conditional classes
-
-## Design Tokens
-
-Use CSS variable pattern (`text-[var(--text-primary)]`), never Tailwind semantics (`text-muted-foreground`) or hardcoded colors (`text-gray-500`, `#333`).
-
-**Text**: `--text-primary`, `--text-secondary`, `--text-tertiary`, `--text-muted`, `--text-icon`, `--text-inverse`, `--text-error`
-**Surfaces**: `--bg`, `--surface-2` through `--surface-7`, `--surface-hover`, `--surface-active`
-**Borders**: `--border`, `--border-1`, `--border-muted`
-**Z-Index**: `--z-dropdown` (100), `--z-modal` (200), `--z-popover` (300), `--z-tooltip` (400), `--z-toast` (500)
-**Shadows**: `shadow-subtle`, `shadow-medium`, `shadow-overlay`, `shadow-card`
-
-## Buttons
-
-| Action | Variant |
-|--------|---------|
-| Toolbar, icon-only | `ghost` (most common, 28%) |
-| Create, save, submit | `primary` (24%) |
-| Cancel, close | `default` |
-| Delete, remove | `destructive` |
-| Selected state | `active` |
-| Toggle | `outline` |
-
-## Delete/Remove Confirmations
-
-Modal `size="sm"`, title "Delete/Remove {ItemType}", `variant="destructive"` action button, `variant="default"` cancel. Cancel left, action right (100% compliance). Use `text-[var(--text-error)]` for irreversible warnings.
-
-## Toast
-
-`toast.success()`, `toast.error()`, `toast()` from `@/components/emcn`. Never custom notification UI.
-
-## Badges
-
-`red`=error/failed, `gray-secondary`=metadata/roles, `type`=type annotations, `green`=success/active, `gray`=neutral, `amber`=processing, `orange`=paused, `blue`=info. Use `dot` prop for status indicators.
-
-## Icons
-
-Default: `h-[14px] w-[14px]` (400+ uses). Color: `text-[var(--text-icon)]`. Scale: 14px > 16px > 12px > 20px.
-
-## Anti-patterns to flag
-
-- Raw `<button>`/`<input>` instead of emcn components
-- Hardcoded colors (`text-gray-*`, `#hex`, `rgb()`)
-- Tailwind semantics (`text-muted-foreground`) instead of CSS variables
-- Template literal className instead of `cn()`
-- Inline styles for colors/static values (dynamic values OK)
-- Importing from emcn subpaths instead of barrel
-- Arbitrary z-index instead of tokens
-- Wrong button variant for action type

.cursor/commands/react-query-best-practices.md

@@ -1,49 +0,0 @@
-# React Query Best Practices
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/hooks/queries/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query (TanStack Query) as the single source of truth for all server state. All query hooks live in `hooks/queries/`. Zustand is used only for client-only UI state. Server data must never be duplicated into useState or Zustand outside of mutation callbacks that coordinate cross-store state.
-
-## References
-
-Read these before analyzing:
-1. https://tkdodo.eu/blog/practical-react-query — foundational defaults, custom hooks, avoiding local state copies
-2. https://tkdodo.eu/blog/effective-react-query-keys — key factory pattern, hierarchical keys, fuzzy invalidation
-3. https://tkdodo.eu/blog/react-query-as-a-state-manager — React Query IS your server state manager
-
-## Rules to enforce
-
-### Query key factories
-- Every file in `hooks/queries/` must have a hierarchical key factory with an `all` root key
-- Keys must include intermediate plural keys (`lists`, `details`) for prefix invalidation
-- Key factories are colocated with their query hooks, not in a global keys file
-
-### Query hooks
-- Every `queryFn` must forward `signal` for request cancellation
-- Every query must have an explicit `staleTime` (default 0 is almost never correct)
-- `keepPreviousData` / `placeholderData` only on variable-key queries (where params change), never on static keys
-- Use `enabled` to prevent queries from running without required params
-
-### Mutations
-- Use `onSettled` (not `onSuccess`) for cache reconciliation — it fires on both success and error
-- For optimistic updates: save previous data in `onMutate`, roll back in `onError`
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- Don't include mutation objects in `useCallback` deps — `.mutate()` is stable
-
-### Server state ownership
-- Never copy query data into useState. Use query data directly in components.
-- Never copy query data into Zustand stores (exception: mutation callbacks that coordinate cross-store state like temp ID replacement)
-- The query cache is not a local state manager — `setQueryData` is for optimistic updates only
-- Forms are the one deliberate exception: copy server data into local form state with `staleTime: Infinity`
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope against the rules listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.cursor/commands/validate-connector.md

@@ -1,311 +0,0 @@
-# Validate Connector Skill
-
-You are an expert auditor for Sim knowledge base connectors. Your job is to thoroughly validate that an existing connector is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate a connector:
-1. Read the service's API documentation (via Context7 or WebFetch)
-2. Read the connector implementation, OAuth config, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the connector — do not skip any:
-
-```
-apps/sim/connectors/{service}/{service}.ts   # Connector implementation
-apps/sim/connectors/{service}/index.ts       # Barrel export
-apps/sim/connectors/registry.ts              # Connector registry entry
-apps/sim/connectors/types.ts                 # ConnectorConfig interface, ExternalDocument, etc.
-apps/sim/connectors/utils.ts                 # Shared utilities (computeContentHash, htmlToPlainText, etc.)
-apps/sim/lib/oauth/oauth.ts                  # OAUTH_PROVIDERS — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts                  # getCanonicalScopesForProvider, getScopesForService, SCOPE_DESCRIPTIONS
-apps/sim/lib/oauth/types.ts                  # OAuthService union type
-apps/sim/components/icons.tsx                 # Icon definition for the service
-```
-
-If the connector uses selectors, also read:
-```
-apps/sim/hooks/selectors/registry.ts         # Selector key definitions
-apps/sim/hooks/selectors/types.ts            # SelectorKey union type
-apps/sim/lib/workflows/subblocks/context.ts  # SELECTOR_CONTEXT_FIELDS
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (cursor, offset, next token)
-- Rate limits and error formats
-- OAuth scopes and their meanings
-
-Use Context7 (resolve-library-id → query-docs) or WebFetch to retrieve documentation. If both fail, note which claims are based on training knowledge vs verified docs.
-
-## Step 3: Validate API Endpoints
-
-For **every** API call in the connector (`listDocuments`, `getDocument`, `validateConfig`, and any helper functions), verify against the API docs:
-
-### URLs and Methods
-- [ ] Base URL is correct for the service's API version
-- [ ] Endpoint paths match the API docs exactly
-- [ ] HTTP method is correct (GET, POST, PUT, PATCH, DELETE)
-- [ ] Path parameters are correctly interpolated and URI-encoded where needed
-- [ ] Query parameters use correct names and formats per the API docs
-
-### Headers
-- [ ] Authorization header uses the correct format:
-  - OAuth: `Authorization: Bearer ${accessToken}`
-  - API Key: correct header name per the service's docs
-- [ ] `Content-Type` is set for POST/PUT/PATCH requests
-- [ ] Any service-specific headers are present (e.g., `Notion-Version`, `Dropbox-API-Arg`)
-- [ ] No headers are sent that the API doesn't support or silently ignores
-
-### Request Bodies
-- [ ] POST/PUT body fields match API parameter names exactly
-- [ ] Required fields are always sent
-- [ ] Optional fields are conditionally included (not sent as `null` or empty unless the API expects that)
-- [ ] Field value types match API expectations (string vs number vs boolean)
-
-### Input Sanitization
-- [ ] User-controlled values interpolated into query strings are properly escaped:
-  - OData `$filter`: single quotes escaped with `''` (e.g., `externalId.replace(/'/g, "''")`)
-  - SOQL: single quotes escaped with `\'`
-  - GraphQL variables: passed as variables, not interpolated into query strings
-  - URL path segments: `encodeURIComponent()` applied
-- [ ] URL-type config fields (e.g., `siteUrl`, `instanceUrl`) are normalized:
-  - Strip `https://` / `http://` prefix if the API expects bare domains
-  - Strip trailing `/`
-  - Apply `.trim()` before validation
-
-### Response Parsing
-- [ ] Response structure is correctly traversed (e.g., `data.results` vs `data.items` vs `data`)
-- [ ] Field names extracted match what the API actually returns
-- [ ] Nullable fields are handled with `?? null` or `|| undefined`
-- [ ] Error responses are checked before accessing data fields
-
-## Step 4: Validate OAuth Scopes (if OAuth connector)
-
-Scopes must be correctly declared and sufficient for all API calls the connector makes.
-
-### Connector requiredScopes
-- [ ] `requiredScopes` in the connector's `auth` config lists all scopes needed by the connector
-- [ ] Each scope in `requiredScopes` is a real, valid scope recognized by the service's API
-- [ ] No invalid, deprecated, or made-up scopes are listed
-- [ ] No unnecessary excess scopes beyond what the connector actually needs
-
-### Scope Subset Validation (CRITICAL)
-- [ ] Every scope in `requiredScopes` exists in the OAuth provider's `scopes` array in `lib/oauth/oauth.ts`
-- [ ] Find the provider in `OAUTH_PROVIDERS[providerGroup].services[serviceId].scopes`
-- [ ] Verify: `requiredScopes` ⊆ `OAUTH_PROVIDERS scopes` (every required scope is present in the provider config)
-- [ ] If a required scope is NOT in the provider config, flag as **critical** — the connector will fail at runtime
-
-### Scope Sufficiency
-For each API endpoint the connector calls:
-- [ ] Identify which scopes are required per the API docs
-- [ ] Verify those scopes are included in the connector's `requiredScopes`
-- [ ] If the connector calls endpoints requiring scopes not in `requiredScopes`, flag as **warning**
-
-### Token Refresh Config
-- [ ] Check the `getOAuthTokenRefreshConfig` function in `lib/oauth/oauth.ts` for this provider
-- [ ] `useBasicAuth` matches the service's token exchange requirements
-- [ ] `supportsRefreshTokenRotation` matches whether the service issues rotating refresh tokens
-- [ ] Token endpoint URL is correct
-
-## Step 5: Validate Pagination
-
-### listDocuments Pagination
-- [ ] Cursor/pagination parameter name matches the API docs
-- [ ] Response pagination field is correctly extracted (e.g., `next_cursor`, `nextPageToken`, `@odata.nextLink`, `offset`)
-- [ ] `hasMore` is correctly determined from the response
-- [ ] `nextCursor` is correctly passed back for the next page
-- [ ] `maxItems` / `maxRecords` cap is correctly applied across pages using `syncContext.totalDocsFetched`
-- [ ] Page size is within the API's allowed range (not exceeding max page size)
-- [ ] Last page precision: when a `maxItems` cap exists, the final page request uses `Math.min(PAGE_SIZE, remaining)` to avoid fetching more records than needed
-- [ ] No off-by-one errors in pagination tracking
-- [ ] The connector does NOT hit known API pagination limits silently (e.g., HubSpot search 10k cap)
-
-### Pagination State Across Pages
-- [ ] `syncContext` is used to cache state across pages (user names, field maps, instance URLs, portal IDs, etc.)
-- [ ] Cached state in `syncContext` is correctly initialized on first page and reused on subsequent pages
-
-## Step 6: Validate Data Transformation
-
-### ExternalDocument Construction
-- [ ] `externalId` is a stable, unique identifier from the source API
-- [ ] `title` is extracted from the correct field and has a sensible fallback (e.g., `'Untitled'`)
-- [ ] `content` is plain text — HTML content is stripped using `htmlToPlainText` from `@/connectors/utils`
-- [ ] `mimeType` is `'text/plain'`
-- [ ] `contentHash` is computed using `computeContentHash` from `@/connectors/utils`
-- [ ] `sourceUrl` is a valid, complete URL back to the original resource (not relative)
-- [ ] `metadata` contains all fields referenced by `mapTags` and `tagDefinitions`
-
-### Content Extraction
-- [ ] Rich text / HTML fields are converted to plain text before indexing
-- [ ] Important content is not silently dropped (e.g., nested blocks, table cells, code blocks)
-- [ ] Content is not silently truncated without logging a warning
-- [ ] Empty/blank documents are properly filtered out
-- [ ] Size checks use `Buffer.byteLength(text, 'utf8')` not `text.length` when comparing against byte-based limits (e.g., `MAX_FILE_SIZE` in bytes)
-
-## Step 7: Validate Tag Definitions and mapTags
-
-### tagDefinitions
-- [ ] Each `tagDefinition` has an `id`, `displayName`, and `fieldType`
-- [ ] `fieldType` matches the actual data type: `'text'` for strings, `'number'` for numbers, `'date'` for dates, `'boolean'` for booleans
-- [ ] Every `id` in `tagDefinitions` is returned by `mapTags`
-- [ ] No `tagDefinition` references a field that `mapTags` never produces
-
-### mapTags
-- [ ] Return keys match `tagDefinition` `id` values exactly
-- [ ] Date values are properly parsed using `parseTagDate` from `@/connectors/utils`
-- [ ] Array values are properly joined using `joinTagArray` from `@/connectors/utils`
-- [ ] Number values are validated (not `NaN`)
-- [ ] Metadata field names accessed in `mapTags` match what `listDocuments`/`getDocument` store in `metadata`
-
-## Step 8: Validate Config Fields and Validation
-
-### configFields
-- [ ] Every field has `id`, `title`, `type`
-- [ ] `required` is set explicitly (not omitted)
-- [ ] Dropdown fields have `options` with `label` and `id` for each option
-- [ ] Selector fields follow the canonical pair pattern:
-  - A `type: 'selector'` field with `selectorKey`, `canonicalParamId`, `mode: 'basic'`
-  - A `type: 'short-input'` field with the same `canonicalParamId`, `mode: 'advanced'`
-  - `required` is identical on both fields in the pair
-- [ ] `selectorKey` values exist in the selector registry
-- [ ] `dependsOn` references selector field `id` values, not `canonicalParamId`
-
-### validateConfig
-- [ ] Validates all required fields are present before making API calls
-- [ ] Validates optional numeric fields (checks `Number.isNaN`, positive values)
-- [ ] Makes a lightweight API call to verify access (e.g., fetch 1 record, get profile)
-- [ ] Uses `VALIDATE_RETRY_OPTIONS` for retry budget
-- [ ] Returns `{ valid: true }` on success
-- [ ] Returns `{ valid: false, error: 'descriptive message' }` on failure
-- [ ] Catches exceptions and returns user-friendly error messages
-- [ ] Does NOT make expensive calls (full data listing, large queries)
-
-## Step 9: Validate getDocument
-
-- [ ] Fetches a single document by `externalId`
-- [ ] Returns `null` for 404 / not found (does not throw)
-- [ ] Returns the same `ExternalDocument` shape as `listDocuments`
-- [ ] Handles all content types that `listDocuments` can produce (e.g., if `listDocuments` returns both pages and blogposts, `getDocument` must handle both — not hardcode one endpoint)
-- [ ] Forwards `syncContext` if it needs cached state (user names, field maps, etc.)
-- [ ] Error handling is graceful (catches, logs, returns null or throws with context)
-- [ ] Does not redundantly re-fetch data already included in the initial API response (e.g., if comments come back with the post, don't fetch them again separately)
-
-## Step 10: Validate General Quality
-
-### fetchWithRetry Usage
-- [ ] All external API calls use `fetchWithRetry` from `@/lib/knowledge/documents/utils`
-- [ ] No raw `fetch()` calls to external APIs
-- [ ] `VALIDATE_RETRY_OPTIONS` used in `validateConfig`
-- [ ] If `validateConfig` calls a shared helper (e.g., `linearGraphQL`, `resolveId`), that helper must accept and forward `retryOptions` to `fetchWithRetry`
-- [ ] Default retry options used in `listDocuments`/`getDocument`
-
-### API Efficiency
-- [ ] APIs that support field selection (e.g., `$select`, `sysparm_fields`, `fields`) should request only the fields the connector needs — in both `listDocuments` AND `getDocument`
-- [ ] No redundant API calls: if a helper already fetches data (e.g., site metadata), callers should reuse the result instead of making a second call for the same information
-- [ ] Sequential per-item API calls (fetching details for each document in a loop) should be batched with `Promise.all` and a concurrency limit of 3-5
-
-### Error Handling
-- [ ] Individual document failures are caught and logged without aborting the sync
-- [ ] API error responses include status codes in error messages
-- [ ] No unhandled promise rejections in concurrent operations
-
-### Concurrency
-- [ ] Concurrent API calls use reasonable batch sizes (3-5 is typical)
-- [ ] No unbounded `Promise.all` over large arrays
-
-### Logging
-- [ ] Uses `createLogger` from `@sim/logger` (not `console.log`)
-- [ ] Logs sync progress at `info` level
-- [ ] Logs errors at `warn` or `error` level with context
-
-### Registry
-- [ ] Connector is exported from `connectors/{service}/index.ts`
-- [ ] Connector is registered in `connectors/registry.ts`
-- [ ] Registry key matches the connector's `id` field
-
-## Step 11: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors, data loss, or auth failures):
-- Wrong API endpoint URL or HTTP method
-- Invalid or missing OAuth scopes (not in provider config)
-- Incorrect response field mapping (accessing wrong path)
-- SOQL/query fields that don't exist on the target object
-- Pagination that silently hits undocumented API limits
-- Missing error handling that would crash the sync
-- `requiredScopes` not a subset of OAuth provider scopes
-- Query/filter injection: user-controlled values interpolated into OData `$filter`, SOQL, or query strings without escaping
-
-**Warning** (incorrect behavior, data quality issues, or convention violations):
-- HTML content not stripped via `htmlToPlainText`
-- `getDocument` not forwarding `syncContext`
-- `getDocument` hardcoded to one content type when `listDocuments` returns multiple (e.g., only pages but not blogposts)
-- Missing `tagDefinition` for metadata fields returned by `mapTags`
-- Incorrect `useBasicAuth` or `supportsRefreshTokenRotation` in token refresh config
-- Invalid scope names that the API doesn't recognize (even if silently ignored)
-- Private resources excluded from name-based lookup despite scopes being available
-- Silent data truncation without logging
-- Size checks using `text.length` (character count) instead of `Buffer.byteLength` (byte count) for byte-based limits
-- URL-type config fields not normalized (protocol prefix, trailing slashes cause API failures)
-- `VALIDATE_RETRY_OPTIONS` not threaded through helper functions called by `validateConfig`
-
-**Suggestion** (minor improvements):
-- Missing incremental sync support despite API supporting it
-- Overly broad scopes that could be narrowed (not wrong, but could be tighter)
-- Source URL format could be more specific
-- Missing `orderBy` for deterministic pagination
-- Redundant API calls that could be cached in `syncContext`
-- Sequential per-item API calls that could be batched with `Promise.all` (concurrency 3-5)
-- API supports field selection but connector fetches all fields (e.g., missing `$select`, `sysparm_fields`, `fields`)
-- `getDocument` re-fetches data already included in the initial API response (e.g., comments returned with post)
-- Last page of pagination requests full `PAGE_SIZE` when fewer records remain (`Math.min(PAGE_SIZE, remaining)`)
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes
-2. TypeScript compiles clean
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read connector implementation, types, utils, registry, and OAuth config
-- [ ] Pulled and read official API documentation for the service
-- [ ] Validated every API endpoint URL, method, headers, and body against API docs
-- [ ] Validated input sanitization: no query/filter injection, URL fields normalized
-- [ ] Validated OAuth scopes: `requiredScopes` ⊆ OAuth provider `scopes` in `oauth.ts`
-- [ ] Validated each scope is real and recognized by the service's API
-- [ ] Validated scopes are sufficient for all API endpoints the connector calls
-- [ ] Validated token refresh config (`useBasicAuth`, `supportsRefreshTokenRotation`)
-- [ ] Validated pagination: cursor names, page sizes, hasMore logic, no silent caps
-- [ ] Validated data transformation: plain text extraction, HTML stripping, content hashing
-- [ ] Validated tag definitions match mapTags output, correct fieldTypes
-- [ ] Validated config fields: canonical pairs, selector keys, required flags
-- [ ] Validated validateConfig: lightweight check, error messages, retry options
-- [ ] Validated getDocument: null on 404, all content types handled, no redundant re-fetches, syncContext forwarding
-- [ ] Validated fetchWithRetry used for all external calls (no raw fetch), VALIDATE_RETRY_OPTIONS threaded through helpers
-- [ ] Validated API efficiency: field selection used, no redundant calls, sequential fetches batched
-- [ ] Validated error handling: graceful failures, no unhandled rejections
-- [ ] Validated logging: createLogger, no console.log
-- [ ] Validated registry: correct export, correct key
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.cursor/commands/validate-integration.md

@@ -1,284 +0,0 @@
-# Validate Integration Skill
-
-You are an expert auditor for Sim integrations. Your job is to thoroughly validate that an existing integration is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate an integration:
-1. Read the service's API documentation (via WebFetch or Context7)
-2. Read every tool, the block, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the integration — do not skip any:
-
-```
-apps/sim/tools/{service}/          # All tool files, types.ts, index.ts
-apps/sim/blocks/blocks/{service}.ts # Block definition
-apps/sim/tools/registry.ts          # Tool registry entries for this service
-apps/sim/blocks/registry.ts         # Block registry entry for this service
-apps/sim/components/icons.tsx        # Icon definition
-apps/sim/lib/auth/auth.ts           # OAuth config — should use getCanonicalScopesForProvider()
-apps/sim/lib/oauth/oauth.ts         # OAuth provider config — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts               # Scope utilities, SCOPE_DESCRIPTIONS for modal UI
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (which param name, which response field)
-- Rate limits and error formats
-
-## Step 3: Validate Tools
-
-For **every** tool file, check:
-
-### Tool ID and Naming
-- [ ] Tool ID uses `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`)
-- [ ] Tool `name` is human-readable (e.g., `'X Create Tweet'`)
-- [ ] Tool `description` is a concise one-liner describing what it does
-- [ ] Tool `version` is set (`'1.0.0'` or `'2.0.0'` for V2)
-
-### Params
-- [ ] All required API params are marked `required: true`
-- [ ] All optional API params are marked `required: false`
-- [ ] Every param has explicit `required: true` or `required: false` — never omitted
-- [ ] Param types match the API (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] Visibility is correct:
-  - `'hidden'` — ONLY for OAuth access tokens and system-injected params
-  - `'user-only'` — for API keys, credentials, and account-specific IDs the user must provide
-  - `'user-or-llm'` — for everything else (search queries, content, filters, IDs that could come from other blocks)
-- [ ] Every param has a `description` that explains what it does
-
-### Request
-- [ ] URL matches the API endpoint exactly (correct base URL, path segments, path params)
-- [ ] HTTP method matches the API spec (GET, POST, PUT, PATCH, DELETE)
-- [ ] Headers include correct auth pattern:
-  - OAuth: `Authorization: Bearer ${params.accessToken}`
-  - API Key: correct header name and format per the service's docs
-- [ ] `Content-Type` header is set for POST/PUT/PATCH requests
-- [ ] Body sends all required fields and only includes optional fields when provided
-- [ ] For GET requests with query params: URL is constructed correctly with query string
-- [ ] ID fields in URL paths are `.trim()`-ed to prevent copy-paste whitespace errors
-- [ ] Path params use template literals correctly: `` `https://api.service.com/v1/${params.id.trim()}` ``
-
-### Response / transformResponse
-- [ ] Correctly parses the API response (`await response.json()`)
-- [ ] Extracts the right fields from the response structure (e.g., `data.data` vs `data` vs `data.results`)
-- [ ] All nullable fields use `?? null`
-- [ ] All optional arrays use `?? []`
-- [ ] Error cases are handled: checks for missing/empty data and returns meaningful error
-- [ ] Does NOT do raw JSON dumps — extracts meaningful, individual fields
-
-### Outputs
-- [ ] All output fields match what the API actually returns
-- [ ] No fields are missing that the API provides and users would commonly need
-- [ ] No phantom fields defined that the API doesn't return
-- [ ] `optional: true` is set on fields that may not exist in all responses
-- [ ] When using `type: 'json'` and the shape is known, `properties` defines the inner fields
-- [ ] When using `type: 'array'`, `items` defines the item structure with `properties`
-- [ ] Field descriptions are accurate and helpful
-
-### Types (types.ts)
-- [ ] Has param interfaces for every tool (e.g., `XCreateTweetParams`)
-- [ ] Has response interfaces for every tool (extending `ToolResponse`)
-- [ ] Optional params use `?` in the interface (e.g., `replyTo?: string`)
-- [ ] Field names in types match actual API field names
-- [ ] Shared response types are properly reused (e.g., `XTweetResponse` shared across tweet tools)
-
-### Barrel Export (index.ts)
-- [ ] Every tool is exported
-- [ ] All types are re-exported (`export * from './types'`)
-- [ ] No orphaned exports (tools that don't exist)
-
-### Tool Registry (tools/registry.ts)
-- [ ] Every tool is imported and registered
-- [ ] Registry keys use snake_case and match tool IDs exactly
-- [ ] Entries are in alphabetical order within the file
-
-## Step 4: Validate Block
-
-### Block ↔ Tool Alignment (CRITICAL)
-
-This is the most important validation — the block must be perfectly aligned with every tool it references.
-
-For **each tool** in `tools.access`:
-- [ ] The operation dropdown has an option whose ID matches the tool ID (or the `tools.config.tool` function correctly maps to it)
-- [ ] Every **required** tool param (except `accessToken`) has a corresponding subBlock input that is:
-  - Shown when that operation is selected (correct `condition`)
-  - Marked as `required: true` (or conditionally required)
-- [ ] Every **optional** tool param has a corresponding subBlock input (or is intentionally omitted if truly never needed)
-- [ ] SubBlock `id` values are unique across the entire block — no duplicates even across different conditions
-- [ ] The `tools.config.tool` function returns the correct tool ID for every possible operation value
-- [ ] The `tools.config.params` function correctly maps subBlock IDs to tool param names when they differ
-
-### SubBlocks
-- [ ] Operation dropdown lists ALL tool operations available in `tools.access`
-- [ ] Dropdown option labels are human-readable and descriptive
-- [ ] Conditions use correct syntax:
-  - Single value: `{ field: 'operation', value: 'x_create_tweet' }`
-  - Multiple values (OR): `{ field: 'operation', value: ['x_create_tweet', 'x_delete_tweet'] }`
-  - Negation: `{ field: 'operation', value: 'delete', not: true }`
-  - Compound: `{ field: 'op', value: 'send', and: { field: 'type', value: 'dm' } }`
-- [ ] Condition arrays include ALL operations that use that field — none missing
-- [ ] `dependsOn` is set for fields that need other values (selectors depending on credential, cascading dropdowns)
-- [ ] SubBlock types match tool param types:
-  - Enum/fixed options → `dropdown`
-  - Free text → `short-input`
-  - Long text/content → `long-input`
-  - True/false → `dropdown` with Yes/No options (not `switch` unless purely UI toggle)
-  - Credentials → `oauth-input` with correct `serviceId`
-- [ ] Dropdown `value: () => 'default'` is set for dropdowns with a sensible default
-
-### Advanced Mode
-- [ ] Optional, rarely-used fields are set to `mode: 'advanced'`:
-  - Pagination tokens / next tokens
-  - Time range filters (start/end time)
-  - Sort order / direction options
-  - Max results / per page limits
-  - Reply settings / threading options
-  - Rarely used IDs (reply-to, quote-tweet, etc.)
-  - Exclude filters
-- [ ] **Required** fields are NEVER set to `mode: 'advanced'`
-- [ ] Fields that users fill in most of the time are NOT set to `mode: 'advanced'`
-
-### WandConfig
-- [ ] Timestamp fields have `wandConfig` with `generationType: 'timestamp'`
-- [ ] Comma-separated list fields have `wandConfig` with a descriptive prompt
-- [ ] Complex filter/query fields have `wandConfig` with format examples in the prompt
-- [ ] All `wandConfig` prompts end with "Return ONLY the [format] - no explanations, no extra text."
-- [ ] `wandConfig.placeholder` describes what to type in natural language
-
-### Tools Config
-- [ ] `tools.access` lists **every** tool ID the block can use — none missing
-- [ ] `tools.config.tool` returns the correct tool ID for each operation
-- [ ] Type coercions are in `tools.config.params` (runs at execution time), NOT in `tools.config.tool` (runs at serialization time before variable resolution)
-- [ ] `tools.config.params` handles:
-  - `Number()` conversion for numeric params that come as strings from inputs
-  - `Boolean` / string-to-boolean conversion for toggle params
-  - Empty string → `undefined` conversion for optional dropdown values
-  - Any subBlock ID → tool param name remapping
-- [ ] No `Number()`, `JSON.parse()`, or other coercions in `tools.config.tool` — these would destroy dynamic references like `<Block.output>`
-
-### Block Outputs
-- [ ] Outputs cover the key fields returned by ALL tools (not just one operation)
-- [ ] Output types are correct (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] `type: 'json'` outputs either:
-  - Describe inner fields in the description string (GOOD): `'User profile (id, name, username, bio)'`
-  - Use nested output definitions (BEST): `{ id: { type: 'string' }, name: { type: 'string' } }`
-- [ ] No opaque `type: 'json'` with vague descriptions like `'Response data'`
-- [ ] Outputs that only appear for certain operations use `condition` if supported, or document which operations return them
-
-### Block Metadata
-- [ ] `type` is snake_case (e.g., `'x'`, `'cloudflare'`)
-- [ ] `name` is human-readable (e.g., `'X'`, `'Cloudflare'`)
-- [ ] `description` is a concise one-liner
-- [ ] `longDescription` provides detail for docs
-- [ ] `docsLink` points to `'https://docs.sim.ai/tools/{service}'`
-- [ ] `category` is `'tools'`
-- [ ] `bgColor` uses the service's brand color hex
-- [ ] `icon` references the correct icon component from `@/components/icons`
-- [ ] `authMode` is set correctly (`AuthMode.OAuth` or `AuthMode.ApiKey`)
-- [ ] Block is registered in `blocks/registry.ts` alphabetically
-
-### Block Inputs
-- [ ] `inputs` section lists all subBlock params that the block accepts
-- [ ] Input types match the subBlock types
-- [ ] When using `canonicalParamId`, inputs list the canonical ID (not the raw subBlock IDs)
-
-## Step 5: Validate OAuth Scopes (if OAuth service)
-
-Scopes are centralized — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-- [ ] Scopes defined in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-- [ ] `auth.ts` uses `getCanonicalScopesForProvider(providerId)` — NOT a hardcoded array
-- [ ] Block `requiredScopes` uses `getScopesForService(serviceId)` — NOT a hardcoded array
-- [ ] No hardcoded scope arrays in `auth.ts` or block files (should all use utility functions)
-- [ ] Each scope has a human-readable description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] No excess scopes that aren't needed by any tool
-
-## Step 6: Validate Pagination Consistency
-
-If any tools support pagination:
-- [ ] Pagination param names match the API docs (e.g., `pagination_token` vs `next_token` vs `cursor`)
-- [ ] Different API endpoints that use different pagination param names have separate subBlocks in the block
-- [ ] Pagination response fields (`nextToken`, `cursor`, etc.) are included in tool outputs
-- [ ] Pagination subBlocks are set to `mode: 'advanced'`
-
-## Step 7: Validate Error Handling
-
-- [ ] `transformResponse` checks for error conditions before accessing data
-- [ ] Error responses include meaningful messages (not just generic "failed")
-- [ ] HTTP error status codes are handled (check `response.ok` or status codes)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors or incorrect behavior):
-- Wrong endpoint URL or HTTP method
-- Missing required params or wrong `required` flag
-- Incorrect response field mapping (accessing wrong path in response)
-- Missing error handling that would cause crashes
-- Tool ID mismatch between tool file, registry, and block `tools.access`
-- OAuth scopes missing in `auth.ts` that tools need
-- `tools.config.tool` returning wrong tool ID for an operation
-- Type coercions in `tools.config.tool` instead of `tools.config.params`
-
-**Warning** (follows conventions incorrectly or has usability issues):
-- Optional field not set to `mode: 'advanced'`
-- Missing `wandConfig` on timestamp/complex fields
-- Wrong `visibility` on params (e.g., `'hidden'` instead of `'user-or-llm'`)
-- Missing `optional: true` on nullable outputs
-- Opaque `type: 'json'` without property descriptions
-- Missing `.trim()` on ID fields in request URLs
-- Missing `?? null` on nullable response fields
-- Block condition array missing an operation that uses that field
-- Hardcoded scope arrays instead of using `getScopesForService()` / `getCanonicalScopesForProvider()`
-- Missing scope description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-
-**Suggestion** (minor improvements):
-- Better description text
-- Inconsistent naming across tools
-- Missing `longDescription` or `docsLink`
-- Pagination fields that could benefit from `wandConfig`
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes with no fixes needed
-2. TypeScript compiles clean (no type errors)
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read ALL tool files, block, types, index, and registries
-- [ ] Pulled and read official API documentation
-- [ ] Validated every tool's ID, params, request, response, outputs, and types against API docs
-- [ ] Validated block ↔ tool alignment (every tool param has a subBlock, every condition is correct)
-- [ ] Validated advanced mode on optional/rarely-used fields
-- [ ] Validated wandConfig on timestamps and complex inputs
-- [ ] Validated tools.config mapping, tool selector, and type coercions
-- [ ] Validated block outputs match what tools return, with typed JSON where possible
-- [ ] Validated OAuth scopes use centralized utilities (getScopesForService, getCanonicalScopesForProvider) — no hardcoded arrays
-- [ ] Validated scope descriptions exist in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for all scopes
-- [ ] Validated pagination consistency across tools and block
-- [ ] Validated error handling (error checks, meaningful messages)
-- [ ] Validated registry entries (tools and block, alphabetical, correct imports)
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.cursor/commands/validate-trigger.md

@@ -1,207 +0,0 @@
-# Validate Trigger
-
-You are an expert auditor for Sim webhook triggers. Your job is to validate that an existing trigger implementation is correct, complete, secure, and aligned across all layers.
-
-## Your Task
-
-1. Read the service's webhook/API documentation (via WebFetch)
-2. Read every trigger file, provider handler, and registry entry
-3. Cross-reference against the API docs and Sim conventions
-4. Report all issues grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the trigger — do not skip any:
-
-```
-apps/sim/triggers/{service}/           # All trigger files, utils.ts, index.ts
-apps/sim/lib/webhooks/providers/{service}.ts  # Provider handler (if exists)
-apps/sim/lib/webhooks/providers/registry.ts   # Handler registry
-apps/sim/triggers/registry.ts                 # Trigger registry
-apps/sim/blocks/blocks/{service}.ts           # Block definition (trigger wiring)
-```
-
-Also read for reference:
-```
-apps/sim/lib/webhooks/providers/types.ts            # WebhookProviderHandler interface
-apps/sim/lib/webhooks/providers/utils.ts            # Shared helpers (createHmacVerifier, etc.)
-apps/sim/lib/webhooks/provider-subscription-utils.ts    # Subscription helpers
-apps/sim/lib/webhooks/processor.ts                  # Central webhook processor
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the service's official webhook documentation. This is the **source of truth** for:
-- Webhook event types and payload shapes
-- Signature/auth verification method (HMAC algorithm, header names, secret format)
-- Challenge/verification handshake requirements
-- Webhook subscription API (create/delete endpoints, if applicable)
-- Retry behavior and delivery guarantees
-
-## Step 3: Validate Trigger Definitions
-
-### utils.ts
-- [ ] `{service}TriggerOptions` lists all trigger IDs accurately
-- [ ] `{service}SetupInstructions` provides clear, correct steps for the service
-- [ ] `build{Service}ExtraFields` includes relevant filter/config fields with correct `condition`
-- [ ] Output builders expose all meaningful fields from the webhook payload
-- [ ] Output builders do NOT use `optional: true` or `items` (tool-output-only features)
-- [ ] Nested output objects correctly model the payload structure
-
-### Trigger Files
-- [ ] Exactly one primary trigger has `includeDropdown: true`
-- [ ] All secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper (not hand-rolled subBlocks)
-- [ ] Every trigger's `id` matches the convention `{service}_{event_name}`
-- [ ] Every trigger's `provider` matches the service name used in the handler registry
-- [ ] `index.ts` barrel exports all triggers
-
-### Trigger ↔ Provider Alignment (CRITICAL)
-- [ ] Every trigger ID referenced in `matchEvent` logic exists in `{service}TriggerOptions`
-- [ ] Event matching logic in the provider correctly maps trigger IDs to service event types
-- [ ] Event matching logic in `is{Service}EventMatch` (if exists) correctly identifies events per the API docs
-
-## Step 4: Validate Provider Handler
-
-### Auth Verification
-- [ ] `verifyAuth` correctly validates webhook signatures per the service's documentation
-- [ ] HMAC algorithm matches (SHA-1, SHA-256, SHA-512)
-- [ ] Signature header name matches the API docs exactly
-- [ ] Signature format is handled (raw hex, `sha256=` prefix, base64, etc.)
-- [ ] Uses `safeCompare` for timing-safe comparison (no `===`)
-- [ ] If `webhookSecret` is required, handler rejects when it's missing (fail-closed)
-- [ ] Signature is computed over raw body (not parsed JSON)
-
-### Event Matching
-- [ ] `matchEvent` returns `boolean` (not `NextResponse` or other values)
-- [ ] Challenge/verification events are excluded from matching (e.g., `endpoint.url_validation`)
-- [ ] When `triggerId` is a generic webhook ID, all events pass through
-- [ ] When `triggerId` is specific, only matching events pass
-- [ ] Event matching logic uses dynamic `await import()` for trigger utils (avoids circular deps)
-
-### formatInput (CRITICAL)
-- [ ] Every key in the `formatInput` return matches a key in the trigger `outputs` schema
-- [ ] Every key in the trigger `outputs` schema is populated by `formatInput`
-- [ ] No extra undeclared keys that users can't discover in the UI
-- [ ] No wrapper objects (`webhook: { ... }`, `{service}: { ... }`)
-- [ ] Nested output paths exist at the correct depth (e.g., `resource.id` actually has `resource: { id: ... }`)
-- [ ] `null` is used for missing optional fields (not empty strings or empty objects)
-- [ ] Returns `{ input: { ... } }` — not a bare object
-
-### Idempotency
-- [ ] `extractIdempotencyId` returns a stable, unique key per delivery
-- [ ] Uses provider-specific delivery IDs when available (e.g., `X-Request-Id`, `Linear-Delivery`, `svix-id`)
-- [ ] Falls back to content-based ID (e.g., `${type}:${id}`) when no delivery header exists
-- [ ] Does NOT include timestamps in the idempotency key (would break dedup on retries)
-
-### Challenge Handling (if applicable)
-- [ ] `handleChallenge` correctly implements the service's URL verification handshake
-- [ ] Returns the expected response format per the API docs
-- [ ] Env-backed secrets are resolved via `resolveEnvVarsInObject` if needed
-
-## Step 5: Validate Automatic Subscription Lifecycle
-
-If the service supports programmatic webhook creation:
-
-### createSubscription
-- [ ] Calls the correct API endpoint to create a webhook
-- [ ] Sends the correct event types/filters
-- [ ] Passes the notification URL from `getNotificationUrl(ctx.webhook)`
-- [ ] Returns `{ providerConfigUpdates: { externalId } }` with the external webhook ID
-- [ ] Throws on failure (orchestration handles rollback)
-- [ ] Provides user-friendly error messages (401 → "Invalid API Key", etc.)
-
-### deleteSubscription
-- [ ] Calls the correct API endpoint to delete the webhook
-- [ ] Handles 404 gracefully (webhook already deleted)
-- [ ] Never throws — catches errors and logs non-fatally
-- [ ] Skips gracefully when `apiKey` or `externalId` is missing
-
-### Orchestration Isolation
-- [ ] NO provider-specific logic in `route.ts`, `provider-subscriptions.ts`, or `deploy.ts`
-- [ ] All subscription logic lives on the handler (`createSubscription`/`deleteSubscription`)
-
-## Step 6: Validate Registration and Block Wiring
-
-### Trigger Registry (`triggers/registry.ts`)
-- [ ] All triggers are imported and registered
-- [ ] Registry keys match trigger IDs exactly
-- [ ] No orphaned entries (triggers that don't exist)
-
-### Provider Handler Registry (`providers/registry.ts`)
-- [ ] Handler is imported and registered (if handler exists)
-- [ ] Registry key matches the `provider` field on the trigger configs
-- [ ] Entries are in alphabetical order
-
-### Block Wiring (`blocks/blocks/{service}.ts`)
-- [ ] Block has `triggers.enabled: true`
-- [ ] `triggers.available` lists all trigger IDs
-- [ ] All trigger subBlocks are spread into `subBlocks`: `...getTrigger('id').subBlocks`
-- [ ] No trigger IDs in `triggers.available` that aren't in the registry
-- [ ] No trigger subBlocks spread that aren't in `triggers.available`
-
-## Step 7: Validate Security
-
-- [ ] Webhook secrets are never logged (not even at debug level)
-- [ ] Auth verification runs before any event processing
-- [ ] No secret comparison uses `===` (must use `safeCompare` or `crypto.timingSafeEqual`)
-- [ ] Timestamp/replay protection is reasonable (not too tight for retries, not too loose for security)
-- [ ] Raw body is used for signature verification (not re-serialized JSON)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (runtime errors, security issues, or data loss):
-- Wrong HMAC algorithm or header name
-- `formatInput` keys don't match trigger `outputs`
-- Missing `verifyAuth` when the service sends signed webhooks
-- `matchEvent` returns non-boolean values
-- Provider-specific logic leaking into shared orchestration files
-- Trigger IDs mismatch between trigger files, registry, and block
-- `createSubscription` calling wrong API endpoint
-- Auth comparison using `===` instead of `safeCompare`
-
-**Warning** (convention violations or usability issues):
-- Missing `extractIdempotencyId` when the service provides delivery IDs
-- Timestamps in idempotency keys (breaks dedup on retries)
-- Missing challenge handling when the service requires URL verification
-- Output schema missing fields that `formatInput` returns (undiscoverable data)
-- Overly tight timestamp skew window that rejects legitimate retries
-- `matchEvent` not filtering challenge/verification events
-- Setup instructions missing important steps
-
-**Suggestion** (minor improvements):
-- More specific output field descriptions
-- Additional output fields that could be exposed
-- Better error messages in `createSubscription`
-- Logging improvements
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run type-check` passes
-2. Re-read all modified files to verify fixes are correct
-3. Provider handler tests pass (if they exist): `bun test {service}`
-
-## Checklist Summary
-
-- [ ] Read all trigger files, provider handler, types, registries, and block
-- [ ] Pulled and read official webhook/API documentation
-- [ ] Validated trigger definitions: options, instructions, extra fields, outputs
-- [ ] Validated primary/secondary trigger distinction (`includeDropdown`)
-- [ ] Validated provider handler: auth, matchEvent, formatInput, idempotency
-- [ ] Validated output alignment: every `outputs` key ↔ every `formatInput` key
-- [ ] Validated subscription lifecycle: createSubscription, deleteSubscription, no shared-file edits
-- [ ] Validated registration: trigger registry, handler registry, block wiring
-- [ ] Validated security: safe comparison, no secret logging, replay protection
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] `bun run type-check` passes after fixes

.cursor/commands/you-might-not-need-a-callback.md

@@ -1,30 +0,0 @@
-# You Might Not Need a Callback
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://react.dev/reference/react/useCallback — official docs on when useCallback is actually needed
-
-## Anti-patterns to detect
-
-1. **useCallback on functions not passed as props or deps**: No benefit if only called within the same component.
-2. **useCallback with deps that change every render**: Memoization is wasted.
-3. **useCallback on handlers passed to native elements**: `<button onClick={fn}>` doesn't benefit from stable references.
-4. **useCallback wrapping functions that return new objects/arrays**: Memoization at the wrong level.
-5. **useCallback with empty deps when deps are needed**: Stale closures.
-6. **Pairing useCallback + React.memo unnecessarily**: Only optimize when you've measured a problem.
-7. **useCallback in hooks that don't need stable references**: Not every hook return needs memoization.
-
-Note: This codebase uses a ref pattern for stable callbacks (`useRef` + empty deps). That pattern is correct — don't flag it.
-
-## Steps
-
-1. Read the reference above
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.cursor/commands/you-might-not-need-a-memo.md

@@ -1,28 +0,0 @@
-# You Might Not Need a Memo
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## References
-
-Read before analyzing:
-1. https://overreacted.io/before-you-memo/ — two techniques to avoid memo entirely
-
-## Anti-patterns to detect
-
-1. **State can be moved down instead of memoizing**: Move state into a smaller child so the slow component stops re-rendering without memo.
-2. **Children can be lifted up**: Extract stateful part, pass expensive subtree as `children` — children as props don't re-render when parent state changes.
-3. **useMemo on cheap computations**: Small array filters, string concat, arithmetic don't need memoization.
-4. **useMemo with constantly-changing deps**: Deps change every render = useMemo does nothing.
-5. **useMemo to stabilize props for non-memoized children**: If the child isn't wrapped in React.memo, stable references don't matter.
-6. **React.memo on components that always receive new props**: Fix the parent instead.
-7. **useMemo for derived state**: Just compute inline during render.
-
-## Steps
-
-1. Read the reference above
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.cursor/commands/you-might-not-need-an-effect.md

@@ -1,12 +0,0 @@
-# You Might Not Need an Effect
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-Steps:
-1. Read https://react.dev/learn/you-might-not-need-an-effect to understand the guidelines
-2. Analyze the specified scope for useEffect anti-patterns
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.cursor/commands/you-might-not-need-state.md

@@ -1,33 +0,0 @@
-# You Might Not Need State
-
-Arguments:
-- scope: what to analyze (default: your current changes). Examples: "diff to main", "PR #123", "src/components/", "whole codebase"
-- fix: whether to apply fixes (default: true). Set to false to only propose changes.
-
-User arguments: $ARGUMENTS
-
-## Context
-
-This codebase uses React Query for all server state and Zustand for client-only global state. useState should only be used for ephemeral UI concerns (open/closed, hover, local form input). Server data should never be copied into useState or Zustand — React Query is the single source of truth.
-
-## References
-
-Read these before analyzing:
-1. https://react.dev/learn/choosing-the-state-structure — 5 principles for structuring state
-2. https://tkdodo.eu/blog/dont-over-use-state — never store derived/computed values in state
-3. https://tkdodo.eu/blog/putting-props-to-use-state — never mirror props into state via useEffect
-
-## Anti-patterns to detect
-
-1. **Derived state stored in useState**: If a value can be computed from props, other state, or query data, compute it inline during render instead of storing it in state.
-2. **Server state copied into useState**: Never `useState` + `useEffect` to sync React Query data into local state. Use query data directly. The only exception is forms where users edit server data.
-3. **Props mirrored into state**: Never `useState(prop)` + `useEffect(() => setState(prop))`. Use the prop directly, or use a key to reset component state.
-4. **Chained useEffect state updates**: Never chain Effects that set state to trigger other Effects. Calculate all derived values in the event handler or inline during render.
-5. **Storing objects when an ID suffices**: Store `selectedId` not a copy of the selected object. Derive the object: `items.find(i => i.id === selectedId)`.
-6. **State that duplicates Zustand or React Query**: If the data already lives in a store or query cache, don't create a parallel useState.
-
-## Steps
-
-1. Read the references above to understand the guidelines
-2. Analyze the specified scope for the anti-patterns listed above
-3. If fix=true, apply the fixes. If fix=false, propose the fixes without applying.

.cursor/rules/constitution.mdc

@@ -1,76 +0,0 @@
----
-description: Sim product language, positioning, and tone guidelines
-globs: ["apps/sim/app/(landing)/**", "apps/sim/app/(home)/**", "apps/docs/**", "apps/sim/app/manifest.ts", "apps/sim/app/sitemap.ts", "apps/sim/app/robots.ts", "apps/sim/app/llms.txt/**", "apps/sim/app/llms-full.txt/**", "apps/sim/app/(landing)/**/structured-data*", "apps/docs/**/structured-data*", "**/metadata*", "**/seo*"]
----
-
-# Sim — Language & Positioning
-
-When editing user-facing copy (landing pages, docs, metadata, marketing), follow these rules.
-
-## Identity
-
-Sim is the **AI workspace** where teams build and run AI agents. Not a workflow tool, not an agent framework, not an automation platform.
-
-**Short definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents.
-
-**Full definition:** Sim is the open-source AI workspace where teams build, deploy, and manage AI agents. Connect 1,000+ integrations and every major LLM to create agents that automate real work — visually, conversationally, or with code.
-
-## Audience
-
-**Primary:** Teams building AI agents for their organization — IT, operations, and technical teams who need governance, security, lifecycle management, and collaboration.
-
-**Secondary:** Individual builders and developers who care about speed, flexibility, and open source.
-
-## Required Language
-
-| Concept | Use | Never use |
-|---------|-----|-----------|
-| The product | "AI workspace" | "workflow tool", "automation platform", "agent framework" |
-| Building | "build agents", "create agents" | "create workflows" (unless describing the workflow module specifically) |
-| Visual builder | "workflow builder" or "visual builder" | "canvas", "graph editor" |
-| Mothership | "Mothership" (capitalized) | "chat", "AI assistant", "copilot" |
-| Deployment | "deploy", "ship" | "publish", "activate" |
-| Audience | "teams", "builders" | "users", "customers" (in marketing copy) |
-| What agents do | "automate real work" | "automate tasks", "automate workflows" |
-| Our advantage | "open-source AI workspace" | "open-source platform" |
-
-## Tone
-
-- **Direct.** Short sentences. Active voice. Lead with what it does.
-- **Concrete.** Name specific things — "Slack bots, compliance agents, data pipelines" — not abstractions.
-- **Confident, not loud.** No exclamation marks or superlatives.
-- **Simple.** If a 16-year-old can't understand the sentence, rewrite it.
-
-## Claim Hierarchy
-
-When describing Sim, always lead with the most differentiated claim:
-
-1. **What it is:** "The AI workspace for teams"
-2. **What you do:** "Build, deploy, and manage AI agents"
-3. **How:** "Visually, conversationally, or with code"
-4. **Scale:** "1,000+ integrations, every major LLM"
-5. **Trust:** "Open source. SOC2. Trusted by 100,000+ builders."
-
-## Module Descriptions
-
-| Module | One-liner |
-|--------|-----------|
-| **Mothership** | Your AI command center. Build and manage everything in natural language. |
-| **Workflows** | The visual builder. Connect blocks, models, and integrations into agent logic. |
-| **Knowledge Base** | Your agents' memory. Upload docs, sync sources, build vector databases. |
-| **Tables** | A database, built in. Store, query, and wire structured data into agent runs. |
-| **Files** | Upload, create, and share. One store for your team and every agent. |
-| **Logs** | Full visibility, every run. Trace execution block by block. |
-
-## What We Never Say
-
-- Never call Sim "just a workflow tool"
-- Never compare only on integration count — we win on AI-native capabilities
-- Never use "no-code" as the primary descriptor — say "visually, conversationally, or with code"
-- Never promise unshipped features
-- Never use jargon ("RAG", "vector database", "MCP") without plain-English explanation on public pages
-- Avoid "agentic workforce" as a primary term — use "AI agents"
-
-## Vision
-
-Sim becomes the default environment where teams build AI agents — not a tool you visit for one task, but a workspace you live in. Workflows are one module; Mothership is another. The workspace is the constant; the interface adapts.

.cursor/rules/emcn-components.mdc

@@ -1,35 +0,0 @@
----
-description: EMCN component library patterns
-globs: ["apps/sim/components/emcn/**"]
----
-
-# EMCN Components
-
-Import from `@/components/emcn`, never from subpaths (except CSS files).
-
-## CVA vs Direct Styles
-
-**Use CVA when:** 2+ variants (primary/secondary, sm/md/lg)
-
-```tsx
-const buttonVariants = cva('base-classes', {
-  variants: { variant: { default: '...', primary: '...' } }
-})
-export { Button, buttonVariants }
-```
-
-**Use direct className when:** Single consistent style, no variations
-
-```tsx
-function Label({ className, ...props }) {
-  return <Primitive className={cn('style-classes', className)} {...props} />
-}
-```
-
-## Rules
-
-- Use Radix UI primitives for accessibility
-- Export component and variants (if using CVA)
-- TSDoc with usage examples
-- Consistent tokens: `font-medium`, `text-[12px]`, `rounded-[4px]`
-- `transition-colors` for hover states

.cursor/rules/global.mdc

@@ -1,62 +0,0 @@
----
-description: Global coding standards that apply to all files
-alwaysApply: true
----
-
-# Global Standards
-
-You are a professional software engineer. All code must follow best practices: accurate, readable, clean, and efficient.
-
-## Logging
-Import `createLogger` from `@sim/logger`. Use `logger.info`, `logger.warn`, `logger.error` instead of `console.log`.
-
-## Comments
-Use TSDoc for documentation. No `====` separators. No non-TSDoc comments.
-
-## Styling
-Never update global styles. Keep all styling local to components.
-
-## ID Generation
-Never use `crypto.randomUUID()`, `nanoid`, or the `uuid` package directly. Use the utilities from `@sim/utils/id`:
-
-- `generateId()` — UUID v4, use by default
-- `generateShortId(size?)` — short URL-safe ID (default 21 chars), for compact identifiers
-
-Both use `crypto.getRandomValues()` under the hood and work in all contexts including non-secure (HTTP) browsers.
-
-```typescript
-// ✗ Bad
-import { nanoid } from 'nanoid'
-import { v4 as uuidv4 } from 'uuid'
-const id = crypto.randomUUID()
-
-// ✓ Good
-import { generateId, generateShortId } from '@sim/utils/id'
-const uuid = generateId()
-const shortId = generateShortId()
-const tiny = generateShortId(8)
-```
-
-## Common Utilities
-Use shared helpers from `@sim/utils` instead of writing inline implementations:
-
-- `sleep(ms)` — async delay. Never write `new Promise(resolve => setTimeout(resolve, ms))`
-- `toError(value)` — normalize unknown caught values to `Error`. Never write `e instanceof Error ? e : new Error(String(e))`
-- `toError(value).message` — get error message safely. Never write `e instanceof Error ? e.message : String(e)`
-
-```typescript
-// ✗ Bad
-await new Promise(resolve => setTimeout(resolve, 1000))
-const msg = error instanceof Error ? error.message : String(error)
-const err = error instanceof Error ? error : new Error(String(error))
-
-// ✓ Good
-import { sleep } from '@sim/utils/helpers'
-import { toError } from '@sim/utils/errors'
-await sleep(1000)
-const msg = toError(error).message
-const err = toError(error)
-```
-
-## Package Manager
-Use `bun` and `bunx`, not `npm` and `npx`.

.cursor/rules/landing-seo-geo.mdc

@@ -1,26 +0,0 @@
----
-description: SEO and GEO guidelines for the landing page
-globs: ["apps/sim/app/(home)/**/*.tsx"]
----
-
-# Landing Page — SEO / GEO
-
-## SEO
-
-- One `<h1>` per page, in Hero only — never add another.
-- Strict heading hierarchy: H1 (Hero) → H2 (section titles) → H3 (feature names).
-- Every section: `<section id="…" aria-labelledby="…-heading">`.
-- Decorative/animated elements: `aria-hidden="true"`.
-- All internal routes use Next.js `<Link>` (crawlable). External links get `rel="noopener noreferrer"`.
-- Navbar is a Server Component (no `'use client'`) for immediate crawlability. Logo `<Image>` has `priority` (LCP element).
-- Navbar `<nav>` carries `SiteNavigationElement` schema.org markup.
-- Feature lists must stay in sync with `WebApplication.featureList` in `structured-data.tsx`.
-
-## GEO (Generative Engine Optimisation)
-
-- **Answer-first pattern**: each section's H2 + subtitle should directly answer a user question (e.g. "What is Sim?", "How fast can I deploy?").
-- **Atomic answer blocks**: each feature / template card should be independently extractable by an AI summariser.
-- **Entity consistency**: always write "Sim" by name — never "the platform" or "our tool".
-- **Keyword density**: first 150 visible chars of Hero must name "Sim", "AI agents", "agentic workflows".
-- **sr-only summaries**: Hero and Templates each have a `<p className="sr-only">` (~50 words) as an atomic product/catalog summary for AI citation.
-- **Specific numbers**: prefer concrete figures ("1,000+ integrations", "15+ AI providers") over vague claims.

.cursor/rules/sim-architecture.mdc

@@ -1,56 +0,0 @@
----
-description: Core architecture principles for the Sim app
-globs: ["apps/sim/**"]
----
-
-# Sim App Architecture
-
-## Core Principles
-1. **Single Responsibility**: Each component, hook, store has one clear purpose
-2. **Composition Over Complexity**: Break down complex logic into smaller pieces
-3. **Type Safety First**: TypeScript interfaces for all props, state, return types
-4. **Predictable State**: Zustand for global state, useState for UI-only concerns
-
-## Root-Level Structure
-
-```
-apps/sim/
-├── app/                 # Next.js app router (pages, API routes)
-├── blocks/              # Block definitions and registry
-├── components/          # Shared UI (emcn/, ui/)
-├── executor/            # Workflow execution engine
-├── hooks/               # Shared hooks (queries/, selectors/)
-├── lib/                 # App-wide utilities
-├── providers/           # LLM provider integrations
-├── stores/              # Zustand stores
-├── tools/               # Tool definitions
-└── triggers/            # Trigger definitions
-```
-
-## Feature Organization
-
-Features live under `app/workspace/[workspaceId]/`:
-
-```
-feature/
-├── components/          # Feature components
-├── hooks/               # Feature-scoped hooks
-├── utils/               # Feature-scoped utilities (2+ consumers)
-├── feature.tsx          # Main component
-└── page.tsx             # Next.js page entry
-```
-
-## Naming Conventions
-- **Components**: PascalCase (`WorkflowList`)
-- **Hooks**: `use` prefix (`useWorkflowOperations`)
-- **Files**: kebab-case (`workflow-list.tsx`)
-- **Stores**: `stores/feature/store.ts`
-- **Constants**: SCREAMING_SNAKE_CASE
-- **Interfaces**: PascalCase with suffix (`WorkflowListProps`)
-
-## Utils Rules
-
-- **Never create `utils.ts` for single consumer** - inline it
-- **Create `utils.ts` when** 2+ files need the same helper
-- **Check existing sources** before duplicating (`lib/` has many utilities)
-- **Location**: `lib/` (app-wide) → `feature/utils/` (feature-scoped) → inline (single-use)

.cursor/rules/sim-components.mdc

@@ -1,48 +0,0 @@
----
-description: Component patterns and structure for React components
-globs: ["apps/sim/**/*.tsx"]
----
-
-# Component Patterns
-
-## Structure Order
-
-```typescript
-'use client' // Only if using hooks
-
-// Imports (external → internal)
-// Constants at module level
-const CONFIG = { SPACING: 8 } as const
-
-// Props interface
-interface ComponentProps {
-  requiredProp: string
-  optionalProp?: boolean
-}
-
-export function Component({ requiredProp, optionalProp = false }: ComponentProps) {
-  // a. Refs
-  // b. External hooks (useParams, useRouter)
-  // c. Store hooks
-  // d. Custom hooks
-  // e. Local state
-  // f. useMemo
-  // g. useCallback
-  // h. useEffect
-  // i. Return JSX
-}
-```
-
-## Rules
-
-1. `'use client'` only when using React hooks
-2. Always define props interface
-3. Extract constants with `as const`
-4. Semantic HTML (`aside`, `nav`, `article`)
-5. Optional chain callbacks: `onAction?.(id)`
-
-## Component Extraction
-
-**Extract when:** 50+ lines, used in 2+ files, or has own state/logic
-
-**Keep inline when:** < 10 lines, single use, purely presentational

.cursor/rules/sim-hooks.mdc

@@ -1,54 +0,0 @@
----
-description: Custom hook patterns and best practices
-globs: ["apps/sim/**/use-*.ts", "apps/sim/**/hooks/**/*.ts"]
----
-
-# Hook Patterns
-
-## Structure
-
-```typescript
-interface UseFeatureProps {
-  id: string
-  onSuccess?: (result: Result) => void
-}
-
-export function useFeature({ id, onSuccess }: UseFeatureProps) {
-  // 1. Refs for stable dependencies
-  const idRef = useRef(id)
-  const onSuccessRef = useRef(onSuccess)
-
-  // 2. State
-  const [data, setData] = useState<Data | null>(null)
-  const [isLoading, setIsLoading] = useState(false)
-
-  // 3. Sync refs
-  useEffect(() => {
-    idRef.current = id
-    onSuccessRef.current = onSuccess
-  }, [id, onSuccess])
-
-  // 4. Operations (useCallback with empty deps when using refs)
-  const fetchData = useCallback(async () => {
-    setIsLoading(true)
-    try {
-      const result = await fetch(`/api/${idRef.current}`).then(r => r.json())
-      setData(result)
-      onSuccessRef.current?.(result)
-    } finally {
-      setIsLoading(false)
-    }
-  }, [])
-
-  return { data, isLoading, fetchData }
-}
-```
-
-## Rules
-
-1. Single responsibility per hook
-2. Props interface required
-3. Refs for stable callback dependencies
-4. Wrap returned functions in useCallback
-5. Always try/catch async operations
-6. Track loading/error states

.cursor/rules/sim-imports.mdc

@@ -1,61 +0,0 @@
----
-description: Import patterns for the Sim application
-globs: ["apps/sim/**/*.ts", "apps/sim/**/*.tsx"]
----
-
-# Import Patterns
-
-## Absolute Imports
-
-**Always use absolute imports.** Never use relative imports.
-
-```typescript
-// ✓ Good
-import { useWorkflowStore } from '@/stores/workflows/store'
-import { Button } from '@/components/ui/button'
-
-// ✗ Bad
-import { useWorkflowStore } from '../../../stores/workflows/store'
-```
-
-## Barrel Exports
-
-Use barrel exports (`index.ts`) when a folder has 3+ exports. Import from barrel, not individual files.
-
-```typescript
-// ✓ Good
-import { Dashboard, Sidebar } from '@/app/workspace/[workspaceId]/logs/components'
-
-// ✗ Bad
-import { Dashboard } from '@/app/workspace/[workspaceId]/logs/components/dashboard/dashboard'
-```
-
-## No Re-exports
-
-Do not re-export from non-barrel files. Import directly from the source.
-
-```typescript
-// ✓ Good - import from where it's declared
-import { CORE_TRIGGER_TYPES } from '@/stores/logs/filters/types'
-
-// ✗ Bad - re-exporting in utils.ts then importing from there
-import { CORE_TRIGGER_TYPES } from '@/app/workspace/.../utils'
-```
-
-## Import Order
-
-1. React/core libraries
-2. External libraries
-3. UI components (`@/components/emcn`, `@/components/ui`)
-4. Utilities (`@/lib/...`)
-5. Stores (`@/stores/...`)
-6. Feature imports
-7. CSS imports
-
-## Type Imports
-
-Use `type` keyword for type-only imports:
-
-```typescript
-import type { WorkflowLog } from '@/stores/logs/types'
-```

.cursor/rules/sim-integrations.mdc

@@ -1,285 +0,0 @@
----
-description: Adding new integrations (tools, blocks, triggers)
-globs: ["apps/sim/tools/**", "apps/sim/blocks/**", "apps/sim/triggers/**"]
----
-
-# Adding Integrations
-
-## Overview
-
-Adding a new integration typically requires:
-1. **Tools** - API operations (`tools/{service}/`)
-2. **Block** - UI component (`blocks/blocks/{service}.ts`)
-3. **Icon** - SVG icon (`components/icons.tsx`)
-4. **Trigger** (optional) - Webhooks/polling (`triggers/{service}/`)
-
-Always look up the service's API docs first.
-
-## 1. Tools (`tools/{service}/`)
-
-```
-tools/{service}/
-├── index.ts           # Export all tools
-├── types.ts           # Params/response types
-├── {action}.ts        # Individual tool (e.g., send_message.ts)
-└── ...
-```
-
-**Tool file structure:**
-
-```typescript
-// tools/{service}/{action}.ts
-import type { {Service}Params, {Service}Response } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-export const {service}{Action}Tool: ToolConfig<{Service}Params, {Service}Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: 'What this tool does',
-  version: '1.0.0',
-  oauth: { required: true, provider: '{service}' }, // if OAuth
-  params: { /* param definitions */ },
-  request: {
-    url: '/api/tools/{service}/{action}',
-    method: 'POST',
-    headers: () => ({ 'Content-Type': 'application/json' }),
-    body: (params) => ({ ...params }),
-  },
-  transformResponse: async (response) => {
-    const data = await response.json()
-    if (!data.success) throw new Error(data.error)
-    return { success: true, output: data.output }
-  },
-  outputs: { /* output definitions */ },
-}
-```
-
-**Register in `tools/registry.ts`:**
-
-```typescript
-import { {service}{Action}Tool } from '@/tools/{service}'
-// Add to registry object
-{service}_{action}: {service}{Action}Tool,
-```
-
-## 2. Block (`blocks/blocks/{service}.ts`)
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import type { {Service}Response } from '@/tools/{service}/types'
-
-export const {Service}Block: BlockConfig<{Service}Response> = {
-  type: '{service}',
-  name: '{Service}',
-  description: 'Short description',
-  longDescription: 'Detailed description',
-  category: 'tools',
-  bgColor: '#hexcolor',
-  icon: {Service}Icon,
-  subBlocks: [ /* see SubBlock Properties below */ ],
-  tools: {
-    access: ['{service}_{action}', ...],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-      params: (params) => ({ ...params }),
-    },
-  },
-  inputs: { /* input definitions */ },
-  outputs: { /* output definitions */ },
-}
-```
-
-### SubBlock Properties
-
-```typescript
-{
-  id: 'fieldName',           // Unique identifier
-  title: 'Field Label',      // UI label
-  type: 'short-input',       // See SubBlock Types below
-  placeholder: 'Hint text',
-  required: true,            // See Required below
-  condition: { ... },        // See Condition below
-  dependsOn: ['otherField'], // See DependsOn below
-  mode: 'basic',             // 'basic' | 'advanced' | 'both' | 'trigger'
-}
-```
-
-**SubBlock Types:** `short-input`, `long-input`, `dropdown`, `code`, `switch`, `slider`, `oauth-input`, `channel-selector`, `user-selector`, `file-upload`, etc.
-
-### `condition` - Show/hide based on another field
-
-```typescript
-// Show when operation === 'send'
-condition: { field: 'operation', value: 'send' }
-
-// Show when operation is 'send' OR 'read'
-condition: { field: 'operation', value: ['send', 'read'] }
-
-// Show when operation !== 'send'
-condition: { field: 'operation', value: 'send', not: true }
-
-// Complex: NOT in list AND another condition
-condition: {
-  field: 'operation',
-  value: ['list_channels', 'list_users'],
-  not: true,
-  and: { field: 'destinationType', value: 'dm', not: true }
-}
-```
-
-### `required` - Field validation
-
-```typescript
-// Always required
-required: true
-
-// Conditionally required (same syntax as condition)
-required: { field: 'operation', value: 'send' }
-```
-
-### `dependsOn` - Clear field when dependencies change
-
-```typescript
-// Clear when credential changes
-dependsOn: ['credential']
-
-// Clear when authMethod changes AND (credential OR botToken) changes
-dependsOn: { all: ['authMethod'], any: ['credential', 'botToken'] }
-```
-
-### `mode` - When to show field
-
-- `'basic'` - Only in basic mode (default UI)
-- `'advanced'` - Only in advanced mode (manual input)
-- `'both'` - Show in both modes (default)
-- `'trigger'` - Only when block is used as trigger
-
-### `canonicalParamId` - Link basic/advanced alternatives
-
-Use to map multiple UI inputs to a single logical parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'fileSelector',
-  type: 'file-selector',
-  mode: 'basic',
-  canonicalParamId: 'fileId',
-  required: true,
-},
-// Advanced mode: Manual input
-{
-  id: 'manualFileId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'fileId',
-  required: true,
-},
-```
-
-**Critical Rules:**
-- `canonicalParamId` must NOT match any subblock's `id`
-- `canonicalParamId` must be unique per operation/condition context
-- **Required consistency:** All subblocks in a canonical group must have the same `required` status
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs
-- **Params function:** Must use canonical param IDs (raw IDs are deleted after canonical transformation)
-
-**Register in `blocks/registry.ts`:**
-
-```typescript
-import { {Service}Block } from '@/blocks/blocks/{service}'
-// Add to registry object (alphabetically)
-{service}: {Service}Block,
-```
-
-## 3. Icon (`components/icons.tsx`)
-
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg {...props} viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
-      {/* SVG path from service's brand assets */}
-    </svg>
-  )
-}
-```
-
-## 4. Trigger (`triggers/{service}/`) - Optional
-
-```
-triggers/{service}/
-├── index.ts           # Export all triggers
-├── webhook.ts         # Webhook handler
-├── utils.ts           # Shared utilities
-└── {event}.ts         # Specific event handlers
-```
-
-**Register in `triggers/registry.ts`:**
-
-```typescript
-import { {service}WebhookTrigger } from '@/triggers/{service}'
-// Add to TRIGGER_REGISTRY
-{service}_webhook: {service}WebhookTrigger,
-```
-
-## File Handling
-
-When integrations handle file uploads/downloads, use `UserFile` objects consistently.
-
-### File Input (Uploads)
-
-1. **Block subBlocks:** Use basic/advanced mode pattern with `canonicalParamId`
-2. **Normalize in block config:** Use `normalizeFileInput` from `@/blocks/utils`
-3. **Internal API route:** Create route that uses `downloadFileFromStorage` to get file content
-4. **Tool routes to internal API:** Don't call external APIs directly with files
-
-```typescript
-// In block tools.config:
-import { normalizeFileInput } from '@/blocks/utils'
-
-const normalizedFile = normalizeFileInput(
-  params.uploadFile || params.fileRef || params.fileContent,
-  { single: true }
-)
-if (normalizedFile) params.file = normalizedFile
-```
-
-### File Output (Downloads)
-
-Use `FileToolProcessor` in tool `transformResponse` to store files:
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-const processor = new FileToolProcessor(context)
-const file = await processor.processFileData({
-  data: base64Content,
-  mimeType: 'application/pdf',
-  filename: 'doc.pdf',
-})
-```
-
-### Key Helpers
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-
-## Checklist
-
-- [ ] Look up API docs for the service
-- [ ] Create `tools/{service}/types.ts` with proper types
-- [ ] Create tool files for each operation
-- [ ] Create `tools/{service}/index.ts` barrel export
-- [ ] Register tools in `tools/registry.ts`
-- [ ] Add icon to `components/icons.tsx`
-- [ ] Create block in `blocks/blocks/{service}.ts`
-- [ ] Register block in `blocks/registry.ts`
-- [ ] (Optional) Create triggers in `triggers/{service}/`
-- [ ] (Optional) Register triggers in `triggers/registry.ts`
-- [ ] (If file uploads) Create internal API route with `downloadFileFromStorage`
-- [ ] (If file uploads) Use `normalizeFileInput` in block config

.cursor/rules/sim-queries.mdc

@@ -1,126 +0,0 @@
----
-description: React Query patterns for the Sim application
-globs: ["apps/sim/hooks/queries/**/*.ts"]
----
-
-# React Query Patterns
-
-All React Query hooks live in `hooks/queries/`. All server state must go through React Query — never use `useState` + `fetch` in components for data fetching or mutations.
-
-## Query Key Factory
-
-Every query file defines a hierarchical keys factory with an `all` root key and intermediate plural keys for prefix-level invalidation:
-
-```typescript
-export const entityKeys = {
-  all: ['entity'] as const,
-  lists: () => [...entityKeys.all, 'list'] as const,
-  list: (workspaceId?: string) => [...entityKeys.lists(), workspaceId ?? ''] as const,
-  details: () => [...entityKeys.all, 'detail'] as const,
-  detail: (id?: string) => [...entityKeys.details(), id ?? ''] as const,
-}
-```
-
-Never use inline query keys — always use the factory.
-
-## File Structure
-
-```typescript
-// 1. Query keys factory
-// 2. Types (if needed)
-// 3. Private fetch functions (accept signal parameter)
-// 4. Exported hooks
-```
-
-## Query Hook
-
-- Every `queryFn` must destructure and forward `signal` for request cancellation
-- Every query must have an explicit `staleTime`
-- Use `keepPreviousData` only on variable-key queries (where params change), never on static keys
-
-```typescript
-async function fetchEntities(workspaceId: string, signal?: AbortSignal) {
-  const response = await fetch(`/api/entities?workspaceId=${workspaceId}`, { signal })
-  if (!response.ok) throw new Error('Failed to fetch entities')
-  return response.json()
-}
-
-export function useEntityList(workspaceId?: string, options?: { enabled?: boolean }) {
-  return useQuery({
-    queryKey: entityKeys.list(workspaceId),
-    queryFn: ({ signal }) => fetchEntities(workspaceId as string, signal),
-    enabled: Boolean(workspaceId) && (options?.enabled ?? true),
-    staleTime: 60 * 1000,
-    placeholderData: keepPreviousData, // OK: workspaceId varies
-  })
-}
-```
-
-## Mutation Hook
-
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- Invalidation must cover all affected query key prefixes (lists, details, related views)
-
-```typescript
-export function useCreateEntity() {
-  const queryClient = useQueryClient()
-  return useMutation({
-    mutationFn: async (variables) => { /* fetch POST */ },
-    onSuccess: () => {
-      queryClient.invalidateQueries({ queryKey: entityKeys.lists() })
-    },
-  })
-}
-```
-
-## Optimistic Updates
-
-For optimistic mutations, use `onSettled` (not `onSuccess`) for cache reconciliation — `onSettled` fires on both success and error, ensuring the cache is always reconciled with the server.
-
-```typescript
-export function useUpdateEntity() {
-  const queryClient = useQueryClient()
-  return useMutation({
-    mutationFn: async (variables) => { /* ... */ },
-    onMutate: async (variables) => {
-      await queryClient.cancelQueries({ queryKey: entityKeys.detail(variables.id) })
-      const previous = queryClient.getQueryData(entityKeys.detail(variables.id))
-      queryClient.setQueryData(entityKeys.detail(variables.id), /* optimistic value */)
-      return { previous }
-    },
-    onError: (_err, variables, context) => {
-      queryClient.setQueryData(entityKeys.detail(variables.id), context?.previous)
-    },
-    onSettled: (_data, _error, variables) => {
-      queryClient.invalidateQueries({ queryKey: entityKeys.lists() })
-      queryClient.invalidateQueries({ queryKey: entityKeys.detail(variables.id) })
-    },
-  })
-}
-```
-
-For optimistic mutations syncing with Zustand, use `createOptimisticMutationHandlers` from `@/hooks/queries/utils/optimistic-mutation`.
-
-## useCallback Dependencies
-
-Never include mutation objects (e.g., `createEntity`) in `useCallback` dependency arrays — the mutation object is not referentially stable and changes on every state update. The `.mutate()` and `.mutateAsync()` functions are stable in TanStack Query v5.
-
-```typescript
-// ✗ Bad — causes unnecessary recreations
-const handler = useCallback(() => {
-  createEntity.mutate(data)
-}, [createEntity]) // unstable reference
-
-// ✓ Good — omit from deps, mutate is stable
-const handler = useCallback(() => {
-  createEntity.mutate(data)
-  // eslint-disable-next-line react-hooks/exhaustive-deps
-}, [data])
-```
-
-## Naming
-
-- **Keys**: `entityKeys`
-- **Query hooks**: `useEntity`, `useEntityList`
-- **Mutation hooks**: `useCreateEntity`, `useUpdateEntity`, `useDeleteEntity`
-- **Fetch functions**: `fetchEntity`, `fetchEntities` (private)

.cursor/rules/sim-sandbox.mdc

@@ -1,85 +0,0 @@
----
-description: Isolated-vm sandbox worker security policy. Hard rules for anything that lives in the worker child process that runs user code.
-globs: ["apps/sim/lib/execution/isolated-vm-worker.cjs", "apps/sim/lib/execution/isolated-vm.ts", "apps/sim/lib/execution/sandbox/**", "apps/sim/sandbox-tasks/**"]
----
-
-# Sim Sandbox — Worker Security Policy
-
-The isolated-vm worker child process at
-`apps/sim/lib/execution/isolated-vm-worker.cjs` runs untrusted user code inside
-V8 isolates. The process itself is a trust boundary. Everything in this rule is
-about what must **never** live in that process.
-
-## Hard rules
-
-1. **No app credentials in the worker process**. The worker must not hold, load,
-   or receive via IPC: database URLs, Redis URLs, AWS keys, Stripe keys,
-   session-signing keys, encryption keys, OAuth client secrets, internal API
-   secrets, or any LLM / email / search provider API keys. If you catch yourself
-   `require`'ing `@/lib/auth`, `@sim/db`, `@/lib/uploads/core/storage-service`,
-   or anything that imports `env` directly inside the worker, stop and use a
-   host-side broker instead.
-
-2. **Host-side brokers own all credentialed work**. The worker can only access
-   resources through `ivm.Reference` / `ivm.Callback` bridges back to the host
-   process. Today the only broker is `workspaceFileBroker`
-   (`apps/sim/lib/execution/sandbox/brokers/workspace-file.ts`); adding a new
-   one requires co-reviewing this file.
-
-3. **Host-side brokers must scope every resource access to a single tenant**.
-   The `SandboxBrokerContext` always carries `workspaceId`. Any new broker that
-   accesses storage, DB, or an external API must use `ctx.workspaceId` to scope
-   the lookup — never accept a raw path, key, or URL from isolate code without
-   validation.
-
-4. **Nothing that runs in the isolate is trusted, even if we wrote it**. The
-   task `bootstrap` and `finalize` strings in `apps/sim/sandbox-tasks/` execute
-   inside the isolate. They must treat `globalThis` as adversarial — no pulling
-   values from it that might have been mutated by user code. The hardening
-   script in `executeTask` undefines dangerous globals before user code runs.
-
-## Why
-
-A V8 JIT bug (Chrome ships these roughly monthly) gives an attacker a native
-code primitive inside the process that owns whatever that process can reach.
-If the worker only holds `isolated-vm` + a single narrow workspace-file broker,
-a V8 escape leaks one tenant's files. If the worker holds a Stripe key or a DB
-connection, a V8 escape leaks the service.
-
-The original `doc-worker.cjs` vulnerability (CVE-class, 225 production secrets
-leaked via `/proc/1/environ`) was the forcing function for this architecture.
-Keep the blast radius small.
-
-## Checklist for changes to `isolated-vm-worker.cjs`
-
-Before landing any change that adds a new `require(...)` or `process.send(...)`
-payload or `ivm.Reference` wrapper in the worker:
-
-- [ ] Does it load a credential, key, connection string, or secret? If yes,
-      move it host-side and expose as a broker.
-- [ ] Does it import from `@/lib/auth`, `@sim/db`, `@/lib/uploads/core/*`,
-      `@/lib/core/config/env`, or any module that reads `process.env` of the
-      main app? If yes, same — move host-side.
-- [ ] Does it expose a resource that's workspace-scoped without taking a
-      `workspaceId`? If yes, re-scope.
-- [ ] Did you update the broker limits (`IVM_MAX_BROKER_ARGS_JSON_CHARS`,
-      `IVM_MAX_BROKER_RESULT_JSON_CHARS`, `IVM_MAX_BROKERS_PER_EXECUTION`) if
-      the new broker can emit large payloads or fire frequently?
-
-## What the worker *may* hold
-
-- `isolated-vm` module
-- Node built-ins: `node:fs` (only for reading the checked-in bundle `.cjs`
-  files) and `node:path`
-- The three prebuilt library bundles under
-  `apps/sim/lib/execution/sandbox/bundles/*.cjs`
-- IPC message handlers for `execute`, `cancel`, `fetchResponse`,
-  `brokerResponse`
-
-The worker deliberately has **no host-side logger**. All errors and
-diagnostics flow through IPC back to the host, which has `@sim/logger`. Do
-not add `createLogger` or console-based logging to the worker — it would
-require pulling the main app's config / env, which is exactly what this
-rule is preventing.
-
-Anything else is suspect.

.cursor/rules/sim-stores.mdc

@@ -1,70 +0,0 @@
----
-description: Zustand store patterns
-globs: ["apps/sim/**/store.ts", "apps/sim/**/stores/**/*.ts"]
----
-
-# Zustand Store Patterns
-
-Stores live in `stores/`. Complex stores split into `store.ts` + `types.ts`.
-
-## Basic Store
-
-```typescript
-import { create } from 'zustand'
-import { devtools } from 'zustand/middleware'
-import type { FeatureState } from '@/stores/feature/types'
-
-const initialState = { items: [] as Item[], activeId: null as string | null }
-
-export const useFeatureStore = create<FeatureState>()(
-  devtools(
-    (set, get) => ({
-      ...initialState,
-      setItems: (items) => set({ items }),
-      addItem: (item) => set((state) => ({ items: [...state.items, item] })),
-      reset: () => set(initialState),
-    }),
-    { name: 'feature-store' }
-  )
-)
-```
-
-## Persisted Store
-
-```typescript
-import { create } from 'zustand'
-import { persist } from 'zustand/middleware'
-
-export const useFeatureStore = create<FeatureState>()(
-  persist(
-    (set) => ({
-      width: 300,
-      setWidth: (width) => set({ width }),
-      _hasHydrated: false,
-      setHasHydrated: (v) => set({ _hasHydrated: v }),
-    }),
-    {
-      name: 'feature-state',
-      partialize: (state) => ({ width: state.width }),
-      onRehydrateStorage: () => (state) => state?.setHasHydrated(true),
-    }
-  )
-)
-```
-
-## Rules
-
-1. Use `devtools` middleware (named stores)
-2. Use `persist` only when data should survive reload
-3. `partialize` to persist only necessary state
-4. `_hasHydrated` pattern for persisted stores needing hydration tracking
-5. Immutable updates only
-6. `set((state) => ...)` when depending on previous state
-7. Provide `reset()` action
-
-## Outside React
-
-```typescript
-const items = useFeatureStore.getState().items
-useFeatureStore.setState({ items: newItems })
-```

.cursor/rules/sim-styling.mdc

@@ -1,40 +0,0 @@
----
-description: Tailwind CSS and styling conventions
-globs: ["apps/sim/**/*.tsx", "apps/sim/**/*.css"]
----
-
-# Styling Rules
-
-## Tailwind
-
-1. **No inline styles** - Use Tailwind classes
-2. **No duplicate dark classes** - Skip `dark:` when value matches light mode
-3. **Exact values** - `text-[14px]`, `h-[26px]`
-4. **Transitions** - `transition-colors` for interactive states
-
-## Conditional Classes
-
-```typescript
-import { cn } from '@/lib/utils'
-
-<div className={cn(
-  'base-classes',
-  isActive && 'active-classes',
-  disabled ? 'opacity-60' : 'hover:bg-accent'
-)} />
-```
-
-## CSS Variables
-
-For dynamic values (widths, heights) synced with stores:
-
-```typescript
-// In store
-setWidth: (width) => {
-  set({ width })
-  document.documentElement.style.setProperty('--sidebar-width', `${width}px`)
-}
-
-// In component
-<aside style={{ width: 'var(--sidebar-width)' }} />
-```

.cursor/rules/sim-testing.mdc

@@ -1,242 +0,0 @@
----
-description: Testing patterns with Vitest and @sim/testing
-globs: ["apps/sim/**/*.test.ts", "apps/sim/**/*.test.tsx"]
----
-
-
-# Testing Patterns
-
-Use Vitest. Test files: `feature.ts` → `feature.test.ts`
-
-## Global Mocks (vitest.setup.ts)
-
-These modules are mocked globally — do NOT re-mock them in test files unless you need to override behavior:
-
-- `@sim/db` → `databaseMock`
-- `@sim/db/schema` → `schemaMock`
-- `drizzle-orm` → `drizzleOrmMock`
-- `@sim/logger` → `loggerMock`
-- `@/lib/auth` → `authMock`
-- `@/lib/auth/hybrid` → `hybridAuthMock` (with default session-delegating behavior)
-- `@/lib/core/utils/request` → `requestUtilsMock`
-- `@/stores/console/store`, `@/stores/terminal`, `@/stores/execution/store`
-- `@/blocks/registry`
-- `@trigger.dev/sdk`
-
-## Structure
-
-```typescript
-/**
- * @vitest-environment node
- */
-import { createMockRequest } from '@sim/testing'
-import { beforeEach, describe, expect, it, vi } from 'vitest'
-
-const { mockGetSession } = vi.hoisted(() => ({
-  mockGetSession: vi.fn(),
-}))
-
-vi.mock('@/lib/auth', () => ({
-  auth: { api: { getSession: vi.fn() } },
-  getSession: mockGetSession,
-}))
-
-import { GET, POST } from '@/app/api/my-route/route'
-
-describe('my route', () => {
-  beforeEach(() => {
-    vi.clearAllMocks()
-    mockGetSession.mockResolvedValue({ user: { id: 'user-1' } })
-  })
-
-  it('returns data', async () => {
-    const req = createMockRequest('GET')
-    const res = await GET(req)
-    expect(res.status).toBe(200)
-  })
-})
-```
-
-## Performance Rules (Critical)
-
-### NEVER use `vi.resetModules()` + `vi.doMock()` + `await import()`
-
-This is the #1 cause of slow tests. It forces complete module re-evaluation per test.
-
-```typescript
-// BAD — forces module re-evaluation every test (~50-100ms each)
-beforeEach(() => {
-  vi.resetModules()
-  vi.doMock('@/lib/auth', () => ({ getSession: vi.fn() }))
-})
-it('test', async () => {
-  const { GET } = await import('./route')  // slow dynamic import
-})
-
-// GOOD — module loaded once, mocks reconfigured per test (~1ms each)
-const { mockGetSession } = vi.hoisted(() => ({
-  mockGetSession: vi.fn(),
-}))
-vi.mock('@/lib/auth', () => ({ getSession: mockGetSession }))
-import { GET } from '@/app/api/my-route/route'
-
-beforeEach(() => { vi.clearAllMocks() })
-it('test', () => {
-  mockGetSession.mockResolvedValue({ user: { id: '1' } })
-})
-```
-
-**Only exception:** Singleton modules that cache state at module scope (e.g., Redis clients, connection pools). These genuinely need `vi.resetModules()` + dynamic import to get a fresh instance per test.
-
-### NEVER use `vi.importActual()`
-
-This defeats the purpose of mocking by loading the real module and all its dependencies.
-
-```typescript
-// BAD — loads real module + all transitive deps
-vi.mock('@/lib/workspaces/utils', async () => {
-  const actual = await vi.importActual('@/lib/workspaces/utils')
-  return { ...actual, myFn: vi.fn() }
-})
-
-// GOOD — mock everything, only implement what tests need
-vi.mock('@/lib/workspaces/utils', () => ({
-  myFn: vi.fn(),
-  otherFn: vi.fn(),
-}))
-```
-
-### Mock heavy transitive dependencies
-
-If a module under test imports `@/blocks` (200+ files), `@/tools/registry`, or other heavy modules, mock them:
-
-```typescript
-vi.mock('@/blocks', () => ({
-  getBlock: () => null,
-  getAllBlocks: () => ({}),
-  getAllBlockTypes: () => [],
-  registry: {},
-}))
-```
-
-### Use `@vitest-environment node` unless DOM is needed
-
-Only use `@vitest-environment jsdom` if the test uses `window`, `document`, `FormData`, or other browser APIs. Node environment is significantly faster.
-
-### Avoid real timers in tests
-
-```typescript
-// BAD
-await new Promise(r => setTimeout(r, 500))
-
-// GOOD — use minimal delays or fake timers
-await new Promise(r => setTimeout(r, 1))
-// or
-vi.useFakeTimers()
-```
-
-## Centralized Mocks (prefer over local declarations)
-
-`@sim/testing` exports ready-to-use mock modules for common dependencies. Import and pass directly to `vi.mock()` — no `vi.hoisted()` boilerplate needed. Each paired `*MockFns` object exposes the underlying `vi.fn()`s for per-test overrides.
-
-| Module mocked | Import | Factory form |
-|---|---|---|
-| `@/app/api/auth/oauth/utils` | `authOAuthUtilsMock`, `authOAuthUtilsMockFns` | `vi.mock('@/app/api/auth/oauth/utils', () => authOAuthUtilsMock)` |
-| `@/app/api/knowledge/utils` | `knowledgeApiUtilsMock`, `knowledgeApiUtilsMockFns` | `vi.mock('@/app/api/knowledge/utils', () => knowledgeApiUtilsMock)` |
-| `@/app/api/workflows/utils` | `workflowsApiUtilsMock`, `workflowsApiUtilsMockFns` | `vi.mock('@/app/api/workflows/utils', () => workflowsApiUtilsMock)` |
-| `@/lib/audit/log` | `auditMock`, `auditMockFns` | `vi.mock('@/lib/audit/log', () => auditMock)` |
-| `@/lib/auth` | `authMock`, `authMockFns` | `vi.mock('@/lib/auth', () => authMock)` |
-| `@/lib/auth/hybrid` | `hybridAuthMock`, `hybridAuthMockFns` | `vi.mock('@/lib/auth/hybrid', () => hybridAuthMock)` |
-| `@/lib/copilot/request/http` | `copilotHttpMock`, `copilotHttpMockFns` | `vi.mock('@/lib/copilot/request/http', () => copilotHttpMock)` |
-| `@/lib/core/config/env` | `envMock`, `createEnvMock(overrides)` | `vi.mock('@/lib/core/config/env', () => envMock)` |
-| `@/lib/core/config/feature-flags` | `featureFlagsMock` | `vi.mock('@/lib/core/config/feature-flags', () => featureFlagsMock)` |
-| `@/lib/core/config/redis` | `redisConfigMock`, `redisConfigMockFns` | `vi.mock('@/lib/core/config/redis', () => redisConfigMock)` |
-| `@/lib/core/security/encryption` | `encryptionMock`, `encryptionMockFns` | `vi.mock('@/lib/core/security/encryption', () => encryptionMock)` |
-| `@/lib/core/security/input-validation.server` | `inputValidationMock`, `inputValidationMockFns` | `vi.mock('@/lib/core/security/input-validation.server', () => inputValidationMock)` |
-| `@/lib/core/utils/request` | `requestUtilsMock`, `requestUtilsMockFns` | `vi.mock('@/lib/core/utils/request', () => requestUtilsMock)` |
-| `@/lib/core/utils/urls` | `urlsMock`, `urlsMockFns` | `vi.mock('@/lib/core/utils/urls', () => urlsMock)` |
-| `@/lib/execution/preprocessing` | `executionPreprocessingMock`, `executionPreprocessingMockFns` | `vi.mock('@/lib/execution/preprocessing', () => executionPreprocessingMock)` |
-| `@/lib/logs/execution/logging-session` | `loggingSessionMock`, `loggingSessionMockFns`, `LoggingSessionMock` | `vi.mock('@/lib/logs/execution/logging-session', () => loggingSessionMock)` |
-| `@/lib/workflows/orchestration` | `workflowsOrchestrationMock`, `workflowsOrchestrationMockFns` | `vi.mock('@/lib/workflows/orchestration', () => workflowsOrchestrationMock)` |
-| `@/lib/workflows/persistence/utils` | `workflowsPersistenceUtilsMock`, `workflowsPersistenceUtilsMockFns` | `vi.mock('@/lib/workflows/persistence/utils', () => workflowsPersistenceUtilsMock)` |
-| `@/lib/workflows/utils` | `workflowsUtilsMock`, `workflowsUtilsMockFns` | `vi.mock('@/lib/workflows/utils', () => workflowsUtilsMock)` |
-| `@/lib/workspaces/permissions/utils` | `permissionsMock`, `permissionsMockFns` | `vi.mock('@/lib/workspaces/permissions/utils', () => permissionsMock)` |
-| `@sim/db/schema` | `schemaMock` | `vi.mock('@sim/db/schema', () => schemaMock)` |
-
-### Auth mocking (API routes)
-
-```typescript
-import { authMock, authMockFns } from '@sim/testing'
-import { beforeEach, describe, expect, it, vi } from 'vitest'
-
-vi.mock('@/lib/auth', () => authMock)
-
-import { GET } from '@/app/api/my-route/route'
-
-beforeEach(() => {
-  vi.clearAllMocks()
-  authMockFns.mockGetSession.mockResolvedValue({ user: { id: 'user-1' } })
-})
-```
-
-Only define a local `vi.mock('@/lib/auth', ...)` if the module under test consumes exports outside the centralized shape (e.g., `auth.api.verifyOneTimeToken`, `auth.api.resetPassword`).
-
-### Hybrid auth mocking
-
-```typescript
-import { hybridAuthMock, hybridAuthMockFns } from '@sim/testing'
-
-vi.mock('@/lib/auth/hybrid', () => hybridAuthMock)
-
-// In tests:
-hybridAuthMockFns.mockCheckSessionOrInternalAuth.mockResolvedValue({
-  success: true, userId: 'user-1', authType: 'session',
-})
-```
-
-### Database chain mocking
-
-```typescript
-const { mockSelect, mockFrom, mockWhere } = vi.hoisted(() => ({
-  mockSelect: vi.fn(),
-  mockFrom: vi.fn(),
-  mockWhere: vi.fn(),
-}))
-
-vi.mock('@sim/db', () => ({
-  db: { select: mockSelect },
-}))
-
-beforeEach(() => {
-  mockSelect.mockReturnValue({ from: mockFrom })
-  mockFrom.mockReturnValue({ where: mockWhere })
-  mockWhere.mockResolvedValue([{ id: '1', name: 'test' }])
-})
-```
-
-## @sim/testing Package
-
-Always prefer over local test data.
-
-| Category | Utilities |
-|----------|-----------|
-| **Module mocks** | See "Centralized Mocks" table above |
-| **Logger helpers** | `loggerMock`, `createMockLogger()`, `getLoggerCalls()`, `clearLoggerMocks()` |
-| **Database helpers** | `databaseMock`, `drizzleOrmMock`, `createMockDb()`, `createMockSql()`, `createMockSqlOperators()` |
-| **Fetch helpers** | `setupGlobalFetchMock()`, `createMockFetch()`, `createMockResponse()`, `mockFetchError()` |
-| **Factories** | `createSession()`, `createWorkflowRecord()`, `createBlock()`, `createExecutionContext()` |
-| **Builders** | `WorkflowBuilder`, `ExecutionContextBuilder` |
-| **Assertions** | `expectWorkflowAccessGranted()`, `expectBlockExecuted()` |
-| **Requests** | `createMockRequest()`, `createMockFormDataRequest()` |
-
-## Rules Summary
-
-1. `@vitest-environment node` unless DOM is required
-2. Prefer centralized mocks from `@sim/testing` (see table above) over local `vi.hoisted()` + `vi.mock()` boilerplate
-3. `vi.hoisted()` + `vi.mock()` + static imports — never `vi.resetModules()` + `vi.doMock()` + dynamic imports
-4. `vi.mock()` calls before importing mocked modules
-5. `beforeEach(() => vi.clearAllMocks())` to reset state — no redundant `afterEach`
-6. No `vi.importActual()` — mock everything explicitly
-7. Mock heavy deps (`@/blocks`, `@/tools/registry`, `@/triggers`) in tests that don't need them
-8. Use absolute imports in test files
-9. Avoid real timers — use 1ms delays or `vi.useFakeTimers()`

.cursor/rules/sim-typescript.mdc

@@ -1,20 +0,0 @@
----
-description: TypeScript conventions and type safety
-globs: ["apps/sim/**/*.ts", "apps/sim/**/*.tsx"]
----
-
-# TypeScript Rules
-
-1. **No `any`** - Use proper types or `unknown` with type guards
-2. **Props interface** - Always define for components
-3. **Const assertions** - `as const` for constant objects/arrays
-4. **Ref types** - Explicit: `useRef<HTMLDivElement>(null)`
-5. **Type imports** - `import type { X }` for type-only imports
-
-```typescript
-// ✗ Bad
-const handleClick = (e: any) => {}
-
-// ✓ Good
-const handleClick = (e: React.MouseEvent<HTMLButtonElement>) => {}
-```

.cursor/skills/add-hosted-key/SKILL.md

@@ -1,296 +0,0 @@
----
-name: add-hosted-key
-description: Add hosted API key support to a tool so Sim provides the key when users don't bring their own. Use when adding hosted keys, BYOK support, hideWhenHosted, or hosted key pricing to a tool or block.
----
-
-# Adding Hosted Key Support to a Tool
-
-When a tool has hosted key support, Sim provides its own API key if the user hasn't configured one (via BYOK or env var). Usage is metered and billed to the workspace.
-
-## Overview
-
-| Step | What | Where |
-|------|------|-------|
-| 1 | Register BYOK provider ID | `tools/types.ts`, `app/api/workspaces/[id]/byok-keys/route.ts` |
-| 2 | Research the API's pricing and rate limits | API docs / pricing page (before writing any code) |
-| 3 | Add `hosting` config to the tool | `tools/{service}/{action}.ts` |
-| 4 | Hide API key field when hosted | `blocks/blocks/{service}.ts` |
-| 5 | Add to BYOK settings UI | BYOK settings component (`byok.tsx`) |
-| 6 | Summarize pricing and throttling comparison | Output to user (after all code changes) |
-
-## Step 1: Register the BYOK Provider ID
-
-Add the new provider to the `BYOKProviderId` union in `tools/types.ts`:
-
-```typescript
-export type BYOKProviderId =
-  | 'openai'
-  | 'anthropic'
-  // ...existing providers
-  | 'your_service'
-```
-
-Then add it to `VALID_PROVIDERS` in `app/api/workspaces/[id]/byok-keys/route.ts`:
-
-```typescript
-const VALID_PROVIDERS = ['openai', 'anthropic', 'google', 'mistral', 'your_service'] as const
-```
-
-## Step 2: Research the API's Pricing Model and Rate Limits
-
-**Before writing any `getCost` or `rateLimit` code**, look up the service's official documentation for both pricing and rate limits. You need to understand:
-
-### Pricing
-
-1. **How the API charges** — per request, per credit, per token, per step, per minute, etc.
-2. **Whether the API reports cost in its response** — look for fields like `creditsUsed`, `costDollars`, `tokensUsed`, or similar in the response body or headers
-3. **Whether cost varies by endpoint/options** — some APIs charge more for certain features (e.g., Firecrawl charges 1 credit/page base but +4 for JSON format, +4 for enhanced mode)
-4. **The dollar-per-unit rate** — what each credit/token/unit costs in dollars on our plan
-
-### Rate Limits
-
-1. **What rate limits the API enforces** — requests per minute/second, tokens per minute, concurrent requests, etc.
-2. **Whether limits vary by plan tier** — free vs paid vs enterprise often have different ceilings
-3. **Whether limits are per-key or per-account** — determines whether adding more hosted keys actually increases total throughput
-4. **What the API returns when rate limited** — HTTP 429, `Retry-After` header, error body format, etc.
-5. **Whether there are multiple dimensions** — some APIs limit both requests/min AND tokens/min independently
-
-Search the API's docs/pricing page (use WebSearch/WebFetch). Capture the pricing model as a comment in `getCost` so future maintainers know the source of truth.
-
-### Setting Our Rate Limits
-
-Our rate limiter (`lib/core/rate-limiter/hosted-key/`) uses a token-bucket algorithm applied **per billing actor** (workspace). It supports two modes:
-
-- **`per_request`** — simple; just `requestsPerMinute`. Good when the API charges flat per-request or cost doesn't vary much.
-- **`custom`** — `requestsPerMinute` plus additional `dimensions` (e.g., `tokens`, `search_units`). Each dimension has its own `limitPerMinute` and an `extractUsage` function that reads actual usage from the response. Use when the API charges on a variable metric (tokens, credits) and you want to cap that metric too.
-
-When choosing values for `requestsPerMinute` and any dimension limits:
-
-- **Stay well below the API's per-key limit** — our keys are shared across all workspaces. If the API allows 60 RPM per key and we have 3 keys, the global ceiling is ~180 RPM. Set the per-workspace limit low enough (e.g., 20-60 RPM) that many workspaces can coexist without collectively hitting the API's ceiling.
-- **Account for key pooling** — our round-robin distributes requests across `N` hosted keys, so the effective API-side rate per key is `(total requests) / N`. But per-workspace limits are enforced *before* key selection, so they apply regardless of key count.
-- **Prefer conservative defaults** — it's easy to raise limits later but hard to claw back after users depend on high throughput.
-
-## Step 3: Add `hosting` Config to the Tool
-
-Add a `hosting` object to the tool's `ToolConfig`. This tells the execution layer how to acquire hosted keys, calculate cost, and rate-limit.
-
-```typescript
-hosting: {
-  envKeyPrefix: 'YOUR_SERVICE_API_KEY',
-  apiKeyParam: 'apiKey',
-  byokProviderId: 'your_service',
-  pricing: {
-    type: 'custom',
-    getCost: (_params, output) => {
-      if (output.creditsUsed == null) {
-        throw new Error('Response missing creditsUsed field')
-      }
-      const creditsUsed = output.creditsUsed as number
-      const cost = creditsUsed * 0.001 // dollars per credit
-      return { cost, metadata: { creditsUsed } }
-    },
-  },
-  rateLimit: {
-    mode: 'per_request',
-    requestsPerMinute: 100,
-  },
-},
-```
-
-### Hosted Key Env Var Convention
-
-Keys use a numbered naming pattern driven by a count env var:
-
-```
-YOUR_SERVICE_API_KEY_COUNT=3
-YOUR_SERVICE_API_KEY_1=sk-...
-YOUR_SERVICE_API_KEY_2=sk-...
-YOUR_SERVICE_API_KEY_3=sk-...
-```
-
-The `envKeyPrefix` value (`YOUR_SERVICE_API_KEY`) determines which env vars are read at runtime. Adding more keys only requires bumping the count and adding the new env var.
-
-### Pricing: Prefer API-Reported Cost
-
-Always prefer using cost data returned by the API (e.g., `creditsUsed`, `costDollars`). This is the most accurate because it accounts for variable pricing tiers, feature modifiers, and plan-level discounts.
-
-**When the API reports cost** — use it directly and throw if missing:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (output.creditsUsed == null) {
-      throw new Error('Response missing creditsUsed field')
-    }
-    // $0.001 per credit — from https://example.com/pricing
-    const cost = (output.creditsUsed as number) * 0.001
-    return { cost, metadata: { creditsUsed: output.creditsUsed } }
-  },
-},
-```
-
-**When the API does NOT report cost** — compute it from params/output based on the pricing docs, but still validate the data you depend on:
-
-```typescript
-pricing: {
-  type: 'custom',
-  getCost: (params, output) => {
-    if (!Array.isArray(output.searchResults)) {
-      throw new Error('Response missing searchResults, cannot determine cost')
-    }
-    // Serper: 1 credit for <=10 results, 2 credits for >10 — from https://serper.dev/pricing
-    const credits = Number(params.num) > 10 ? 2 : 1
-    return { cost: credits * 0.001, metadata: { credits } }
-  },
-},
-```
-
-**`getCost` must always throw** if it cannot determine cost. Never silently fall back to a default — this would hide billing inaccuracies.
-
-### Capturing Cost Data from the API
-
-If the API returns cost info, capture it in `transformResponse` so `getCost` can read it from the output:
-
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      results: data.results,
-      creditsUsed: data.creditsUsed,  // pass through for getCost
-    },
-  }
-},
-```
-
-For async/polling tools, capture it in `postProcess` when the job completes:
-
-```typescript
-if (jobData.status === 'completed') {
-  result.output = {
-    data: jobData.data,
-    creditsUsed: jobData.creditsUsed,
-  }
-}
-```
-
-## Step 4: Hide the API Key Field When Hosted
-
-In the block config (`blocks/blocks/{service}.ts`), add `hideWhenHosted: true` to the API key subblock. This hides the field on hosted Sim since the platform provides the key:
-
-```typescript
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-},
-```
-
-The visibility is controlled by `isSubBlockHidden()` in `lib/workflows/subblocks/visibility.ts`, which checks both the `isHosted` feature flag (`hideWhenHosted`) and optional env var conditions (`hideWhenEnvSet`).
-
-### Excluding Specific Operations from Hosted Key Support
-
-When a block has multiple operations but some operations should **not** use a hosted key (e.g., the underlying API is deprecated, unsupported, or too expensive), use the **duplicate apiKey subblock** pattern. This is the same pattern Exa uses for its `research` operation:
-
-1. **Remove the `hosting` config** from the tool definition for that operation — it must not have a `hosting` object at all.
-2. **Duplicate the `apiKey` subblock** in the block config with opposing conditions:
-
-```typescript
-// API Key — hidden when hosted for operations with hosted key support
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  hideWhenHosted: true,
-  condition: { field: 'operation', value: 'unsupported_op', not: true },
-},
-// API Key — always visible for unsupported_op (no hosted key support)
-{
-  id: 'apiKey',
-  title: 'API Key',
-  type: 'short-input',
-  placeholder: 'Enter your API key',
-  password: true,
-  required: true,
-  condition: { field: 'operation', value: 'unsupported_op' },
-},
-```
-
-Both subblocks share the same `id: 'apiKey'`, so the same value flows to the tool. The conditions ensure only one is visible at a time. The first has `hideWhenHosted: true` and shows for all hosted operations; the second has no `hideWhenHosted` and shows only for the excluded operation — meaning users must always provide their own key for that operation.
-
-To exclude multiple operations, use an array: `{ field: 'operation', value: ['op_a', 'op_b'] }`.
-
-**Reference implementations:**
-- **Exa** (`blocks/blocks/exa.ts`): `research` operation excluded from hosting — lines 309-329
-- **Google Maps** (`blocks/blocks/google_maps.ts`): `speed_limits` operation excluded from hosting (deprecated Roads API)
-
-## Step 5: Add to the BYOK Settings UI
-
-Add an entry to the `PROVIDERS` array in the BYOK settings component so users can bring their own key. You need the service icon from `components/icons.tsx`:
-
-```typescript
-{
-  id: 'your_service',
-  name: 'Your Service',
-  icon: YourServiceIcon,
-  description: 'What this service does',
-  placeholder: 'Enter your API key',
-},
-```
-
-## Step 6: Summarize Pricing and Throttling Comparison
-
-After all code changes are complete, output a detailed summary to the user covering:
-
-### What to include
-
-1. **API's pricing model** — how the service charges (per token, per credit, per request, etc.), the specific rates found in docs, and whether the API reports cost in responses.
-2. **Our `getCost` approach** — how we calculate cost, what fields we depend on, and any assumptions or estimates (especially when the API doesn't report exact dollar cost).
-3. **API's rate limits** — the documented limits (RPM, TPM, concurrent, etc.), which plan tier they apply to, and whether they're per-key or per-account.
-4. **Our `rateLimit` config** — what we set for `requestsPerMinute` (and dimensions if custom mode), why we chose those values, and how they compare to the API's limits.
-5. **Key pooling impact** — how many hosted keys we expect, and how round-robin distribution affects the effective per-key rate at the API.
-6. **Gaps or risks** — anything the API charges for that we don't meter, rate limit dimensions we chose not to enforce, or pricing that may be inaccurate due to variable model/tier costs.
-
-### Format
-
-Present this as a structured summary with clear headings. Example:
-
-```
-### Pricing
-- **API charges**: $X per 1M tokens (input), $Y per 1M tokens (output) — varies by model
-- **Response reports cost?**: No — only token counts in `usage` field
-- **Our getCost**: Estimates cost at $Z per 1M total tokens based on median model pricing
-- **Risk**: Actual cost varies by model; our estimate may over/undercharge for cheap/expensive models
-
-### Throttling
-- **API limits**: 300 RPM per key (paid tier), 60 RPM (free tier)
-- **Per-key or per-account**: Per key — more keys = more throughput
-- **Our config**: 60 RPM per workspace (per_request mode)
-- **With N keys**: Effective per-key rate is (total RPM across workspaces) / N
-- **Headroom**: Comfortable — even 10 active workspaces at full rate = 600 RPM / 3 keys = 200 RPM per key, under the 300 RPM API limit
-```
-
-This summary helps reviewers verify that the pricing and rate limiting are well-calibrated and surfaces any risks that need monitoring.
-
-## Checklist
-
-- [ ] Provider added to `BYOKProviderId` in `tools/types.ts`
-- [ ] Provider added to `VALID_PROVIDERS` in the BYOK keys API route
-- [ ] API pricing docs researched — understand per-unit cost and whether the API reports cost in responses
-- [ ] API rate limits researched — understand RPM/TPM limits, per-key vs per-account, and plan tiers
-- [ ] `hosting` config added to the tool with `envKeyPrefix`, `apiKeyParam`, `byokProviderId`, `pricing`, and `rateLimit`
-- [ ] `getCost` throws if required cost data is missing from the response
-- [ ] Cost data captured in `transformResponse` or `postProcess` if API provides it
-- [ ] `hideWhenHosted: true` added to the API key subblock in the block config
-- [ ] Provider entry added to the BYOK settings UI with icon and description
-- [ ] Env vars documented: `{PREFIX}_COUNT` and `{PREFIX}_1..N`
-- [ ] Pricing and throttling summary provided to reviewer

.devcontainer/.bashrc

@@ -0,0 +1,69 @@
+# Sim Studio Development Environment Bashrc
+# This gets sourced by post-create.sh
+
+# Enhanced prompt with git branch info
+parse_git_branch() {
+  git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/'
+}
+
+export PS1="\[\033[01;32m\]\u@simstudio\[\033[00m\]:\[\033[01;34m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\]\$ "
+
+# Helpful aliases
+alias ll="ls -la"
+alias ..="cd .."
+alias ...="cd ../.."
+
+# Database aliases
+alias pgc="PGPASSWORD=postgres psql -h db -U postgres -d simstudio"
+alias check-db="PGPASSWORD=postgres psql -h db -U postgres -c '\l'"
+
+# Sim Studio specific aliases
+alias logs="cd /workspace/apps/sim && tail -f logs/*.log 2>/dev/null || echo 'No log files found'"
+alias sim-start="cd /workspace && bun run dev"
+alias sim-migrate="cd /workspace/apps/sim && bunx drizzle-kit push"
+alias sim-generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
+alias sim-rebuild="cd /workspace && bun run build && bun run start"
+alias docs-dev="cd /workspace/apps/docs && bun run dev"
+
+# Turbo related commands
+alias turbo-build="cd /workspace && bunx turbo run build"
+alias turbo-dev="cd /workspace && bunx turbo run dev"
+alias turbo-test="cd /workspace && bunx turbo run test"
+
+# Bun specific commands
+alias bun-update="cd /workspace && bun update"
+alias bun-add="cd /workspace && bun add"
+alias bun-pm="cd /workspace && bun pm"
+alias bun-canary="bun upgrade --canary"
+
+# Default to workspace directory
+cd /workspace 2>/dev/null || true
+
+# Welcome message - only show once per session
+if [ -z "$SIM_WELCOME_SHOWN" ]; then
+  export SIM_WELCOME_SHOWN=1
+  
+  echo ""
+  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+  echo "🚀 Welcome to Sim Studio development environment!"
+  echo ""
+  echo "Available commands:"
+  echo "  sim-start    - Start all apps in development mode"
+  echo "  sim-migrate  - Push schema changes to the database for sim app"
+  echo "  sim-generate - Generate new migrations for sim app"
+  echo "  sim-rebuild  - Build and start all apps"
+  echo "  docs-dev     - Start only the docs app in development mode"
+  echo ""
+  echo "Turbo commands:"
+  echo "  turbo-build  - Build all apps using Turborepo"
+  echo "  turbo-dev    - Start development mode for all apps"
+  echo "  turbo-test   - Run tests for all packages"
+  echo ""
+  echo "Bun commands:"
+  echo "  bun-update   - Update dependencies"
+  echo "  bun-add      - Add a new dependency"
+  echo "  bun-pm       - Manage dependencies"
+  echo "  bun-canary   - Upgrade to the latest canary version of Bun"
+  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+  echo ""
+fi 

.devcontainer/Dockerfile

@@ -1,43 +1,38 @@
-FROM oven/bun:1.3.11-alpine
+# Use the latest Bun canary image for development
+FROM oven/bun:canary
+
+# Avoid warnings by switching to noninteractive
+ENV DEBIAN_FRONTEND=noninteractive
 
 # Install necessary packages for development
-RUN apk add --no-cache \
-    git \
-    curl \
-    wget \
-    jq \
-    sudo \
-    postgresql-client \
-    vim \
-    nano \
-    bash \
-    bash-completion \
-    zsh \
-    zsh-vcs \
-    ca-certificates \
-    shadow
+RUN apt-get update \
+    && apt-get -y install --no-install-recommends \
+       git curl wget jq sudo postgresql-client vim nano \
+       bash-completion ca-certificates lsb-release gnupg \
+    && apt-get clean -y \
+    && rm -rf /var/lib/apt/lists/*
 
-# Create a non-root user with matching UID/GID
+# Create a non-root user
 ARG USERNAME=bun
 ARG USER_UID=1000
 ARG USER_GID=$USER_UID
 
-# Create user group if it doesn't exist
-RUN if ! getent group $USER_GID >/dev/null; then \
-        addgroup -g $USER_GID $USERNAME; \
-    fi
-
-# Create user if it doesn't exist
-RUN if ! getent passwd $USER_UID >/dev/null; then \
-        adduser -D -u $USER_UID -G $(getent group $USER_GID | cut -d: -f1) $USERNAME; \
-    fi
-
 # Add sudo support
 RUN echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME \
     && chmod 0440 /etc/sudoers.d/$USERNAME
 
+# Install global packages for development
+RUN bun install -g turbo drizzle-kit typescript @types/node
+
+# Install bun completions
+RUN bun completions > /etc/bash_completion.d/bun
+
 # Set up shell environment
-RUN echo "export PATH=\$PATH:/home/$USERNAME/.bun/bin" >> /etc/profile
+RUN echo "export PATH=$PATH:/home/$USERNAME/.bun/bin" >> /etc/profile
+RUN echo "source /etc/profile" >> /etc/bash.bashrc
+
+# Switch back to dialog for any ad-hoc use of apt-get
+ENV DEBIAN_FRONTEND=dialog
 
 WORKDIR /workspace
 

.devcontainer/README.md

@@ -1,75 +1,78 @@
-# Sim Development Container
+# Sim Studio Development Container
 
-Development container configuration for VS Code Dev Containers and GitHub Codespaces.
+This directory contains configuration files for Visual Studio Code Dev Containers / GitHub Codespaces. Dev containers provide a consistent, isolated development environment for this project.
 
-## Prerequisites
+## Contents
+
+- `devcontainer.json` - The main configuration file that defines the development container settings
+- `Dockerfile` - Defines the container image and development environment
+- `docker-compose.yml` - Sets up the application and database containers
+- `post-create.sh` - Script that runs when the container is created
+- `.bashrc` - Custom shell configuration with helpful aliases
+
+## Usage
+
+### Prerequisites
 
 - Visual Studio Code
-- Docker Desktop or Podman Desktop
-- VS Code Dev Containers extension
+- Docker installation:
+  - Docker Desktop (Windows/macOS)
+  - Docker Engine (Linux)
+- VS Code Remote - Containers extension
 
-## Getting Started
+### Getting Started
 
-1. Open this project in VS Code
-2. Click "Reopen in Container" when prompted (or press `F1` → "Dev Containers: Reopen in Container")
+1. Open this project in Visual Studio Code
+2. When prompted, click "Reopen in Container"
+   - Alternatively, press `F1` and select "Remote-Containers: Reopen in Container"
 3. Wait for the container to build and initialize
-4. Start developing with `sim-start`
+4. The post-creation script will automatically:
 
-The setup script will automatically install dependencies and run migrations.
+   - Install dependencies
+   - Set up environment variables
+   - Run database migrations
+   - Configure helpful aliases
 
-## Development Commands
+5. Start the application with `sim-start` (alias for `bun run dev`)
 
-### Running Services
+### Development Commands
 
-You have two options for running the development environment:
-
-**Option 1: Run everything together (recommended for most development)**
-```bash
-sim-start  # Runs both app and socket server using concurrently
-```
-
-**Option 2: Run services separately (useful for debugging individual services)**
-- In the **app** container terminal: `sim-app` (starts Next.js app on port 3000)
-- In the **realtime** container terminal: `sim-sockets` (starts socket server on port 3002)
-
-### Other Commands
+The development environment includes these helpful aliases:
 
+- `sim-start` - Start the development server
 - `sim-migrate` - Push schema changes to the database
 - `sim-generate` - Generate new migrations
-- `build` - Build the application
-- `pgc` - Connect to PostgreSQL database
+- `sim-rebuild` - Build and start the production version
+- `pgc` - Connect to the PostgreSQL database
+- `check-db` - List all databases
+
+### Using GitHub Codespaces
+
+This project is also configured for GitHub Codespaces. To use it:
+
+1. Go to the GitHub repository
+2. Click the "Code" button
+3. Select the "Codespaces" tab
+4. Click "Create codespace on main"
+
+This will start a new Codespace with the development environment already set up.
+
+## Customization
+
+You can customize the development environment by:
+
+- Modifying `devcontainer.json` to add VS Code extensions or settings
+- Updating the `Dockerfile` to install additional packages
+- Editing `docker-compose.yml` to add services or change configuration
+- Modifying `.bashrc` to add custom aliases or configurations
 
 ## Troubleshooting
 
-**Build errors**: Rebuild the container with `F1` → "Dev Containers: Rebuild Container"
+If you encounter issues:
 
-**Port conflicts**: Ensure ports 3000, 3002, and 5432 are available
+1. Rebuild the container: `F1` → "Remote-Containers: Rebuild Container"
+2. Check Docker logs for build errors
+3. Verify Docker Desktop is running
+4. Ensure all prerequisites are installed
 
-**Container runtime issues**: Verify Docker Desktop or Podman Desktop is running
-
-## Technical Details
-
-Services:
-- **App container** (8GB memory limit) - Main Next.js application
-- **Realtime container** (4GB memory limit) - Socket.io server for real-time features
-- **Database** - PostgreSQL with pgvector extension
-- **Migrations** - Runs automatically on container creation
-
-You can develop with services running together or independently.
-
-### Personalization
-
-**Project commands** (`sim-start`, `sim-app`, etc.) are automatically available via `/workspace/.devcontainer/sim-commands.sh`.
-
-**Personal shell customization** (aliases, prompts, etc.) should use VS Code's dotfiles feature:
-1. Create a dotfiles repository (e.g., `github.com/youruser/dotfiles`)
-2. Add your `.bashrc`, `.zshrc`, or other configs
-3. Configure in VS Code Settings:
-   ```json
-   {
-     "dotfiles.repository": "youruser/dotfiles",
-     "dotfiles.installCommand": "install.sh"
-   }
-   ```
-
-This separates project-specific commands from personal preferences, following VS Code best practices.
+For more information, see the [VS Code Remote Development documentation](https://code.visualstudio.com/docs/remote/containers).

.devcontainer/devcontainer.json

@@ -1,5 +1,5 @@
 {
-  "name": "Sim Dev Environment",
+  "name": "Sim Studio Dev Environment",
   "dockerComposeFile": "docker-compose.yml",
   "service": "app",
   "workspaceFolder": "/workspace",
@@ -13,6 +13,13 @@
           "source.fixAll.biome": "explicit",
           "source.organizeImports.biome": "explicit"
         },
+        "terminal.integrated.defaultProfile.linux": "bash",
+        "terminal.integrated.profiles.linux": {
+          "bash": {
+            "path": "/bin/bash",
+            "args": ["--login"]
+          }
+        },
         "terminal.integrated.shellIntegration.enabled": true
       },
       "extensions": [
@@ -29,9 +36,18 @@
     }
   },
 
-  "forwardPorts": [3000, 3002, 5432],
+  "forwardPorts": [3000, 5432],
 
   "postCreateCommand": "bash -c 'bash .devcontainer/post-create.sh || true'",
 
-  "remoteUser": "bun"
+  "postStartCommand": "bash -c 'if [ ! -f ~/.bashrc ] || ! grep -q \"sim-start\" ~/.bashrc; then cp .devcontainer/.bashrc ~/.bashrc; fi'",
+
+  "remoteUser": "bun",
+
+  "features": {
+    "ghcr.io/devcontainers/features/git:1": {},
+    "ghcr.io/prulloac/devcontainer-features/bun:1": {
+      "version": "latest"
+    }
+  }
 }

.devcontainer/docker-compose.yml

@@ -7,56 +7,53 @@ services:
       - ..:/workspace:cached
       - bun-cache:/home/bun/.bun/cache:delegated
     command: sleep infinity
-    deploy:
-      resources:
-        limits:
-          memory: 8G
     environment:
       - NODE_ENV=development
       - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
+      - POSTGRES_URL=postgresql://postgres:postgres@db:5432/simstudio
       - BETTER_AUTH_URL=http://localhost:3000
       - NEXT_PUBLIC_APP_URL=http://localhost:3000
-      - BETTER_AUTH_SECRET=${BETTER_AUTH_SECRET:-your_auth_secret_here}
-      - ENCRYPTION_KEY=${ENCRYPTION_KEY:-your_encryption_key_here}
-      - COPILOT_API_KEY=${COPILOT_API_KEY}
-      - SIM_AGENT_API_URL=${SIM_AGENT_API_URL}
-      - OLLAMA_URL=${OLLAMA_URL:-http://localhost:11434}
-      - NEXT_PUBLIC_SOCKET_URL=${NEXT_PUBLIC_SOCKET_URL:-http://localhost:3002}
       - BUN_INSTALL_CACHE_DIR=/home/bun/.bun/cache
     depends_on:
       db:
         condition: service_healthy
+      realtime:
+        condition: service_healthy
       migrations:
         condition: service_completed_successfully
     ports:
       - "3000:3000"
       - "3001:3001"
     working_dir: /workspace
+    healthcheck:
+      test: ['CMD', 'wget', '--spider', '--quiet', 'http://127.0.0.1:3000']
+      interval: 90s
+      timeout: 5s
+      retries: 3
+      start_period: 10s
 
   realtime:
     build:
       context: ..
       dockerfile: .devcontainer/Dockerfile
-    volumes:
-      - ..:/workspace:cached
-      - bun-cache:/home/bun/.bun/cache:delegated
     command: sleep infinity
-    deploy:
-      resources:
-        limits:
-          memory: 1G
     environment:
       - NODE_ENV=development
       - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
       - BETTER_AUTH_URL=http://localhost:3000
       - NEXT_PUBLIC_APP_URL=http://localhost:3000
-      - BETTER_AUTH_SECRET=${BETTER_AUTH_SECRET:-your_auth_secret_here}
     depends_on:
       db:
         condition: service_healthy
     ports:
       - "3002:3002"
     working_dir: /workspace
+    healthcheck:
+      test: ['CMD', 'wget', '--spider', '--quiet', 'http://127.0.0.1:3002']
+      interval: 90s
+      timeout: 5s
+      retries: 3
+      start_period: 10s
 
   migrations:
     build:
@@ -80,7 +77,7 @@ services:
       - POSTGRES_PASSWORD=postgres
       - POSTGRES_DB=simstudio
     ports:
-      - "${POSTGRES_PORT:-5432}:5432"
+      - "5432:5432"
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U postgres"]
       interval: 5s

.devcontainer/post-create.sh

@@ -3,48 +3,16 @@
 # Exit on error, but with some error handling
 set -e
 
-echo "🔧 Setting up Sim development environment..."
+echo "🔧 Setting up Sim Studio development environment..."
 
 # Change to the workspace root directory
 cd /workspace
 
-# Install global packages for development (done at runtime, not build time)
-echo "📦 Installing global development tools..."
-bun install -g turbo drizzle-kit typescript @types/node 2>/dev/null || {
-  echo "⚠️ Some global packages may already be installed, continuing..."
-}
-
-# Set up bun completions (with proper shell detection)
-echo "🔧 Setting up shell completions..."
-if [ -n "$SHELL" ] && [ -f "$SHELL" ]; then
-  SHELL=/bin/bash bun completions 2>/dev/null | sudo tee /etc/bash_completion.d/bun > /dev/null || {
-    echo "⚠️ Could not install bun completions, but continuing..."
-  }
-fi
-
-# Add project commands to shell profile
-echo "📄 Setting up project commands..."
-# Add sourcing of sim-commands.sh to user's shell config files if they exist
-for rcfile in ~/.bashrc ~/.zshrc; do
-  if [ -f "$rcfile" ]; then
-    # Check if already added
-    if ! grep -q "sim-commands.sh" "$rcfile"; then
-      echo "" >> "$rcfile"
-      echo "# Sim project commands" >> "$rcfile"
-      echo "if [ -f /workspace/.devcontainer/sim-commands.sh ]; then" >> "$rcfile"
-      echo "  source /workspace/.devcontainer/sim-commands.sh" >> "$rcfile"
-      echo "fi" >> "$rcfile"
-    fi
-  fi
-done
-
-# If no rc files exist yet, create a minimal one
-if [ ! -f ~/.bashrc ] && [ ! -f ~/.zshrc ]; then
-  echo "# Source Sim project commands" > ~/.bashrc
-  echo "if [ -f /workspace/.devcontainer/sim-commands.sh ]; then" >> ~/.bashrc
-  echo "  source /workspace/.devcontainer/sim-commands.sh" >> ~/.bashrc
-  echo "fi" >> ~/.bashrc
-fi
+# Setup .bashrc
+echo "📄 Setting up .bashrc with aliases..."
+cp /workspace/.devcontainer/.bashrc ~/.bashrc
+# Add to .profile to ensure .bashrc is sourced in non-interactive shells
+echo 'if [ -f ~/.bashrc ]; then . ~/.bashrc; fi' >> ~/.profile
 
 # Clean and reinstall dependencies to ensure platform compatibility
 echo "📦 Cleaning and reinstalling dependencies..."
@@ -61,12 +29,18 @@ chmod 700 ~/.bun ~/.bun/cache
 
 # Install dependencies with platform-specific binaries
 echo "Installing dependencies with Bun..."
-bun install
+bun install || {
+  echo "⚠️ bun install had issues but continuing setup..."
+}
 
 # Check for native dependencies
 echo "Checking for native dependencies compatibility..."
-if grep -q '"trustedDependencies"' apps/sim/package.json 2>/dev/null; then
-  echo "⚠️ Native dependencies detected. Bun will handle compatibility during install."
+NATIVE_DEPS=$(grep '"trustedDependencies"' apps/sim/package.json || echo "")
+if [ ! -z "$NATIVE_DEPS" ]; then
+  echo "⚠️ Native dependencies detected. Ensuring compatibility with Bun..."
+  for pkg in $(echo $NATIVE_DEPS | grep -oP '"[^"]*"' | tr -d '"' | grep -v "trustedDependencies"); do
+    echo "Checking compatibility for $pkg..."
+  done
 fi
 
 # Set up environment variables if .env doesn't exist for the sim app
@@ -108,12 +82,29 @@ echo "Waiting for database to be ready..."
   fi
 ) || echo "⚠️ Database setup had issues but continuing..."
 
+# Add additional helpful aliases to .bashrc
+cat << EOF >> ~/.bashrc
+
+# Additional Sim Studio Development Aliases
+alias migrate="cd /workspace/apps/sim && DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio bunx drizzle-kit push"
+alias generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
+alias dev="cd /workspace && bun run dev"
+alias build="cd /workspace && bun run build"
+alias start="cd /workspace && bun run dev"
+alias lint="cd /workspace/apps/sim && bun run lint"
+alias test="cd /workspace && bun run test"
+alias bun-update="cd /workspace && bun update"
+EOF
+
+# Source the .bashrc to make aliases available immediately
+. ~/.bashrc
+
 # Clear the welcome message flag to ensure it shows after setup
 unset SIM_WELCOME_SHOWN
 
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "✅ Sim development environment setup complete!"
+echo "✅ Sim Studio development environment setup complete!"
 echo ""
 echo "Your environment is now ready. A new terminal session will show"
 echo "available commands. You can start the development server with:"

.devcontainer/sim-commands.sh

@@ -1,42 +0,0 @@
-#!/bin/bash
-# Sim Project Commands
-# Source this file to add project-specific commands to your shell
-# Add to your ~/.bashrc or ~/.zshrc: source /workspace/.devcontainer/sim-commands.sh
-
-# Project-specific aliases for Sim development
-alias sim-start="cd /workspace && bun run dev:full"
-alias sim-app="cd /workspace && bun run dev"
-alias sim-sockets="cd /workspace && bun run dev:sockets"
-alias sim-migrate="cd /workspace/apps/sim && bunx drizzle-kit push"
-alias sim-generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
-alias sim-rebuild="cd /workspace && bun run build && bun run start"
-alias docs-dev="cd /workspace/apps/docs && bun run dev"
-
-# Database connection helpers
-alias pgc="PGPASSWORD=postgres psql -h db -U postgres -d simstudio"
-alias check-db="PGPASSWORD=postgres psql -h db -U postgres -c '\l'"
-
-# Default to workspace directory
-cd /workspace 2>/dev/null || true
-
-# Welcome message - show once per session
-if [ -z "$SIM_WELCOME_SHOWN" ]; then
-  export SIM_WELCOME_SHOWN=1
-
-  echo ""
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "🚀 Sim Development Environment"
-  echo ""
-  echo "Project commands:"
-  echo "  sim-start      - Start app + socket server"
-  echo "  sim-app        - Start only main app"
-  echo "  sim-sockets    - Start only socket server"
-  echo "  sim-migrate    - Push schema changes"
-  echo "  sim-generate   - Generate migrations"
-  echo ""
-  echo "Database:"
-  echo "  pgc            - Connect to PostgreSQL"
-  echo "  check-db       - List databases"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-fi

.dockerignore

@@ -1,67 +1,11 @@
-# Git
-.git
-.gitignore
-
-# Documentation
 LICENSE
 NOTICE
-README.md
-*.md
-docs/
-
-# IDE and editor
-.vscode
-.idea
-*.swp
-*.swo
-
-# Environment and config
-.env*
-!.env.example
 .prettierrc
 .prettierignore
-.eslintrc*
-.eslintignore
-
-# CI/CD and DevOps
+README.md
+.gitignore
+.husky
 .github
 .devcontainer
-.husky
-docker-compose*.yml
-Dockerfile*
-
-# Build artifacts and caches
-.next
-.turbo
-.cache
-dist
-build
-out
-coverage
-*.log
-
-# Dependencies (will be installed fresh in container)
-node_modules
-.bun
-
-# Test files
-**/*.test.ts
-**/*.test.tsx
-**/*.spec.ts
-**/*.spec.tsx
-__tests__
-__mocks__
-jest.config.*
-vitest.config.*
-
-# TypeScript build info
-*.tsbuildinfo
-
-# OS files
-.DS_Store
-Thumbs.db
-
-# Temporary files
-tmp
-temp
-*.tmp
+.env.example
+node_modules

.gitattributes

@@ -1,34 +0,0 @@
-# Set default behavior to automatically normalize line endings
-* text=auto eol=lf
-
-# Explicitly declare text files you want to always be normalized and converted
-# to native line endings on checkout
-*.ts text eol=lf
-*.tsx text eol=lf
-*.js text eol=lf
-*.jsx text eol=lf
-*.json text eol=lf
-*.md text eol=lf
-*.yml text eol=lf
-*.yaml text eol=lf
-*.toml text eol=lf
-*.css text eol=lf
-*.scss text eol=lf
-*.sh text eol=lf
-*.bash text eol=lf
-Dockerfile* text eol=lf
-.dockerignore text eol=lf
-.gitignore text eol=lf
-.gitattributes text eol=lf
-
-# Denote all files that are truly binary and should not be modified
-*.png binary
-*.jpg binary
-*.jpeg binary
-*.gif binary
-*.ico binary
-*.woff binary
-*.woff2 binary
-*.ttf binary
-*.eot binary
-*.pdf binary

.github/CODEOWNERS

@@ -1,28 +0,0 @@
-# Copilot/Mothership chat streaming entrypoints and replay surfaces.
-/apps/sim/app/api/copilot/chat/ @simstudioai/mothership
-/apps/sim/app/api/copilot/confirm/ @simstudioai/mothership
-/apps/sim/app/api/copilot/chats/ @simstudioai/mothership
-/apps/sim/app/api/mothership/chat/ @simstudioai/mothership
-/apps/sim/app/api/mothership/chats/ @simstudioai/mothership
-/apps/sim/app/api/mothership/execute/ @simstudioai/mothership
-/apps/sim/app/api/v1/copilot/chat/ @simstudioai/mothership
-
-# Server-side stream orchestration, persistence, and protocol.
-/apps/sim/lib/copilot/chat/ @simstudioai/mothership
-/apps/sim/lib/copilot/async-runs/ @simstudioai/mothership
-/apps/sim/lib/copilot/request/ @simstudioai/mothership
-/apps/sim/lib/copilot/generated/ @simstudioai/mothership
-/apps/sim/lib/copilot/constants.ts @simstudioai/mothership
-/apps/sim/lib/core/utils/sse.ts @simstudioai/mothership
-
-# Stream-time tool execution, confirmations, resource persistence, and handlers.
-/apps/sim/lib/copilot/tool-executor/ @simstudioai/mothership
-/apps/sim/lib/copilot/tools/ @simstudioai/mothership
-/apps/sim/lib/copilot/persistence/ @simstudioai/mothership
-/apps/sim/lib/copilot/resources/ @simstudioai/mothership
-
-# Client-side stream consumption, hydration, and reconnect.
-/apps/sim/app/workspace/*/home/hooks/index.ts @simstudioai/mothership
-/apps/sim/app/workspace/*/home/hooks/use-chat.ts @simstudioai/mothership
-/apps/sim/app/workspace/*/home/hooks/use-file-preview-sessions.ts @simstudioai/mothership
-/apps/sim/hooks/queries/tasks.ts @simstudioai/mothership

.github/CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# Code of Conduct - Sim
+# Code of Conduct - Sim Studio
 
 ## Our Pledge
 
@@ -55,7 +55,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behaviour may be
-reported to the community leaders responsible for enforcement at <waleed@sim.ai>.
+reported to the community leaders responsible for enforcement at <waleed@simstudio.ai>.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

.github/CONTRIBUTING.md

@@ -1,9 +1,9 @@
-# Contributing to Sim
+# Contributing to Sim Studio
 
-Thank you for your interest in contributing to Sim! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
+Thank you for your interest in contributing to Sim Studio! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
 
 > **Project Overview:**  
-> Sim is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
+> Sim Studio is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
 
 ---
 
@@ -15,6 +15,8 @@ Thank you for your interest in contributing to Sim! Our goal is to provide devel
 - [Commit Message Guidelines](#commit-message-guidelines)
 - [Local Development Setup](#local-development-setup)
 - [Adding New Blocks and Tools](#adding-new-blocks-and-tools)
+- [Local Storage Mode](#local-storage-mode)
+- [Standalone Build](#standalone-build)
 - [License](#license)
 - [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 
@@ -55,7 +57,7 @@ We strive to keep our workflow as simple as possible. To contribute:
    ```
 
 7. **Create a Pull Request**  
-   Open a pull request against the `staging` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
+   Open a pull request against the `main` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
 
 ---
 
@@ -83,7 +85,7 @@ If you discover a bug or have a feature request, please open an issue in our Git
 Before creating a pull request:
 
 - **Ensure Your Branch Is Up-to-Date:**  
-  Rebase your branch onto the latest `staging` branch to prevent merge conflicts.
+  Rebase your branch onto the latest `main` branch to prevent merge conflicts.
 - **Follow the Guidelines:**  
   Make sure your changes are well-tested, follow our coding standards, and include relevant documentation if necessary.
 
@@ -130,7 +132,7 @@ To set up your local development environment:
 
 ### Option 1: Using NPM Package (Simplest)
 
-The easiest way to run Sim locally is using our NPM package:
+The easiest way to run Sim Studio locally is using our NPM package:
 
 ```bash
 npx simstudio
@@ -140,7 +142,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim on (default: 3000)
+- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
 - `--no-pull`: Skip pulling the latest Docker images
 
 #### Requirements
@@ -154,7 +156,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 git clone https://github.com/<your-username>/sim.git
 cd sim
 
-# Start Sim
+# Start Sim Studio
 docker compose -f docker-compose.prod.yml up -d
 ```
 
@@ -162,19 +164,15 @@ Access the application at [http://localhost:3000/](http://localhost:3000/)
 
 #### Using Local Models
 
-To use local models with Sim:
+To use local models with Sim Studio:
 
-1. Install Ollama and pull models:
+1. Pull models using our helper script:
 
 ```bash
-# Install Ollama (if not already installed)
-curl -fsSL https://ollama.ai/install.sh | sh
-
-# Pull a model (e.g., gemma3:4b)
-ollama pull gemma3:4b
+./apps/sim/scripts/ollama_docker.sh pull <model_name>
 ```
 
-2. Start Sim with local model support:
+2. Start Sim Studio with local model support:
 
 ```bash
 # With NVIDIA GPU support
@@ -211,14 +209,13 @@ Dev Containers provide a consistent and easy-to-use development environment:
 
 3. **Start Developing:**
 
-   - Run `bun run dev:full` in the terminal or use the `sim-start` alias
-   - This starts both the main application and the realtime socket server
+   - Run `bun run dev` in the terminal or use the `sim-start` alias
    - All dependencies and configurations are automatically set up
    - Your changes will be automatically hot-reloaded
 
 4. **GitHub Codespaces:**
    - This setup also works with GitHub Codespaces if you prefer development in the browser
-   - Just click "Code" → "Codespaces" → "Create codespace on staging"
+   - Just click "Code" → "Codespaces" → "Create codespace on main"
 
 ### Option 4: Manual Setup
 
@@ -249,11 +246,9 @@ If you prefer not to use Docker or Dev Containers:
 4. **Run the Development Server:**
 
    ```bash
-   bun run dev:full
+   bun run dev
    ```
 
-   This command starts both the main application and the realtime socket server required for full functionality.
-
 5. **Make Your Changes and Test Locally.**
 
 ### Email Template Development
@@ -280,7 +275,7 @@ When working on email templates, you can preview them using a local email previe
 
 ## Adding New Blocks and Tools
 
-Sim is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
+Sim Studio is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
 
 ### Where to Add Your Code
 
@@ -305,8 +300,8 @@ In addition, you will need to update the registries:
 
    ```typescript:/apps/sim/blocks/blocks/pinecone.ts
    import { PineconeIcon } from '@/components/icons'
-   import type { BlockConfig } from '@/blocks/types'
-   import type { PineconeResponse } from '@/tools/pinecone/types'
+   import { PineconeResponse } from '@/tools/pinecone/types'
+   import { BlockConfig } from '../types'
 
    export const PineconeBlock: BlockConfig<PineconeResponse> = {
      type: 'pinecone',
@@ -317,56 +312,13 @@ In addition, you will need to update the registries:
      bgColor: '#123456',
      icon: PineconeIcon,
 
+     // If this block requires OAuth authentication
+     provider: 'pinecone',
+
+     // Define subBlocks for the UI configuration
      subBlocks: [
-       {
-         id: 'operation',
-         title: 'Operation',
-         type: 'dropdown'
-         required: true,
-         options: [
-           { label: 'Generate Embeddings', id: 'generate' },
-           { label: 'Search Text', id: 'search_text' },
-         ],
-         value: () => 'generate',
-       },
-       {
-         id: 'apiKey',
-         title: 'API Key',
-         type: 'short-input'
-         placeholder: 'Your Pinecone API key',
-         password: true,
-         required: true,
-       },
+       // Block configuration options
      ],
-
-     tools: {
-       access: ['pinecone_generate_embeddings', 'pinecone_search_text'],
-       config: {
-         tool: (params: Record<string, any>) => {
-           switch (params.operation) {
-             case 'generate':
-               return 'pinecone_generate_embeddings'
-             case 'search_text':
-               return 'pinecone_search_text'
-             default:
-               throw new Error('Invalid operation selected')
-           }
-         },
-       },
-     },
-
-     inputs: {
-       operation: { type: 'string', description: 'Operation to perform' },
-       apiKey: { type: 'string', description: 'Pinecone API key' },
-       searchQuery: { type: 'string', description: 'Search query text' },
-       topK: { type: 'string', description: 'Number of results to return' },
-     },
-
-     outputs: {
-       matches: { type: 'any', description: 'Search results or generated embeddings' },
-       data: { type: 'any', description: 'Response data from Pinecone' },
-       usage: { type: 'any', description: 'API usage statistics' },
-     },
    }
    ```
 
@@ -374,7 +326,7 @@ In addition, you will need to update the registries:
    Add your block to the blocks registry (`/apps/sim/blocks/registry.ts`):
 
    ```typescript:/apps/sim/blocks/registry.ts
-   import { PineconeBlock } from '@/blocks/blocks/pinecone'
+   import { PineconeBlock } from './blocks/pinecone'
 
    // Registry of all available blocks
    export const registry: Record<string, BlockConfig> = {
@@ -414,8 +366,8 @@ In addition, you will need to update the registries:
    Your tool should export a constant with a naming convention of `{toolName}Tool`. The tool ID should follow the format `{provider}_{tool_name}`. For example:
 
    ```typescript:/apps/sim/tools/pinecone/fetch.ts
-   import { ToolConfig, ToolResponse } from '@/tools/types'
-   import { PineconeParams, PineconeResponse } from '@/tools/pinecone/types'
+   import { ToolConfig, ToolResponse } from '../types'
+   import { PineconeParams, PineconeResponse } from './types'
 
    export const fetchTool: ToolConfig<PineconeParams, PineconeResponse> = {
      id: 'pinecone_fetch', // Follow the {provider}_{tool_name} format
@@ -427,18 +379,7 @@ In addition, you will need to update the registries:
      provider: 'pinecone', // ID of the OAuth provider
 
      params: {
-       parameterName: {
-         type: 'string',
-         required: true,
-         visibility: 'user-or-llm', // Controls parameter visibility
-         description: 'Description of the parameter',
-       },
-       optionalParam: {
-         type: 'string',
-         required: false,
-         visibility: 'user-only',
-         description: 'Optional parameter only user can set',
-       },
+       // Tool parameters
      },
      request: {
        // Request configuration
@@ -446,6 +387,9 @@ In addition, you will need to update the registries:
      transformResponse: async (response: Response) => {
        // Transform response
      },
+     transformError: (error) => {
+       // Handle errors
+     },
    }
    ```
 
@@ -453,7 +397,7 @@ In addition, you will need to update the registries:
    Update the tools registry in `/apps/sim/tools/index.ts` to include your new tool:
 
    ```typescript:/apps/sim/tools/index.ts
-   import { fetchTool, generateEmbeddingsTool, searchTextTool } from '/@tools/pinecone'
+   import { fetchTool, generateEmbeddingsTool, searchTextTool } from './pinecone'
    // ... other imports
 
    export const tools: Record<string, ToolConfig> = {
@@ -485,57 +429,11 @@ Maintaining consistent naming across the codebase is critical for auto-generatio
 - **Tool Exports:** Should be named `{toolName}Tool` (e.g., `fetchTool`)
 - **Tool IDs:** Should follow the format `{provider}_{tool_name}` (e.g., `pinecone_fetch`)
 
-### Parameter Visibility System
-
-Sim implements a sophisticated parameter visibility system that controls how parameters are exposed to users and LLMs in agent workflows. Each parameter can have one of four visibility levels:
-
-| Visibility  | User Sees | LLM Sees | How It Gets Set                |
-|-------------|-----------|----------|--------------------------------|
-| `user-only` | ✅ Yes     | ❌ No     | User provides in UI            |
-| `user-or-llm` | ✅ Yes     | ✅ Yes    | User provides OR LLM generates |
-| `llm-only`  | ❌ No      | ✅ Yes    | LLM generates only             |
-| `hidden`    | ❌ No      | ❌ No     | Application injects at runtime |
-
-#### Visibility Guidelines
-
-- **`user-or-llm`**: Use for core parameters that can be provided by users or intelligently filled by the LLM (e.g., search queries, email subjects)
-- **`user-only`**: Use for configuration parameters, API keys, and settings that only users should control (e.g., number of results, authentication credentials)
-- **`llm-only`**: Use for computed values that the LLM should handle internally (e.g., dynamic calculations, contextual data)
-- **`hidden`**: Use for system-level parameters injected at runtime (e.g., OAuth tokens, internal identifiers)
-
-#### Example Implementation
-
-```typescript
-params: {
-  query: {
-    type: 'string',
-    required: true,
-    visibility: 'user-or-llm', // User can provide or LLM can generate
-    description: 'Search query to execute',
-  },
-  apiKey: {
-    type: 'string',
-    required: true,
-    visibility: 'user-only', // Only user provides this
-    description: 'API key for authentication',
-  },
-  internalId: {
-    type: 'string',
-    required: false,
-    visibility: 'hidden', // System provides this at runtime
-    description: 'Internal tracking identifier',
-  },
-}
-```
-
-This visibility system ensures clean user interfaces while maintaining full flexibility for LLM-driven workflows.
-
 ### Guidelines & Best Practices
 
-- **Code Style:** Follow the project's Biome configurations. Use meaningful variable names and small, focused functions.
+- **Code Style:** Follow the project's ESLint and Prettier configurations. Use meaningful variable names and small, focused functions.
 - **Documentation:** Clearly document the purpose, inputs, outputs, and any special behavior for your block/tool.
 - **Error Handling:** Implement robust error handling and provide user-friendly error messages.
-- **Parameter Visibility:** Always specify the appropriate visibility level for each parameter to ensure proper UI behavior and LLM integration.
 - **Testing:** Add unit or integration tests to verify your changes when possible.
 - **Commit Changes:** Update all related components and registries, and describe your changes in your pull request.
 
@@ -553,7 +451,7 @@ This project is licensed under the Apache License 2.0. By contributing, you agre
 
 By contributing to this repository, you agree that your contributions are provided under the terms of the Apache License Version 2.0, as included in the LICENSE file of this repository.
 
-In addition, by submitting your contributions, you grant Sim, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
+In addition, by submitting your contributions, you grant Sim Studio, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
 
 - Use, copy, modify, distribute, publicly display, publicly perform, and prepare derivative works of your contributions.
 - Incorporate your contributions into other works or products.
@@ -565,4 +463,4 @@ If you do not agree with these terms, you must not contribute your work to this
 
 ---
 
-Thank you for taking the time to contribute to Sim. We truly appreciate your efforts and look forward to collaborating with you!
+Thank you for taking the time to contribute to Sim Studio. We truly appreciate your efforts and look forward to collaborating with you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,42 @@
-## Summary
-Brief description of what this PR does and why.
+## Description
 
-Fixes #(issue)
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
 
-## Type of Change
-- [ ] Bug fix
-- [ ] New feature  
-- [ ] Breaking change
-- [ ] Documentation
-- [ ] Other: ___________
+Fixes # (issue)
 
-## Testing
-How has this been tested? What should reviewers focus on?
+## Type of change
 
-## Checklist
-- [ ] Code follows project style guidelines
-- [ ] Self-reviewed my changes
-- [ ] Tests added/updated and passing
-- [ ] No new warnings introduced
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Security enhancement
+- [ ] Performance improvement
+- [ ] Code refactoring (no functional changes)
+
+## How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] All tests pass locally and in CI (`bun run test`)
+- [ ] My changes generate no new warnings
+- [ ] Any dependent changes have been merged and published in downstream modules
+- [ ] I have updated version numbers as needed (if needed)
 - [ ] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
 
-## Screenshots/Videos
-<!-- If applicable, add screenshots or videos to help explain your changes -->
-<!-- For UI changes, before/after screenshots are especially helpful -->
+## Security Considerations:
+
+- [ ] My changes do not introduce any new security vulnerabilities
+- [ ] I have considered the security implications of my changes
+
+## Additional Information:
+
+Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.

.github/SECURITY.md

@@ -8,11 +8,11 @@
 
 ## Reporting a Vulnerability
 
-We take the security of Sim seriously. If you believe you've found a security vulnerability, please follow these steps:
+We take the security of Sim Studio seriously. If you believe you've found a security vulnerability, please follow these steps:
 
 1. **Do not disclose the vulnerability publicly** or to any third parties.
 
-2. **Email us directly** at security@sim.ai with details of the vulnerability.
+2. **Email us directly** at security@simstudio.ai with details of the vulnerability.
 
 3. **Include the following information** in your report: