Upload folder using huggingface_hub

data/tasks/cb-001.yaml

@@ -0,0 +1,55 @@
+id: cb-001
+title: "List open issues in a GitHub repo"
+difficulty: easy
+category: project_mgmt
+description: |
+  List all currently open issues in the repository "acme-corp/web-platform".
+  Display the issue number, title, and assignee for each.
+tools_provided:
+  - gh
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 42
+            title: "Fix login redirect loop"
+            state: open
+            assignee: alice
+            labels: ["bug", "auth"]
+          - number: 43
+            title: "Add dark mode support"
+            state: open
+            assignee: bob
+            labels: ["enhancement", "ui"]
+          - number: 44
+            title: "Update README with API docs"
+            state: closed
+            assignee: carol
+            labels: ["docs"]
+          - number: 45
+            title: "Memory leak in websocket handler"
+            state: open
+            assignee: null
+            labels: ["bug", "critical"]
+          - number: 46
+            title: "Migrate to Node 20"
+            state: open
+            assignee: dave
+            labels: ["chore"]
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh issue list.*--repo acme-corp/web-platform.*--state open"
+    output_contains:
+      - "42"
+      - "43"
+      - "45"
+      - "46"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-002.yaml

@@ -0,0 +1,37 @@
+id: cb-002
+title: "Create a GitHub issue with title and body"
+difficulty: easy
+category: project_mgmt
+description: |
+  Create a new issue in the repository "acme-corp/web-platform" with the title
+  "Add rate limiting to public API endpoints" and a body that describes the need
+  to prevent abuse on unauthenticated API routes.
+tools_provided:
+  - gh
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 50
+            title: "Existing issue"
+            state: open
+            assignee: alice
+            labels: []
+expected_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - title: "Add rate limiting to public API endpoints"
+            state: open
+            body_contains: "rate limit"
+    command_history:
+      - pattern: "gh issue create.*--repo acme-corp/web-platform.*--title"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-003.yaml

@@ -0,0 +1,53 @@
+id: cb-003
+title: "List channels in Slack workspace"
+difficulty: easy
+category: communication
+description: |
+  List all public channels in the Slack workspace. Show the channel name,
+  member count, and topic for each channel.
+tools_provided:
+  - slack
+initial_state:
+  slack:
+    channels:
+      - id: C001
+        name: general
+        is_private: false
+        num_members: 45
+        topic: "Company-wide announcements"
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        topic: "Engineering discussions"
+      - id: C003
+        name: design-team
+        is_private: true
+        num_members: 8
+        topic: "Design reviews"
+      - id: C004
+        name: random
+        is_private: false
+        num_members: 40
+        topic: "Non-work banter"
+      - id: C005
+        name: incidents
+        is_private: false
+        num_members: 15
+        topic: "Production incident coordination"
+expected_state:
+  slack:
+    command_history:
+      - pattern: "slack channel list"
+    output_contains:
+      - "general"
+      - "engineering"
+      - "random"
+      - "incidents"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-004.yaml

@@ -0,0 +1,39 @@
+id: cb-004
+title: "Send a message to a Slack channel"
+difficulty: easy
+category: communication
+description: |
+  Send the message "Deployment v2.3.1 completed successfully. All health checks passing."
+  to the #engineering channel in Slack.
+tools_provided:
+  - slack
+initial_state:
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        topic: "Engineering discussions"
+        messages: []
+      - id: C001
+        name: general
+        is_private: false
+        num_members: 45
+        topic: "Company-wide announcements"
+        messages: []
+expected_state:
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "Deployment v2.3.1 completed successfully"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-005.yaml

@@ -0,0 +1,57 @@
+id: cb-005
+title: "List issues assigned to a specific user in Linear"
+difficulty: easy
+category: project_mgmt
+description: |
+  List all issues in Linear that are currently assigned to the user "sarah@acme.com".
+  Show the issue identifier, title, status, and priority.
+tools_provided:
+  - linear
+initial_state:
+  linear:
+    issues:
+      - id: ACM-101
+        title: "Implement OAuth2 PKCE flow"
+        status: in_progress
+        priority: high
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-102
+        title: "Database migration script"
+        status: todo
+        priority: medium
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-103
+        title: "Update CI pipeline"
+        status: in_progress
+        priority: low
+        assignee: mark@acme.com
+        team: Platform
+      - id: ACM-104
+        title: "Add Sentry error tracking"
+        status: backlog
+        priority: high
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-105
+        title: "Refactor user service"
+        status: done
+        priority: medium
+        assignee: mark@acme.com
+        team: Platform
+expected_state:
+  linear:
+    command_history:
+      - pattern: "linear issue list.*--assignee.*sarah"
+    output_contains:
+      - "ACM-101"
+      - "ACM-102"
+      - "ACM-104"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-006.yaml

@@ -0,0 +1,41 @@
+id: cb-006
+title: "Create a Linear issue with priority"
+difficulty: easy
+category: project_mgmt
+description: |
+  Create a new issue in the Linear team "Platform" with the title
+  "Implement webhook retry logic with exponential backoff", set the priority
+  to "urgent", and assign it to "sarah@acme.com".
+tools_provided:
+  - linear
+initial_state:
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+        members:
+          - sarah@acme.com
+          - mark@acme.com
+    issues:
+      - id: ACM-110
+        title: "Existing backlog item"
+        status: backlog
+        priority: low
+        assignee: mark@acme.com
+        team: Platform
+expected_state:
+  linear:
+    issues:
+      - title: "Implement webhook retry logic with exponential backoff"
+        priority: urgent
+        assignee: sarah@acme.com
+        team: Platform
+    command_history:
+      - pattern: "linear issue create.*--team.*Platform.*--priority.*urgent"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-007.yaml

@@ -0,0 +1,48 @@
+id: cb-007
+title: "Search for Slack messages containing a keyword"
+difficulty: easy
+category: communication
+description: |
+  Search the Slack workspace for all messages containing the keyword "outage"
+  from the last 7 days. Display the channel, sender, timestamp, and message text.
+tools_provided:
+  - slack
+initial_state:
+  slack:
+    channels:
+      - id: C005
+        name: incidents
+        messages:
+          - user: ops-bot
+            text: "ALERT: Database outage detected in us-east-1"
+            ts: "2026-03-10T14:30:00Z"
+          - user: alice
+            text: "Investigating the outage — looks like connection pool exhaustion"
+            ts: "2026-03-10T14:35:00Z"
+          - user: bob
+            text: "Restarting the affected pods now"
+            ts: "2026-03-10T14:40:00Z"
+      - id: C002
+        name: engineering
+        messages:
+          - user: carol
+            text: "FYI the outage yesterday was caused by a bad migration"
+            ts: "2026-03-11T09:00:00Z"
+          - user: dave
+            text: "PR #234 is ready for review"
+            ts: "2026-03-11T10:00:00Z"
+expected_state:
+  slack:
+    command_history:
+      - pattern: "slack message search.*outage"
+    output_contains:
+      - "outage"
+      - "incidents"
+      - "engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-008.yaml

@@ -0,0 +1,42 @@
+id: cb-008
+title: "View a specific GitHub issue by number"
+difficulty: easy
+category: project_mgmt
+description: |
+  View the full details of issue #42 in the repository "acme-corp/web-platform",
+  including its title, body, labels, assignee, and comments.
+tools_provided:
+  - gh
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 42
+            title: "Fix login redirect loop"
+            state: open
+            assignee: alice
+            labels: ["bug", "auth"]
+            body: |
+              Users are experiencing an infinite redirect loop when logging in
+              with SSO. The issue occurs after the OAuth callback redirects back
+              to the application. Browser console shows ERR_TOO_MANY_REDIRECTS.
+            comments:
+              - user: bob
+                body: "I can reproduce this on Chrome 120 with SSO provider Okta."
+              - user: alice
+                body: "Found the root cause — the session cookie domain is misconfigured."
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh issue view 42.*--repo acme-corp/web-platform"
+    output_contains:
+      - "Fix login redirect loop"
+      - "redirect"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-009.yaml

@@ -0,0 +1,48 @@
+id: cb-009
+title: "List projects in Linear"
+difficulty: easy
+category: project_mgmt
+description: |
+  List all projects in the Linear workspace. Show the project name, status,
+  lead, and target date for each project.
+tools_provided:
+  - linear
+initial_state:
+  linear:
+    projects:
+      - name: "Q1 Platform Migration"
+        status: in_progress
+        lead: sarah@acme.com
+        target_date: "2026-03-31"
+        teams: ["Platform"]
+      - name: "Mobile App v3"
+        status: in_progress
+        lead: mark@acme.com
+        target_date: "2026-04-15"
+        teams: ["Mobile"]
+      - name: "Security Audit Remediation"
+        status: planned
+        lead: alice@acme.com
+        target_date: "2026-05-01"
+        teams: ["Platform", "Security"]
+      - name: "Design System 2.0"
+        status: completed
+        lead: carol@acme.com
+        target_date: "2026-02-28"
+        teams: ["Design", "Frontend"]
+expected_state:
+  linear:
+    command_history:
+      - pattern: "linear project list"
+    output_contains:
+      - "Q1 Platform Migration"
+      - "Mobile App v3"
+      - "Security Audit Remediation"
+      - "Design System 2.0"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-010.yaml

@@ -0,0 +1,41 @@
+id: cb-010
+title: "Send a DM to a user on Slack"
+difficulty: easy
+category: communication
+description: |
+  Send a direct message to the Slack user "alice" with the text:
+  "Hey Alice, can you review PR #234 when you get a chance? It's the auth fix we discussed."
+tools_provided:
+  - slack
+initial_state:
+  slack:
+    users:
+      - id: U001
+        name: alice
+        real_name: "Alice Chen"
+        status: active
+      - id: U002
+        name: bob
+        real_name: "Bob Smith"
+        status: active
+      - id: U003
+        name: carol
+        real_name: "Carol Davis"
+        status: away
+    direct_messages:
+      alice: []
+      bob: []
+expected_state:
+  slack:
+    direct_messages:
+      alice:
+        - text_contains: "review PR #234"
+    command_history:
+      - pattern: "slack message send.*--user.*alice"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-011.yaml

@@ -0,0 +1,48 @@
+id: cb-011
+title: "Add a label to a GitHub issue"
+difficulty: easy
+category: project_mgmt
+description: |
+  Add the label "priority:high" to issue #45 in the repository
+  "acme-corp/web-platform". The issue is about a memory leak in the
+  websocket handler.
+tools_provided:
+  - gh
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        labels:
+          - name: "priority:high"
+            color: "ff0000"
+          - name: "priority:low"
+            color: "00ff00"
+          - name: "bug"
+            color: "d73a4a"
+        issues:
+          - number: 45
+            title: "Memory leak in websocket handler"
+            state: open
+            assignee: null
+            labels: ["bug"]
+          - number: 46
+            title: "Migrate to Node 20"
+            state: open
+            assignee: dave
+            labels: ["chore"]
+expected_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 45
+            labels: ["bug", "priority:high"]
+    command_history:
+      - pattern: "gh issue edit 45.*--add-label.*priority:high"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-012.yaml

@@ -0,0 +1,44 @@
+id: cb-012
+title: "Update a Linear issue status to done"
+difficulty: easy
+category: project_mgmt
+description: |
+  Update the Linear issue "ACM-101" (Implement OAuth2 PKCE flow) to mark
+  its status as "done". The implementation has been completed and merged.
+tools_provided:
+  - linear
+initial_state:
+  linear:
+    issues:
+      - id: ACM-101
+        title: "Implement OAuth2 PKCE flow"
+        status: in_progress
+        priority: high
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-102
+        title: "Database migration script"
+        status: todo
+        priority: medium
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-103
+        title: "Update CI pipeline"
+        status: in_progress
+        priority: low
+        assignee: mark@acme.com
+        team: Platform
+expected_state:
+  linear:
+    issues:
+      - id: ACM-101
+        status: done
+    command_history:
+      - pattern: "linear issue update ACM-101.*--status.*done"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-013.yaml

@@ -0,0 +1,54 @@
+id: cb-013
+title: "List Notion pages"
+difficulty: easy
+category: data_ops
+description: |
+  List all pages in the Notion workspace. Show the page title, last edited time,
+  and parent database or page for each entry.
+tools_provided:
+  - notion
+initial_state:
+  notion:
+    pages:
+      - id: pg-001
+        title: "Engineering Runbook"
+        last_edited: "2026-03-10T16:00:00Z"
+        parent: "Engineering Wiki"
+        created_by: alice
+      - id: pg-002
+        title: "Q1 OKRs"
+        last_edited: "2026-03-08T10:00:00Z"
+        parent: "Company Goals"
+        created_by: ceo
+      - id: pg-003
+        title: "Onboarding Checklist"
+        last_edited: "2026-02-20T14:00:00Z"
+        parent: "HR"
+        created_by: carol
+      - id: pg-004
+        title: "Incident Post-Mortem Template"
+        last_edited: "2026-03-11T09:00:00Z"
+        parent: "Engineering Wiki"
+        created_by: bob
+      - id: pg-005
+        title: "API Design Guidelines"
+        last_edited: "2026-03-05T11:00:00Z"
+        parent: "Engineering Wiki"
+        created_by: sarah
+expected_state:
+  notion:
+    command_history:
+      - pattern: "notion page list"
+    output_contains:
+      - "Engineering Runbook"
+      - "Q1 OKRs"
+      - "Onboarding Checklist"
+      - "Incident Post-Mortem Template"
+      - "API Design Guidelines"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-014.yaml

@@ -0,0 +1,41 @@
+id: cb-014
+title: "Create a Notion page"
+difficulty: easy
+category: data_ops
+description: |
+  Create a new Notion page under the "Engineering Wiki" parent with the title
+  "Redis Caching Strategy". The page content should describe a caching approach
+  for the user service with TTL policies.
+tools_provided:
+  - notion
+initial_state:
+  notion:
+    pages:
+      - id: pg-001
+        title: "Engineering Runbook"
+        last_edited: "2026-03-10T16:00:00Z"
+        parent: "Engineering Wiki"
+        created_by: alice
+      - id: pg-004
+        title: "Incident Post-Mortem Template"
+        last_edited: "2026-03-11T09:00:00Z"
+        parent: "Engineering Wiki"
+        created_by: bob
+    databases:
+      - id: db-001
+        title: "Engineering Wiki"
+expected_state:
+  notion:
+    pages:
+      - title: "Redis Caching Strategy"
+        parent: "Engineering Wiki"
+        content_contains: "caching"
+    command_history:
+      - pattern: "notion page create.*--parent.*Engineering Wiki.*--title.*Redis Caching Strategy"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-015.yaml

@@ -0,0 +1,57 @@
+id: cb-015
+title: "List Jira issues in a project"
+difficulty: easy
+category: project_mgmt
+description: |
+  List all issues in the Jira project "INFRA" (Infrastructure). Show the issue
+  key, summary, status, assignee, and priority for each issue.
+tools_provided:
+  - jira
+initial_state:
+  jira:
+    projects:
+      - key: INFRA
+        name: "Infrastructure"
+        issues:
+          - key: INFRA-201
+            summary: "Upgrade Kubernetes to 1.29"
+            status: "In Progress"
+            assignee: ops-alice
+            priority: High
+          - key: INFRA-202
+            summary: "Set up Prometheus alerting rules"
+            status: "To Do"
+            assignee: ops-bob
+            priority: Medium
+          - key: INFRA-203
+            summary: "Migrate RDS from db.m5 to db.m6i"
+            status: "To Do"
+            assignee: null
+            priority: High
+          - key: INFRA-204
+            summary: "Configure CloudFront cache invalidation"
+            status: "Done"
+            assignee: ops-alice
+            priority: Low
+          - key: INFRA-205
+            summary: "Implement VPC peering for staging"
+            status: "In Progress"
+            assignee: ops-carol
+            priority: Medium
+expected_state:
+  jira:
+    command_history:
+      - pattern: "jira issue list.*--project.*INFRA"
+    output_contains:
+      - "INFRA-201"
+      - "INFRA-202"
+      - "INFRA-203"
+      - "INFRA-204"
+      - "INFRA-205"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-016.yaml

@@ -0,0 +1,43 @@
+id: cb-016
+title: "Create a Jira issue"
+difficulty: easy
+category: project_mgmt
+description: |
+  Create a new Jira issue in the "INFRA" project with summary "Set up
+  centralized log aggregation with Loki", type "Task", priority "High",
+  and assign it to "ops-bob".
+tools_provided:
+  - jira
+initial_state:
+  jira:
+    projects:
+      - key: INFRA
+        name: "Infrastructure"
+        members:
+          - ops-alice
+          - ops-bob
+          - ops-carol
+        issues:
+          - key: INFRA-205
+            summary: "Implement VPC peering for staging"
+            status: "In Progress"
+            assignee: ops-carol
+            priority: Medium
+expected_state:
+  jira:
+    projects:
+      - key: INFRA
+        issues:
+          - summary: "Set up centralized log aggregation with Loki"
+            type: Task
+            priority: High
+            assignee: ops-bob
+    command_history:
+      - pattern: "jira issue create.*--project.*INFRA.*--summary"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-017.yaml

@@ -0,0 +1,52 @@
+id: cb-017
+title: "Search Gmail for messages from a sender"
+difficulty: easy
+category: communication
+description: |
+  Search Gmail for all emails from "security@github.com" received in the
+  last 30 days. Display the subject, date, and a snippet of each message.
+tools_provided:
+  - google
+initial_state:
+  google:
+    gmail:
+      messages:
+        - id: msg-001
+          from: "security@github.com"
+          to: "dev@acme.com"
+          subject: "Security advisory: CVE-2026-1234"
+          date: "2026-03-05T08:00:00Z"
+          snippet: "A critical vulnerability has been identified in..."
+        - id: msg-002
+          from: "security@github.com"
+          to: "dev@acme.com"
+          subject: "Dependabot alert: lodash prototype pollution"
+          date: "2026-03-01T12:00:00Z"
+          snippet: "A new Dependabot alert has been created for..."
+        - id: msg-003
+          from: "noreply@linear.app"
+          to: "dev@acme.com"
+          subject: "Issue ACM-101 assigned to you"
+          date: "2026-03-08T09:00:00Z"
+          snippet: "Sarah assigned ACM-101 to you..."
+        - id: msg-004
+          from: "security@github.com"
+          to: "dev@acme.com"
+          subject: "Secret scanning alert: API key exposed"
+          date: "2026-02-25T15:00:00Z"
+          snippet: "A secret has been detected in your repository..."
+expected_state:
+  google:
+    command_history:
+      - pattern: "google gmail search.*from:security@github.com"
+    output_contains:
+      - "CVE-2026-1234"
+      - "Dependabot alert"
+      - "Secret scanning alert"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-018.yaml

@@ -0,0 +1,52 @@
+id: cb-018
+title: "List Google Calendar events for today"
+difficulty: easy
+category: data_ops
+description: |
+  List all events on the primary Google Calendar for today (2026-03-12).
+  Show the event title, start time, end time, and attendees.
+tools_provided:
+  - google
+initial_state:
+  google:
+    calendar:
+      events:
+        - id: evt-001
+          title: "Daily Standup"
+          start: "2026-03-12T09:00:00Z"
+          end: "2026-03-12T09:15:00Z"
+          attendees: ["alice@acme.com", "bob@acme.com", "sarah@acme.com"]
+          calendar: primary
+        - id: evt-002
+          title: "Sprint Planning"
+          start: "2026-03-12T14:00:00Z"
+          end: "2026-03-12T15:00:00Z"
+          attendees: ["alice@acme.com", "sarah@acme.com", "mark@acme.com"]
+          calendar: primary
+        - id: evt-003
+          title: "1:1 with Manager"
+          start: "2026-03-12T16:00:00Z"
+          end: "2026-03-12T16:30:00Z"
+          attendees: ["alice@acme.com", "vp-eng@acme.com"]
+          calendar: primary
+        - id: evt-004
+          title: "Architecture Review"
+          start: "2026-03-13T10:00:00Z"
+          end: "2026-03-13T11:00:00Z"
+          attendees: ["alice@acme.com", "bob@acme.com"]
+          calendar: primary
+expected_state:
+  google:
+    command_history:
+      - pattern: "google calendar list.*--date.*2026-03-12"
+    output_contains:
+      - "Daily Standup"
+      - "Sprint Planning"
+      - "1:1 with Manager"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-019.yaml

@@ -0,0 +1,52 @@
+id: cb-019
+title: "List files in Google Drive"
+difficulty: easy
+category: data_ops
+description: |
+  List all files in the Google Drive folder "Engineering/Architecture".
+  Show the file name, size, last modified date, and owner.
+tools_provided:
+  - google
+initial_state:
+  google:
+    drive:
+      folders:
+        - path: "Engineering/Architecture"
+          files:
+            - name: "System Design v2.pdf"
+              size: "4.2 MB"
+              modified: "2026-03-01T10:00:00Z"
+              owner: "alice@acme.com"
+            - name: "Database Schema.drawio"
+              size: "128 KB"
+              modified: "2026-02-28T14:00:00Z"
+              owner: "bob@acme.com"
+            - name: "API Spec OpenAPI.yaml"
+              size: "56 KB"
+              modified: "2026-03-10T16:00:00Z"
+              owner: "sarah@acme.com"
+            - name: "Infrastructure Diagram.png"
+              size: "2.1 MB"
+              modified: "2026-02-15T09:00:00Z"
+              owner: "ops-alice@acme.com"
+            - name: "Migration Plan Q1.docx"
+              size: "320 KB"
+              modified: "2026-03-05T11:00:00Z"
+              owner: "mark@acme.com"
+expected_state:
+  google:
+    command_history:
+      - pattern: "google drive list.*Engineering/Architecture"
+    output_contains:
+      - "System Design v2.pdf"
+      - "Database Schema.drawio"
+      - "API Spec OpenAPI.yaml"
+      - "Infrastructure Diagram.png"
+      - "Migration Plan Q1.docx"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-020.yaml

@@ -0,0 +1,46 @@
+id: cb-020
+title: "Comment on a Linear issue"
+difficulty: easy
+category: project_mgmt
+description: |
+  Add a comment to the Linear issue "ACM-102" (Database migration script)
+  with the text: "Migration tested successfully on staging. Ready for production
+  deployment. Rolling update strategy confirmed with ops team."
+tools_provided:
+  - linear
+initial_state:
+  linear:
+    issues:
+      - id: ACM-102
+        title: "Database migration script"
+        status: in_progress
+        priority: medium
+        assignee: sarah@acme.com
+        team: Platform
+        comments:
+          - user: sarah@acme.com
+            body: "Schema changes drafted, running test suite."
+          - user: mark@acme.com
+            body: "Make sure to test with the staging dataset."
+      - id: ACM-103
+        title: "Update CI pipeline"
+        status: in_progress
+        priority: low
+        assignee: mark@acme.com
+        team: Platform
+        comments: []
+expected_state:
+  linear:
+    issues:
+      - id: ACM-102
+        comments:
+          - body_contains: "Migration tested successfully on staging"
+    command_history:
+      - pattern: "linear issue comment ACM-102"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 3
+optimal_commands: 1
+timeout_seconds: 30

data/tasks/cb-021.yaml

@@ -0,0 +1,70 @@
+id: cb-021
+title: "Find urgent GitHub issues and post summary to Slack"
+difficulty: medium
+category: composite
+description: |
+  Find all open GitHub issues in "acme-corp/web-platform" that have the label
+  "priority:critical" or "priority:high". Then compose a summary of these issues
+  and post it to the #engineering Slack channel with the format:
+  "Urgent Issues Report: N issues require attention" followed by a list.
+tools_provided:
+  - gh
+  - slack
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 42
+            title: "Fix login redirect loop"
+            state: open
+            assignee: alice
+            labels: ["bug", "priority:critical"]
+          - number: 45
+            title: "Memory leak in websocket handler"
+            state: open
+            assignee: null
+            labels: ["bug", "priority:high"]
+          - number: 46
+            title: "Migrate to Node 20"
+            state: open
+            assignee: dave
+            labels: ["chore"]
+          - number: 47
+            title: "SQL injection in search endpoint"
+            state: open
+            assignee: bob
+            labels: ["security", "priority:critical"]
+          - number: 48
+            title: "Add dark mode toggle"
+            state: open
+            assignee: carol
+            labels: ["enhancement", "priority:low"]
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh issue list.*--label.*priority"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "Urgent Issues Report"
+          - text_contains: "login redirect"
+          - text_contains: "Memory leak"
+          - text_contains: "SQL injection"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-022.yaml

@@ -0,0 +1,70 @@
+id: cb-022
+title: "Create Linear issues from Slack channel messages about bugs"
+difficulty: medium
+category: composite
+description: |
+  Search the #incidents Slack channel for messages from the last 24 hours that
+  mention "bug" or "error". For each unique bug report found, create a
+  corresponding Linear issue in the "Platform" team with priority "high"
+  and status "triage".
+tools_provided:
+  - slack
+  - linear
+initial_state:
+  slack:
+    channels:
+      - id: C005
+        name: incidents
+        messages:
+          - user: ops-bot
+            text: "Bug detected: Payment processing fails for amounts > $10,000"
+            ts: "2026-03-12T08:30:00Z"
+          - user: alice
+            text: "Error in user registration — email validation regex rejects valid TLDs"
+            ts: "2026-03-12T09:15:00Z"
+          - user: bob
+            text: "Deployed hotfix for the caching issue from yesterday"
+            ts: "2026-03-12T10:00:00Z"
+          - user: carol
+            text: "Bug report from customer: PDF export generates blank pages"
+            ts: "2026-03-12T11:00:00Z"
+          - user: dave
+            text: "Standup reminder: 2pm today"
+            ts: "2026-03-12T11:30:00Z"
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+        members:
+          - sarah@acme.com
+          - mark@acme.com
+    issues:
+      - id: ACM-110
+        title: "Existing issue"
+        status: backlog
+        priority: low
+        team: Platform
+expected_state:
+  slack:
+    command_history:
+      - pattern: "slack message search.*(bug|error)"
+  linear:
+    issues:
+      - title_contains: "Payment processing"
+        priority: high
+        team: Platform
+      - title_contains: "email validation"
+        priority: high
+        team: Platform
+      - title_contains: "PDF export"
+        priority: high
+        team: Platform
+    command_history:
+      - pattern: "linear issue create.*--team.*Platform.*--priority.*high"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 10
+optimal_commands: 4
+timeout_seconds: 90

data/tasks/cb-023.yaml

@@ -0,0 +1,83 @@
+id: cb-023
+title: "Sync GitHub issue labels with Linear issue priorities"
+difficulty: medium
+category: composite
+description: |
+  For each open issue in the GitHub repo "acme-corp/web-platform" that has a
+  "linear:" prefixed label (e.g., "linear:ACM-101"), find the corresponding
+  Linear issue and update its priority to match the GitHub issue's priority
+  label. Map as follows: "priority:critical" -> urgent, "priority:high" -> high,
+  "priority:medium" -> medium, "priority:low" -> low.
+tools_provided:
+  - gh
+  - linear
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 50
+            title: "Auth token expiry handling"
+            state: open
+            labels: ["bug", "priority:critical", "linear:ACM-201"]
+          - number: 51
+            title: "API rate limiting"
+            state: open
+            labels: ["enhancement", "priority:medium", "linear:ACM-202"]
+          - number: 52
+            title: "Fix CORS headers"
+            state: open
+            labels: ["bug", "priority:high", "linear:ACM-203"]
+          - number: 53
+            title: "Update docs"
+            state: open
+            labels: ["docs"]
+          - number: 54
+            title: "Logging improvements"
+            state: closed
+            labels: ["chore", "priority:low", "linear:ACM-204"]
+  linear:
+    issues:
+      - id: ACM-201
+        title: "Auth token expiry handling"
+        status: in_progress
+        priority: medium
+        team: Platform
+      - id: ACM-202
+        title: "API rate limiting"
+        status: todo
+        priority: low
+        team: Platform
+      - id: ACM-203
+        title: "Fix CORS headers"
+        status: todo
+        priority: low
+        team: Platform
+      - id: ACM-204
+        title: "Logging improvements"
+        status: done
+        priority: low
+        team: Platform
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh issue list.*--repo acme-corp/web-platform"
+  linear:
+    issues:
+      - id: ACM-201
+        priority: urgent
+      - id: ACM-202
+        priority: medium
+      - id: ACM-203
+        priority: high
+    command_history:
+      - pattern: "linear issue update ACM-201.*--priority.*urgent"
+      - pattern: "linear issue update ACM-202.*--priority.*medium"
+      - pattern: "linear issue update ACM-203.*--priority.*high"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 10
+optimal_commands: 5
+timeout_seconds: 90

data/tasks/cb-024.yaml

@@ -0,0 +1,73 @@
+id: cb-024
+title: "Find unassigned Linear issues and notify team on Slack"
+difficulty: medium
+category: composite
+description: |
+  Find all Linear issues in the "Platform" team that have status "todo" or
+  "in_progress" but have no assignee. Post a message to the #engineering
+  Slack channel listing these unassigned issues and asking team members
+  to pick them up.
+tools_provided:
+  - linear
+  - slack
+initial_state:
+  linear:
+    issues:
+      - id: ACM-301
+        title: "Implement rate limiter middleware"
+        status: todo
+        priority: high
+        assignee: null
+        team: Platform
+      - id: ACM-302
+        title: "Set up integration tests"
+        status: in_progress
+        priority: medium
+        assignee: null
+        team: Platform
+      - id: ACM-303
+        title: "Refactor auth module"
+        status: todo
+        priority: low
+        assignee: sarah@acme.com
+        team: Platform
+      - id: ACM-304
+        title: "Add health check endpoints"
+        status: todo
+        priority: medium
+        assignee: null
+        team: Platform
+      - id: ACM-305
+        title: "Database connection pooling"
+        status: backlog
+        priority: low
+        assignee: null
+        team: Platform
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  linear:
+    command_history:
+      - pattern: "linear issue list.*--team.*Platform"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "ACM-301"
+          - text_contains: "ACM-302"
+          - text_contains: "ACM-304"
+          - text_contains: "unassigned"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-025.yaml

@@ -0,0 +1,78 @@
+id: cb-025
+title: "Create Notion summary from Linear project status"
+difficulty: medium
+category: composite
+description: |
+  Retrieve the status of the Linear project "Q1 Platform Migration" including
+  all its issues and their current states. Create a Notion page under
+  "Engineering Wiki" titled "Q1 Platform Migration - Status Report" that
+  summarizes the project progress: total issues, completed vs in-progress vs
+  todo counts, and lists any blocked items.
+tools_provided:
+  - linear
+  - notion
+initial_state:
+  linear:
+    projects:
+      - name: "Q1 Platform Migration"
+        status: in_progress
+        lead: sarah@acme.com
+        target_date: "2026-03-31"
+        teams: ["Platform"]
+    issues:
+      - id: ACM-401
+        title: "Migrate user service to gRPC"
+        status: done
+        priority: high
+        project: "Q1 Platform Migration"
+        team: Platform
+      - id: ACM-402
+        title: "Update API gateway routing"
+        status: in_progress
+        priority: high
+        project: "Q1 Platform Migration"
+        team: Platform
+      - id: ACM-403
+        title: "Database schema migration"
+        status: done
+        priority: urgent
+        project: "Q1 Platform Migration"
+        team: Platform
+      - id: ACM-404
+        title: "Update client SDKs"
+        status: todo
+        priority: medium
+        project: "Q1 Platform Migration"
+        team: Platform
+      - id: ACM-405
+        title: "Load testing new endpoints"
+        status: blocked
+        priority: high
+        project: "Q1 Platform Migration"
+        team: Platform
+  notion:
+    pages:
+      - id: pg-001
+        title: "Engineering Runbook"
+        parent: "Engineering Wiki"
+    databases:
+      - id: db-001
+        title: "Engineering Wiki"
+expected_state:
+  linear:
+    command_history:
+      - pattern: "linear issue list.*--project.*Q1 Platform Migration"
+  notion:
+    pages:
+      - title: "Q1 Platform Migration - Status Report"
+        parent: "Engineering Wiki"
+        content_contains: "blocked"
+    command_history:
+      - pattern: "notion page create.*--title.*Q1 Platform Migration.*Status Report"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-026.yaml

@@ -0,0 +1,77 @@
+id: cb-026
+title: "Find Jira issues blocked for more than 3 days and notify on Slack"
+difficulty: medium
+category: composite
+description: |
+  Search the Jira project "INFRA" for issues with status "Blocked" that have
+  been in that status for more than 3 days. For each blocked issue, post a
+  notification to the #incidents Slack channel with the issue key, summary,
+  assignee, and how long it has been blocked.
+tools_provided:
+  - jira
+  - slack
+initial_state:
+  jira:
+    projects:
+      - key: INFRA
+        name: "Infrastructure"
+        issues:
+          - key: INFRA-301
+            summary: "Upgrade load balancer firmware"
+            status: "Blocked"
+            status_changed: "2026-03-07T10:00:00Z"
+            assignee: ops-alice
+            priority: High
+            blocker_reason: "Waiting for vendor approval"
+          - key: INFRA-302
+            summary: "Deploy new monitoring agent"
+            status: "Blocked"
+            status_changed: "2026-03-11T14:00:00Z"
+            assignee: ops-bob
+            priority: Medium
+            blocker_reason: "Dependency on INFRA-301"
+          - key: INFRA-303
+            summary: "Rotate SSL certificates"
+            status: "Blocked"
+            status_changed: "2026-03-05T09:00:00Z"
+            assignee: ops-carol
+            priority: Critical
+            blocker_reason: "Certificate authority outage"
+          - key: INFRA-304
+            summary: "Set up backup replication"
+            status: "In Progress"
+            assignee: ops-alice
+            priority: High
+          - key: INFRA-305
+            summary: "Network segmentation review"
+            status: "Blocked"
+            status_changed: "2026-03-10T08:00:00Z"
+            assignee: null
+            priority: Medium
+            blocker_reason: "Pending security team review"
+  slack:
+    channels:
+      - id: C005
+        name: incidents
+        is_private: false
+        num_members: 15
+        messages: []
+expected_state:
+  jira:
+    command_history:
+      - pattern: "jira issue list.*--project.*INFRA.*--status.*Blocked"
+  slack:
+    channels:
+      - name: incidents
+        messages:
+          - text_contains: "INFRA-301"
+          - text_contains: "INFRA-303"
+    command_history:
+      - pattern: "slack message send.*--channel.*incidents"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-027.yaml

@@ -0,0 +1,71 @@
+id: cb-027
+title: "Search Gmail for meeting invites and create Linear tasks"
+difficulty: medium
+category: composite
+description: |
+  Search Gmail for emails with subject containing "Action Items" or "Follow-up"
+  received in the last 7 days. Extract action items from these emails and create
+  corresponding Linear issues in the "Platform" team with appropriate priorities.
+tools_provided:
+  - google
+  - linear
+initial_state:
+  google:
+    gmail:
+      messages:
+        - id: msg-101
+          from: "alice@acme.com"
+          subject: "Meeting Action Items - Sprint Review 3/10"
+          date: "2026-03-10T16:00:00Z"
+          body: |
+            Action items from today's sprint review:
+            1. [HIGH] Investigate performance regression in search API
+            2. [MEDIUM] Update API documentation for v2 endpoints
+            3. [LOW] Clean up deprecated feature flags
+        - id: msg-102
+          from: "bob@acme.com"
+          subject: "Follow-up: Security Audit Discussion"
+          date: "2026-03-11T11:00:00Z"
+          body: |
+            Follow-up tasks:
+            1. [URGENT] Patch CVE-2026-5678 in auth library
+            2. [HIGH] Enable CSP headers on all endpoints
+        - id: msg-103
+          from: "carol@acme.com"
+          subject: "Lunch plans for Friday"
+          date: "2026-03-11T12:00:00Z"
+          body: "Anyone want to try the new ramen place?"
+        - id: msg-104
+          from: "noreply@github.com"
+          subject: "PR Review Requested"
+          date: "2026-03-11T14:00:00Z"
+          body: "bob requested your review on PR #567"
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+        members:
+          - sarah@acme.com
+          - mark@acme.com
+    issues: []
+expected_state:
+  google:
+    command_history:
+      - pattern: "google gmail search.*(Action Items|Follow-up)"
+  linear:
+    issues:
+      - title_contains: "performance regression"
+        priority: high
+        team: Platform
+      - title_contains: "CVE-2026-5678"
+        priority: urgent
+        team: Platform
+    command_history:
+      - pattern: "linear issue create.*--team.*Platform"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 10
+optimal_commands: 6
+timeout_seconds: 90

data/tasks/cb-028.yaml

@@ -0,0 +1,74 @@
+id: cb-028
+title: "Find large files in Google Drive and post report to Slack"
+difficulty: medium
+category: composite
+description: |
+  List all files in Google Drive that are larger than 50 MB. Create a summary
+  report with the file name, size, owner, and last modified date, then post
+  this report to the #engineering Slack channel with a message asking owners
+  to archive or clean up unused large files.
+tools_provided:
+  - google
+  - slack
+initial_state:
+  google:
+    drive:
+      all_files:
+        - name: "production-db-dump-20260301.sql"
+          size_mb: 2400
+          modified: "2026-03-01T03:00:00Z"
+          owner: "ops-alice@acme.com"
+          path: "Backups/"
+        - name: "demo-video-q1.mp4"
+          size_mb: 350
+          modified: "2026-02-15T14:00:00Z"
+          owner: "marketing@acme.com"
+          path: "Marketing/"
+        - name: "Architecture Diagram.png"
+          size_mb: 2
+          modified: "2026-03-10T09:00:00Z"
+          owner: "bob@acme.com"
+          path: "Engineering/"
+        - name: "ml-model-weights-v3.bin"
+          size_mb: 890
+          modified: "2026-01-20T10:00:00Z"
+          owner: "data-team@acme.com"
+          path: "ML/"
+        - name: "load-test-results.csv"
+          size_mb: 75
+          modified: "2026-03-08T16:00:00Z"
+          owner: "sarah@acme.com"
+          path: "Engineering/Testing/"
+        - name: "sprint-notes.docx"
+          size_mb: 1
+          modified: "2026-03-11T09:00:00Z"
+          owner: "alice@acme.com"
+          path: "Engineering/"
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  google:
+    command_history:
+      - pattern: "google drive list.*--min-size"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "production-db-dump"
+          - text_contains: "demo-video"
+          - text_contains: "ml-model-weights"
+          - text_contains: "load-test-results"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-029.yaml

@@ -0,0 +1,81 @@
+id: cb-029
+title: "Cross-reference GitHub PRs with Linear issues"
+difficulty: medium
+category: composite
+description: |
+  List all open pull requests in "acme-corp/web-platform" that reference a
+  Linear issue in their title or body (pattern: ACM-NNN). For each referenced
+  Linear issue, update its status to "in_progress" if it is currently "todo".
+  Report any PRs that reference non-existent Linear issues.
+tools_provided:
+  - gh
+  - linear
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        pull_requests:
+          - number: 200
+            title: "feat: Implement PKCE flow [ACM-501]"
+            state: open
+            author: alice
+            body: "Implements the OAuth2 PKCE flow as described in ACM-501."
+          - number: 201
+            title: "fix: CORS headers [ACM-502]"
+            state: open
+            author: bob
+            body: "Fixes CORS header configuration per ACM-502."
+          - number: 202
+            title: "chore: Update dependencies"
+            state: open
+            author: carol
+            body: "Routine dependency updates, no Linear issue."
+          - number: 203
+            title: "feat: Rate limiter [ACM-503]"
+            state: open
+            author: dave
+            body: "Implements rate limiting middleware. Refs ACM-503."
+          - number: 204
+            title: "fix: Session handling [ACM-999]"
+            state: open
+            author: alice
+            body: "Fix session timeout. References ACM-999."
+  linear:
+    issues:
+      - id: ACM-501
+        title: "Implement OAuth2 PKCE flow"
+        status: todo
+        priority: high
+        team: Platform
+      - id: ACM-502
+        title: "Fix CORS headers"
+        status: in_progress
+        priority: medium
+        team: Platform
+      - id: ACM-503
+        title: "Implement rate limiter"
+        status: todo
+        priority: high
+        team: Platform
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh pr list.*--repo acme-corp/web-platform"
+  linear:
+    issues:
+      - id: ACM-501
+        status: in_progress
+      - id: ACM-502
+        status: in_progress
+      - id: ACM-503
+        status: in_progress
+    command_history:
+      - pattern: "linear issue update ACM-501.*--status.*in_progress"
+      - pattern: "linear issue update ACM-503.*--status.*in_progress"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 10
+optimal_commands: 6
+timeout_seconds: 90

data/tasks/cb-030.yaml

@@ -0,0 +1,77 @@
+id: cb-030
+title: "Create Notion doc listing all Slack channel topics"
+difficulty: medium
+category: composite
+description: |
+  List all public Slack channels in the workspace and collect their names,
+  topics, and member counts. Create a Notion page under "Company Resources"
+  titled "Slack Channel Directory" that organizes all channels into a
+  structured document with descriptions and member counts.
+tools_provided:
+  - slack
+  - notion
+initial_state:
+  slack:
+    channels:
+      - id: C001
+        name: general
+        is_private: false
+        num_members: 45
+        topic: "Company-wide announcements and updates"
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        topic: "Engineering discussions, code reviews, technical decisions"
+      - id: C003
+        name: design-team
+        is_private: true
+        num_members: 8
+        topic: "Design reviews and feedback"
+      - id: C004
+        name: random
+        is_private: false
+        num_members: 40
+        topic: "Non-work banter, memes, and fun"
+      - id: C005
+        name: incidents
+        is_private: false
+        num_members: 15
+        topic: "Production incident coordination and post-mortems"
+      - id: C006
+        name: hiring
+        is_private: false
+        num_members: 12
+        topic: "Hiring pipeline updates and interview feedback"
+      - id: C007
+        name: product
+        is_private: false
+        num_members: 18
+        topic: "Product roadmap, feature requests, user feedback"
+  notion:
+    pages:
+      - id: pg-010
+        title: "Company Handbook"
+        parent: "Company Resources"
+    databases:
+      - id: db-002
+        title: "Company Resources"
+expected_state:
+  slack:
+    command_history:
+      - pattern: "slack channel list"
+  notion:
+    pages:
+      - title: "Slack Channel Directory"
+        parent: "Company Resources"
+        content_contains: "engineering"
+        content_contains_2: "incidents"
+    command_history:
+      - pattern: "notion page create.*--title.*Slack Channel Directory"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 8
+optimal_commands: 3
+timeout_seconds: 60

data/tasks/cb-031.yaml

@@ -0,0 +1,127 @@
+id: cb-031
+title: "Incident response: find broken commit, create issue, assign on-call, notify Slack"
+difficulty: hard
+category: composite
+description: |
+  A production incident has been reported. Investigate the GitHub repository
+  "acme-corp/web-platform" to find the most recent merged PR that touched
+  files in the "src/auth/" directory. Create a GitHub issue documenting the
+  incident and link it to that PR. Then find the on-call engineer from the
+  Linear team "Platform" (the one with the "oncall" label on their current
+  issue) and assign the GitHub issue to them. Finally, post an incident
+  notification to the #incidents Slack channel with the issue link, suspected
+  PR, and assigned engineer.
+tools_provided:
+  - gh
+  - linear
+  - slack
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        pull_requests:
+          - number: 180
+            title: "feat: Add session refresh logic"
+            state: closed
+            merged: true
+            merged_at: "2026-03-12T06:00:00Z"
+            author: dave
+            files_changed: ["src/auth/session.ts", "src/auth/refresh.ts"]
+          - number: 179
+            title: "fix: Update user avatar upload"
+            state: closed
+            merged: true
+            merged_at: "2026-03-11T15:00:00Z"
+            author: carol
+            files_changed: ["src/profile/avatar.ts"]
+          - number: 178
+            title: "chore: Bump auth library version"
+            state: closed
+            merged: true
+            merged_at: "2026-03-11T10:00:00Z"
+            author: bob
+            files_changed: ["package.json", "src/auth/config.ts"]
+          - number: 181
+            title: "docs: Update API reference"
+            state: open
+            author: alice
+            files_changed: ["docs/api.md"]
+        issues:
+          - number: 90
+            title: "Existing tracking issue"
+            state: open
+            labels: ["tracking"]
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+        members:
+          - sarah@acme.com
+          - mark@acme.com
+          - dave@acme.com
+          - bob@acme.com
+    issues:
+      - id: ACM-600
+        title: "On-call rotation week 11"
+        status: in_progress
+        priority: medium
+        assignee: mark@acme.com
+        team: Platform
+        labels: ["oncall"]
+      - id: ACM-601
+        title: "Refactor error handling"
+        status: todo
+        priority: low
+        assignee: sarah@acme.com
+        team: Platform
+        labels: []
+      - id: ACM-602
+        title: "Performance optimization"
+        status: in_progress
+        priority: medium
+        assignee: dave@acme.com
+        team: Platform
+        labels: []
+  slack:
+    channels:
+      - id: C005
+        name: incidents
+        is_private: false
+        num_members: 15
+        messages: []
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - title_contains: "incident"
+            state: open
+            assignee: mark
+            body_contains: "180"
+    command_history:
+      - pattern: "gh pr list.*--state.*merged"
+      - pattern: "gh issue create.*--repo acme-corp/web-platform"
+  linear:
+    command_history:
+      - pattern: "linear issue list.*--team.*Platform.*--label.*oncall"
+  slack:
+    channels:
+      - name: incidents
+        messages:
+          - text_contains: "incident"
+          - text_contains: "mark"
+          - text_contains: "180"
+    command_history:
+      - pattern: "slack message send.*--channel.*incidents"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 15
+optimal_commands: 7
+timeout_seconds: 120

data/tasks/cb-032.yaml

@@ -0,0 +1,122 @@
+id: cb-032
+title: "Sprint planning: pull Linear backlog, create Notion sprint doc, notify team"
+difficulty: hard
+category: composite
+description: |
+  Prepare for sprint planning. Pull all Linear issues from the "Platform"
+  team that are in "backlog" or "todo" status and have priority "high" or
+  "urgent". Create a Notion page under "Engineering Wiki" titled
+  "Sprint 12 Planning - 2026-03-12" that organizes these issues by priority,
+  includes estimated effort, and highlights any blocked dependencies.
+  Then post a message to the #engineering Slack channel announcing the sprint
+  planning doc is ready and listing the top 3 highest priority items.
+tools_provided:
+  - linear
+  - notion
+  - slack
+initial_state:
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+    issues:
+      - id: ACM-701
+        title: "Implement GraphQL subscriptions"
+        status: backlog
+        priority: urgent
+        assignee: null
+        team: Platform
+        estimate: 8
+        labels: ["api"]
+      - id: ACM-702
+        title: "Add OpenTelemetry tracing"
+        status: todo
+        priority: high
+        assignee: sarah@acme.com
+        team: Platform
+        estimate: 5
+        labels: ["observability"]
+      - id: ACM-703
+        title: "Migrate to PostgreSQL 16"
+        status: backlog
+        priority: high
+        assignee: null
+        team: Platform
+        estimate: 13
+        labels: ["database", "blocked"]
+        blocked_by: "ACM-710"
+      - id: ACM-704
+        title: "Implement circuit breaker pattern"
+        status: todo
+        priority: urgent
+        assignee: mark@acme.com
+        team: Platform
+        estimate: 5
+        labels: ["resilience"]
+      - id: ACM-705
+        title: "Update API documentation"
+        status: todo
+        priority: low
+        assignee: null
+        team: Platform
+        estimate: 3
+        labels: ["docs"]
+      - id: ACM-706
+        title: "Add retry logic to external calls"
+        status: backlog
+        priority: high
+        assignee: null
+        team: Platform
+        estimate: 3
+        labels: ["resilience"]
+      - id: ACM-710
+        title: "Provision new database cluster"
+        status: in_progress
+        priority: high
+        assignee: ops-alice@acme.com
+        team: Platform
+        estimate: 8
+        labels: ["infrastructure"]
+  notion:
+    databases:
+      - id: db-001
+        title: "Engineering Wiki"
+    pages:
+      - id: pg-020
+        title: "Sprint 11 Retrospective"
+        parent: "Engineering Wiki"
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  linear:
+    command_history:
+      - pattern: "linear issue list.*--team.*Platform"
+  notion:
+    pages:
+      - title_contains: "Sprint 12 Planning"
+        parent: "Engineering Wiki"
+        content_contains: "ACM-701"
+        content_contains_2: "ACM-704"
+        content_contains_3: "blocked"
+    command_history:
+      - pattern: "notion page create.*Sprint 12"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "Sprint 12"
+          - text_contains: "planning"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 12
+optimal_commands: 5
+timeout_seconds: 120

data/tasks/cb-033.yaml

@@ -0,0 +1,96 @@
+id: cb-033
+title: "Cross-platform project sync: GitHub milestones to Linear projects to Notion"
+difficulty: hard
+category: composite
+description: |
+  Synchronize project tracking across three platforms. First, list all open
+  GitHub milestones in "acme-corp/web-platform". For each milestone, find or
+  create the corresponding Linear project (matching by name). Update the
+  Linear project's target date to match the milestone's due date. Finally,
+  create a Notion page under "Project Tracking" that shows a unified view
+  of all projects with their GitHub milestone progress (open/closed issue
+  counts) and Linear project status.
+tools_provided:
+  - gh
+  - linear
+  - notion
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        milestones:
+          - title: "v3.0 Release"
+            state: open
+            due_date: "2026-04-01"
+            open_issues: 12
+            closed_issues: 28
+            description: "Major version release with new auth system"
+          - title: "Security Hardening"
+            state: open
+            due_date: "2026-03-20"
+            open_issues: 5
+            closed_issues: 15
+            description: "Address all findings from Q4 security audit"
+          - title: "Performance Sprint"
+            state: open
+            due_date: "2026-03-25"
+            open_issues: 8
+            closed_issues: 4
+            description: "P95 latency reduction targets"
+          - title: "v2.9 Release"
+            state: closed
+            due_date: "2026-02-28"
+            open_issues: 0
+            closed_issues: 35
+  linear:
+    projects:
+      - name: "v3.0 Release"
+        status: in_progress
+        lead: sarah@acme.com
+        target_date: "2026-03-28"
+        teams: ["Platform"]
+      - name: "Security Hardening"
+        status: in_progress
+        lead: bob@acme.com
+        target_date: "2026-03-15"
+        teams: ["Platform", "Security"]
+  notion:
+    databases:
+      - id: db-003
+        title: "Project Tracking"
+    pages:
+      - id: pg-030
+        title: "Archived Projects"
+        parent: "Project Tracking"
+expected_state:
+  gh:
+    command_history:
+      - pattern: "gh api.*milestones"
+  linear:
+    projects:
+      - name: "v3.0 Release"
+        target_date: "2026-04-01"
+      - name: "Security Hardening"
+        target_date: "2026-03-20"
+      - name: "Performance Sprint"
+        status: planned
+    command_history:
+      - pattern: "linear project update.*v3.0.*--target-date"
+      - pattern: "linear project (update|create).*Security Hardening"
+      - pattern: "linear project create.*Performance Sprint"
+  notion:
+    pages:
+      - title_contains: "Project Sync"
+        parent: "Project Tracking"
+        content_contains: "v3.0 Release"
+        content_contains_2: "Security Hardening"
+        content_contains_3: "Performance Sprint"
+    command_history:
+      - pattern: "notion page create.*--parent.*Project Tracking"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 15
+optimal_commands: 8
+timeout_seconds: 120

data/tasks/cb-034.yaml

@@ -0,0 +1,125 @@
+id: cb-034
+title: "Bug triage: GitHub issues to Linear issues, assign by labels, notify Slack"
+difficulty: hard
+category: composite
+description: |
+  Perform a full bug triage workflow. Find all open GitHub issues in
+  "acme-corp/web-platform" with the "bug" label that don't have a
+  "linear:" label yet. For each bug, create a Linear issue in the
+  appropriate team based on GitHub labels ("auth" -> Security team,
+  "api" -> Platform team, "ui" -> Frontend team, default -> Platform).
+  Set priority based on other labels ("priority:critical" -> urgent,
+  "priority:high" -> high, otherwise medium). Add a "linear:ACM-XXX"
+  label back to each GitHub issue. Finally, post a triage summary to
+  #engineering on Slack listing all newly created Linear issues.
+tools_provided:
+  - gh
+  - linear
+  - slack
+initial_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 100
+            title: "XSS vulnerability in search input"
+            state: open
+            labels: ["bug", "auth", "priority:critical"]
+            assignee: null
+          - number: 101
+            title: "REST API returns 500 on empty payload"
+            state: open
+            labels: ["bug", "api", "priority:high"]
+            assignee: null
+          - number: 102
+            title: "Button misalignment on mobile"
+            state: open
+            labels: ["bug", "ui"]
+            assignee: null
+          - number: 103
+            title: "Race condition in job queue"
+            state: open
+            labels: ["bug", "priority:high"]
+            assignee: null
+          - number: 104
+            title: "Implement dark mode"
+            state: open
+            labels: ["enhancement", "ui"]
+            assignee: carol
+          - number: 105
+            title: "Token refresh bug [linear:ACM-501]"
+            state: open
+            labels: ["bug", "auth", "linear:ACM-501"]
+            assignee: alice
+  linear:
+    teams:
+      - name: Platform
+        key: ACM
+        members: ["sarah@acme.com", "mark@acme.com"]
+      - name: Security
+        key: SEC
+        members: ["alice@acme.com", "bob@acme.com"]
+      - name: Frontend
+        key: FE
+        members: ["carol@acme.com", "dave@acme.com"]
+    issues:
+      - id: ACM-501
+        title: "Token refresh bug"
+        status: in_progress
+        priority: high
+        team: Security
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+expected_state:
+  gh:
+    repos:
+      acme-corp/web-platform:
+        issues:
+          - number: 100
+            labels_contain: "linear:"
+          - number: 101
+            labels_contain: "linear:"
+          - number: 102
+            labels_contain: "linear:"
+          - number: 103
+            labels_contain: "linear:"
+    command_history:
+      - pattern: "gh issue list.*--label.*bug"
+      - pattern: "gh issue edit.*--add-label.*linear:"
+  linear:
+    issues:
+      - title_contains: "XSS vulnerability"
+        team: Security
+        priority: urgent
+      - title_contains: "REST API returns 500"
+        team: Platform
+        priority: high
+      - title_contains: "Button misalignment"
+        team: Frontend
+        priority: medium
+      - title_contains: "Race condition"
+        team: Platform
+        priority: high
+    command_history:
+      - pattern: "linear issue create"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "triage"
+          - text_contains: "XSS"
+          - text_contains: "REST API"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 18
+optimal_commands: 12
+timeout_seconds: 180

data/tasks/cb-035.yaml

@@ -0,0 +1,66 @@
+id: cb-035
+title: "(kforge) Deploy artifact: list artifacts, trigger staging pipeline, check status"
+difficulty: hard
+category: custom_cli
+description: |
+  Using the kforge CLI, deploy the latest build artifact for the "web-platform"
+  service to the staging environment. First, list available artifacts to find
+  the most recent successful build. Then trigger a deployment pipeline for
+  staging using that artifact. Wait for the pipeline to reach a terminal state
+  and report the result. If the deployment fails, roll back to the previously
+  deployed version.
+tools_provided:
+  - kforge
+initial_state:
+  kforge:
+    artifacts:
+      - id: art-050
+        service: web-platform
+        version: "2.3.1"
+        build_status: success
+        created_at: "2026-03-12T08:00:00Z"
+        sha: "abc123f"
+      - id: art-049
+        service: web-platform
+        version: "2.3.0"
+        build_status: success
+        created_at: "2026-03-11T16:00:00Z"
+        sha: "def456a"
+      - id: art-048
+        service: web-platform
+        version: "2.2.9"
+        build_status: failed
+        created_at: "2026-03-11T10:00:00Z"
+        sha: "ghi789b"
+      - id: art-047
+        service: api-gateway
+        version: "1.5.2"
+        build_status: success
+        created_at: "2026-03-10T14:00:00Z"
+        sha: "jkl012c"
+    deployments:
+      staging:
+        web-platform:
+          current_version: "2.3.0"
+          artifact_id: art-049
+          deployed_at: "2026-03-11T17:00:00Z"
+          status: healthy
+    pipelines: []
+expected_state:
+  kforge:
+    command_history:
+      - pattern: "kforge artifact list.*--service.*web-platform"
+      - pattern: "kforge deploy trigger.*--env.*staging.*--artifact.*art-050"
+      - pattern: "kforge pipeline status"
+    deployments:
+      staging:
+        web-platform:
+          current_version: "2.3.1"
+          artifact_id: art-050
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 10
+optimal_commands: 4
+timeout_seconds: 90

data/tasks/cb-036.yaml

@@ -0,0 +1,62 @@
+id: cb-036
+title: "(flowctl) Create approval workflow: define steps, add gate, trigger run"
+difficulty: hard
+category: custom_cli
+description: |
+  Using the flowctl CLI, create a new approval workflow called
+  "production-deploy-approval" for the web-platform service. The workflow
+  should have three steps: (1) "security-scan" — automated security scanning,
+  (2) "qa-signoff" — manual approval gate requiring sign-off from the QA lead,
+  (3) "release-manager-approval" — manual approval gate requiring the release
+  manager. After creating the workflow, trigger a run of it with the context
+  of artifact version "2.3.1". Check that the workflow run was created
+  successfully and is in "pending" state waiting for the first step.
+tools_provided:
+  - flowctl
+initial_state:
+  flowctl:
+    workflows:
+      - id: wf-001
+        name: "staging-deploy"
+        steps:
+          - name: "lint-check"
+            type: automated
+          - name: "deploy-staging"
+            type: automated
+        status: active
+    runs: []
+    users:
+      - email: qa-lead@acme.com
+        role: qa_lead
+      - email: release-mgr@acme.com
+        role: release_manager
+      - email: security@acme.com
+        role: security_engineer
+expected_state:
+  flowctl:
+    workflows:
+      - name: "production-deploy-approval"
+        steps:
+          - name: "security-scan"
+            type: automated
+          - name: "qa-signoff"
+            type: manual
+            approver_contains: "qa-lead"
+          - name: "release-manager-approval"
+            type: manual
+            approver_contains: "release-mgr"
+    runs:
+      - workflow: "production-deploy-approval"
+        status: pending
+        context_contains: "2.3.1"
+    command_history:
+      - pattern: "flowctl workflow create.*production-deploy-approval"
+      - pattern: "flowctl workflow add-step"
+      - pattern: "flowctl run trigger.*production-deploy-approval"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 12
+optimal_commands: 6
+timeout_seconds: 90

data/tasks/cb-037.yaml

@@ -0,0 +1,96 @@
+id: cb-037
+title: "(alertmgr) Incident management: acknowledge alerts, create incident, escalate"
+difficulty: hard
+category: custom_cli
+description: |
+  Using the alertmgr CLI, handle a production incident. First, list all
+  firing alerts to understand the scope. Acknowledge all critical alerts
+  related to the "payment-service". Create a new incident titled
+  "Payment Service Degradation" with severity "P1" and link the acknowledged
+  alerts to it. Assign the incident to the on-call responder. If no on-call
+  responder is available, escalate to the engineering manager. Add a timeline
+  entry describing the initial findings.
+tools_provided:
+  - alertmgr
+initial_state:
+  alertmgr:
+    alerts:
+      - id: alert-301
+        name: "High error rate on payment-service"
+        severity: critical
+        status: firing
+        service: payment-service
+        started_at: "2026-03-12T14:00:00Z"
+        labels:
+          team: payments
+          env: production
+      - id: alert-302
+        name: "Payment-service latency > 5s"
+        severity: critical
+        status: firing
+        service: payment-service
+        started_at: "2026-03-12T14:02:00Z"
+        labels:
+          team: payments
+          env: production
+      - id: alert-303
+        name: "Database connection pool exhaustion"
+        severity: warning
+        status: firing
+        service: payment-service
+        started_at: "2026-03-12T14:05:00Z"
+        labels:
+          team: payments
+          env: production
+      - id: alert-304
+        name: "CDN cache hit ratio below threshold"
+        severity: warning
+        status: firing
+        service: cdn-edge
+        started_at: "2026-03-12T13:00:00Z"
+        labels:
+          team: infrastructure
+          env: production
+      - id: alert-305
+        name: "Disk usage above 85%"
+        severity: info
+        status: firing
+        service: log-aggregator
+        started_at: "2026-03-12T12:00:00Z"
+        labels:
+          team: infrastructure
+          env: production
+    incidents: []
+    oncall:
+      payments: null
+      infrastructure: ops-alice@acme.com
+    escalation:
+      payments: eng-manager@acme.com
+      infrastructure: vp-infra@acme.com
+expected_state:
+  alertmgr:
+    alerts:
+      - id: alert-301
+        status: acknowledged
+      - id: alert-302
+        status: acknowledged
+    incidents:
+      - title: "Payment Service Degradation"
+        severity: P1
+        assignee: eng-manager@acme.com
+        linked_alerts: ["alert-301", "alert-302"]
+        timeline:
+          - entry_contains: "initial"
+    command_history:
+      - pattern: "alertmgr alert list.*--status.*firing"
+      - pattern: "alertmgr alert ack.*alert-301"
+      - pattern: "alertmgr alert ack.*alert-302"
+      - pattern: "alertmgr incident create.*--severity.*P1"
+      - pattern: "alertmgr (oncall|escalat)"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 15
+optimal_commands: 8
+timeout_seconds: 120

data/tasks/cb-038.yaml

@@ -0,0 +1,73 @@
+id: cb-038
+title: "(datapipe) Build ETL: connect source, create transform, set up sink, schedule"
+difficulty: hard
+category: custom_cli
+description: |
+  Using the datapipe CLI, build an ETL pipeline that extracts user activity
+  data from a PostgreSQL source, transforms it to compute daily active user
+  metrics, and loads the results into an Elasticsearch sink. Create a source
+  connection to the PostgreSQL database "analytics_db" on host
+  "db.internal:5432". Create a transform step that aggregates user events
+  by day and computes unique user counts. Create a sink connection to
+  Elasticsearch cluster "es.internal:9200" targeting the index
+  "user_metrics". Wire these into a pipeline called "daily-dau-pipeline"
+  and schedule it to run daily at 02:00 UTC.
+tools_provided:
+  - datapipe
+initial_state:
+  datapipe:
+    sources: []
+    transforms: []
+    sinks: []
+    pipelines:
+      - id: pipe-001
+        name: "hourly-logs-pipeline"
+        status: active
+        schedule: "0 * * * *"
+        source: src-010
+        transform: tx-010
+        sink: sink-010
+    connections:
+      - id: src-010
+        type: source
+        connector: s3
+        config:
+          bucket: raw-logs
+      - id: sink-010
+        type: sink
+        connector: elasticsearch
+        config:
+          host: "es.internal:9200"
+          index: raw_logs
+expected_state:
+  datapipe:
+    sources:
+      - connector: postgresql
+        config_contains:
+          host: "db.internal:5432"
+          database: analytics_db
+    transforms:
+      - type: aggregation
+        config_contains: "unique"
+    sinks:
+      - connector: elasticsearch
+        config_contains:
+          host: "es.internal:9200"
+          index: user_metrics
+    pipelines:
+      - name: "daily-dau-pipeline"
+        schedule: "0 2 * * *"
+        status: active
+    command_history:
+      - pattern: "datapipe source create.*--connector.*postgresql"
+      - pattern: "datapipe transform create"
+      - pattern: "datapipe sink create.*--connector.*elasticsearch"
+      - pattern: "datapipe pipeline create.*daily-dau-pipeline"
+      - pattern: "datapipe pipeline schedule"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 15
+optimal_commands: 7
+timeout_seconds: 120

data/tasks/cb-039.yaml

@@ -0,0 +1,101 @@
+id: cb-039
+title: "(meshctl + alertmgr) Detect failing service, reroute traffic, create alert"
+difficulty: hard
+category: composite
+description: |
+  A service mesh health check has detected issues. Using meshctl, check the
+  health of all services in the "production" mesh. For any service with error
+  rate above 5%, reroute its traffic to the canary deployment (weight 0%
+  to primary, 100% to canary). Then use alertmgr to create alerts for each
+  failing service and create an incident if more than one service is affected.
+  Add traffic rerouting details to the incident timeline.
+tools_provided:
+  - meshctl
+  - alertmgr
+initial_state:
+  meshctl:
+    mesh: production
+    services:
+      - name: user-service
+        version: "1.4.0"
+        instances: 3
+        error_rate: 0.2
+        latency_p99_ms: 45
+        traffic_weights:
+          primary: 100
+          canary: 0
+      - name: payment-service
+        version: "2.1.0"
+        instances: 3
+        error_rate: 12.5
+        latency_p99_ms: 3200
+        traffic_weights:
+          primary: 100
+          canary: 0
+      - name: notification-service
+        version: "1.0.3"
+        instances: 2
+        error_rate: 8.7
+        latency_p99_ms: 1500
+        traffic_weights:
+          primary: 100
+          canary: 0
+      - name: search-service
+        version: "3.2.1"
+        instances: 4
+        error_rate: 1.2
+        latency_p99_ms: 120
+        traffic_weights:
+          primary: 100
+          canary: 0
+      - name: auth-service
+        version: "2.0.5"
+        instances: 3
+        error_rate: 0.5
+        latency_p99_ms: 30
+        traffic_weights:
+          primary: 100
+          canary: 0
+  alertmgr:
+    alerts: []
+    incidents: []
+    oncall:
+      payments: oncall-pay@acme.com
+      platform: oncall-plat@acme.com
+expected_state:
+  meshctl:
+    services:
+      - name: payment-service
+        traffic_weights:
+          primary: 0
+          canary: 100
+      - name: notification-service
+        traffic_weights:
+          primary: 0
+          canary: 100
+    command_history:
+      - pattern: "meshctl service health.*--mesh.*production"
+      - pattern: "meshctl traffic shift.*payment-service.*--canary.*100"
+      - pattern: "meshctl traffic shift.*notification-service.*--canary.*100"
+  alertmgr:
+    alerts:
+      - service: payment-service
+        severity: critical
+      - service: notification-service
+        severity: critical
+    incidents:
+      - title_contains: "service"
+        linked_alerts_count_gte: 2
+        timeline:
+          - entry_contains: "reroute"
+    command_history:
+      - pattern: "alertmgr alert create.*payment-service"
+      - pattern: "alertmgr alert create.*notification-service"
+      - pattern: "alertmgr incident create"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 18
+optimal_commands: 10
+timeout_seconds: 150

data/tasks/cb-040.yaml

@@ -0,0 +1,120 @@
+id: cb-040
+title: "(kforge + flowctl + slack) Full deployment: promote artifact, create approval gate, notify"
+difficulty: hard
+category: composite
+description: |
+  Execute a full production deployment workflow using multiple tools.
+  First, use kforge to find the latest successful artifact for "web-platform"
+  that is currently deployed in staging. Verify the staging deployment is
+  healthy. Then use flowctl to create and trigger a "prod-release" approval
+  workflow with steps: automated security scan, manual QA approval, and
+  manual release manager approval. Use kforge to promote the staging artifact
+  to the production environment once the workflow is approved (simulate
+  approval). Finally, post deployment notifications to both #engineering
+  and #incidents Slack channels with the artifact version, deployment status,
+  and a link to the approval workflow run.
+tools_provided:
+  - kforge
+  - flowctl
+  - slack
+initial_state:
+  kforge:
+    artifacts:
+      - id: art-080
+        service: web-platform
+        version: "3.0.0-rc1"
+        build_status: success
+        created_at: "2026-03-12T06:00:00Z"
+        sha: "abc123f"
+      - id: art-079
+        service: web-platform
+        version: "2.9.5"
+        build_status: success
+        created_at: "2026-03-10T14:00:00Z"
+        sha: "def456a"
+      - id: art-078
+        service: api-gateway
+        version: "1.6.0"
+        build_status: success
+        created_at: "2026-03-11T08:00:00Z"
+        sha: "ghi789b"
+    deployments:
+      staging:
+        web-platform:
+          current_version: "3.0.0-rc1"
+          artifact_id: art-080
+          deployed_at: "2026-03-12T07:00:00Z"
+          status: healthy
+      production:
+        web-platform:
+          current_version: "2.9.5"
+          artifact_id: art-079
+          deployed_at: "2026-03-10T15:00:00Z"
+          status: healthy
+    pipelines: []
+  flowctl:
+    workflows:
+      - id: wf-010
+        name: "staging-deploy"
+        status: active
+    runs: []
+    users:
+      - email: qa-lead@acme.com
+        role: qa_lead
+      - email: release-mgr@acme.com
+        role: release_manager
+  slack:
+    channels:
+      - id: C002
+        name: engineering
+        is_private: false
+        num_members: 22
+        messages: []
+      - id: C005
+        name: incidents
+        is_private: false
+        num_members: 15
+        messages: []
+expected_state:
+  kforge:
+    deployments:
+      production:
+        web-platform:
+          current_version: "3.0.0-rc1"
+          artifact_id: art-080
+    command_history:
+      - pattern: "kforge artifact list.*--service.*web-platform"
+      - pattern: "kforge deploy status.*--env.*staging"
+      - pattern: "kforge deploy trigger.*--env.*production.*--artifact.*art-080"
+  flowctl:
+    workflows:
+      - name: "prod-release"
+        steps:
+          - type: automated
+          - type: manual
+          - type: manual
+    runs:
+      - workflow: "prod-release"
+        status: approved
+    command_history:
+      - pattern: "flowctl workflow create.*prod-release"
+      - pattern: "flowctl run trigger.*prod-release"
+  slack:
+    channels:
+      - name: engineering
+        messages:
+          - text_contains: "3.0.0-rc1"
+          - text_contains: "production"
+      - name: incidents
+        messages:
+          - text_contains: "deployment"
+    command_history:
+      - pattern: "slack message send.*--channel.*engineering"
+      - pattern: "slack message send.*--channel.*incidents"
+scoring:
+  outcome: 0.6
+  efficiency: 0.2
+  recovery: 0.2
+max_turns: 20
+optimal_commands: 12
+timeout_seconds: 180