@cursor/july 0.1.108 → 0.1.109

package/docs/guides/bitbucket.md

@@ -0,0 +1,89 @@
+---
+title: "Bitbucket"
+description: "Wake your agent from pull requests, comments, and pushes on Bitbucket Cloud or Bitbucket Data Center."
+---
+
+# Bitbucket agents
+
+Use `bitbucketChannel()` for Bitbucket Cloud and Bitbucket Data Center. The
+channel detects the source from each signed payload and normalizes Data Center
+events to the Bitbucket Cloud event vocabulary.
+
+## Define the channel
+
+Author `agent/channels/bitbucket.ts`:
+
+```ts
+import { bitbucketChannel } from "@cursor/july/channels/bitbucket";
+
+export default bitbucketChannel({});
+```
+
+Without `onPullRequest`, new pull requests start turns. Data Center updates
+also start turns when the source branch has new commits. Comments and pushes
+are opt-in through `onPullRequestComment` and `onPush`. Use `onEvent` for
+other event types. Set `webhookEvents` when managed event delivery must
+subscribe to an event that only `onEvent` handles.
+
+Filter comment hooks by author before starting a turn. This prevents comments
+posted by the agent from triggering another turn.
+
+`ctx.bitbucket.api` can read pull requests, post comments, and create build
+statuses. See the [Channels reference](../reference/channels.md) for hook
+return values and session behavior.
+
+## Connect Bitbucket
+
+Set a repository hook secret and API token:
+
+```bash
+BITBUCKET_WEBHOOK_SECRET=...
+BITBUCKET_TOKEN=...
+```
+
+Add a repository webhook for
+`https://<your-host>/<slug>/v1/channels/bitbucket`. Use the same secret on
+both sides. The channel verifies the `X-Hub-Signature` HMAC before it parses
+the payload.
+
+Bitbucket Cloud uses its 2.0 API by default. Data Center also needs its REST
+API base:
+
+```ts
+export default bitbucketChannel({
+  apiBaseUrl: "https://bitbucket.example.com/rest/api/1.0",
+  repos: ["PLATFORM/api"],
+});
+```
+
+You can set `BITBUCKET_API_BASE_URL` instead.
+
+## Test locally
+
+Start the agent, then replay a pull request you can read:
+
+```bash
+agent-sdk dev
+agent-sdk bitbucket replay \
+  https://bitbucket.example.com/projects/PLATFORM/repos/api/pull-requests/42
+```
+
+Replay supports Bitbucket Cloud and Data Center URLs. `BITBUCKET_TOKEN` needs
+pull request read access. The command reads the pull request, creates a payload
+in the matching dialect, and sends it through the same channel route. Use
+`--events '*'` to replay the supported events declared by the channel. Use
+`--dry-run --out fixtures/bitbucket` to save fixtures.
+
+```bash
+agent-sdk bitbucket events --dir .
+agent-sdk bitbucket forward --dir .
+```
+
+`forward` prints the repository-hook and HTTPS tunnel setup for live
+deliveries.
+
+## Related
+
+- [Channels reference](../reference/channels.md)
+- [Webhooks and custom channels](./webhooks.md)
+- [Evals](../evals.md)

package/docs/guides/github.md

@@ -79,6 +79,37 @@ snapshot in the wake.
 This is the preferred production path: no public URL, no repo admin
 webhook, and no inbound network for GitHub deliveries.
 
+## Connect GitHub Enterprise Server
+
+GitHub Enterprise Server uses the same `githubChannel()` hooks and normalized
+events. Connect it through the direct webhook route. Set the REST API base and
+credentials for your server:
+
+```ts
+export default githubChannel({
+  api: {
+    apiBaseUrl: "https://github.example.com/api/v3",
+  },
+  credentials: {
+    token: () => process.env.GITHUB_TOKEN,
+    webhookSecret: () => process.env.GITHUB_WEBHOOK_SECRET,
+  },
+  onPullRequest: (ctx, pr) =>
+    pr.action === "opened" ? { auth: defaultGitHubAuth(ctx) } : null,
+});
+```
+
+Add a repository webhook for
+`https://<your-host>/<slug>/v1/channels/github`. Use the same webhook secret
+on the server and in `GITHUB_WEBHOOK_SECRET`. The channel verifies
+`X-Hub-Signature-256` before it parses the payload.
+
+Cursor account event pull, `github replay`, and `github forward` target
+GitHub.com. Test Enterprise Server integrations by posting saved webhook
+fixtures to a local `--dev` server. Leave `GITHUB_WEBHOOK_SECRET` unset for
+this local test so the channel admits unsigned loopback deliveries. Use a real
+delivery from your server so the fixture matches its version.
+
 ## Define the channel
 
 Author `agent/channels/github.ts` with `githubChannel()` from

package/docs/guides/gitlab.md

@@ -0,0 +1,97 @@
+---
+title: "GitLab"
+description: "Wake your agent from GitLab merge requests, notes, pipelines, and pushes on GitLab.com or self-managed GitLab."
+---
+
+# GitLab agents
+
+Use `gitlabChannel()` for GitLab.com and self-managed GitLab. The channel
+verifies project hooks, normalizes their payloads, and gives each hook a
+project-bound `ctx.gitlab` API client.
+
+## Define the channel
+
+Author `agent/channels/gitlab.ts`:
+
+```ts
+import { gitlabChannel } from "@cursor/july/channels/gitlab";
+
+export default gitlabChannel({});
+```
+
+Without `onMergeRequest`, new and reopened merge requests start turns.
+Updates start turns only when they include new commits. Notes, pushes, and
+pipelines are opt-in through `onNote`, `onPush`, and `onPipeline`.
+Use `onEvent` for other GitLab event types. Set `webhookEvents` when managed
+event delivery must subscribe to an event that only `onEvent` handles.
+
+Filter note hooks by author before starting a turn. This prevents comments
+posted by the agent from triggering another turn.
+
+`ctx.gitlab` can call the project REST API and create commit statuses. See the
+[Channels reference](../reference/channels.md) for hook return values and
+session behavior.
+
+## Connect GitLab
+
+On Cursor-managed hosting, use the signed-in Cursor account:
+
+```ts
+export default gitlabChannel({
+  cursorAccount: {
+    projects: ["acme/platform"],
+  },
+});
+```
+
+For direct webhooks, set a project hook secret and API token:
+
+```bash
+GITLAB_WEBHOOK_SECRET=...
+GITLAB_TOKEN=...
+```
+
+Add a project webhook for
+`https://<your-host>/<slug>/v1/channels/gitlab`. Use the same value for the
+GitLab secret token and `GITLAB_WEBHOOK_SECRET`. The channel checks
+`X-Gitlab-Token` before it parses the payload.
+
+Self-managed GitLab also needs its REST API base:
+
+```ts
+export default gitlabChannel({
+  apiBaseUrl: "https://gitlab.example.com/api/v4",
+  projects: ["acme/platform"],
+});
+```
+
+You can set `GITLAB_API_BASE_URL` instead.
+
+## Test locally
+
+Start the agent, then replay a merge request you can read:
+
+```bash
+agent-sdk dev
+agent-sdk gitlab replay \
+  https://gitlab.example.com/acme/platform/-/merge_requests/42
+```
+
+`GITLAB_TOKEN` needs API read access. Replay reads the merge request,
+creates GitLab-shaped payloads, and sends them through the same channel route.
+Use `--events '*'` to replay the supported events declared by the channel.
+Use `--dry-run --out fixtures/gitlab` to save fixtures.
+
+```bash
+agent-sdk gitlab events --dir .
+agent-sdk gitlab forward --dir .
+```
+
+GitLab has no local webhook relay. `forward` prints the project-hook and HTTPS
+tunnel setup for live deliveries.
+
+## Related
+
+- [Channels reference](../reference/channels.md)
+- [Webhooks and custom channels](./webhooks.md)
+- [Evals](../evals.md)

package/docs/guides/webhooks.md

@@ -9,7 +9,8 @@ A custom channel gives the agent its own HTTP surface. You get routes
 with validated payloads, sessions keyed to something in your domain (a
 thread, a ticket, a PR), and replies delivered back to the caller. The
 [Slack](./slack.md) and [GitHub](./github.md) packs build on this
-mechanism. This page is the mechanism itself.
+mechanism. The [GitLab](./gitlab.md) and [Bitbucket](./bitbucket.md) packs
+use it too. This page is the mechanism itself.
 
 ## What you already have
 
@@ -463,6 +464,7 @@ from any PR you can read. See the [GitHub guide](./github.md).
 Continue with these pages:
 
 - [Channels reference](../reference/channels.md): the full authoring API
-- [GitHub](./github.md) and [Slack](./slack.md): the packaged channels
+- [GitHub](./github.md), [GitLab](./gitlab.md),
+  [Bitbucket](./bitbucket.md), and [Slack](./slack.md): the packaged channels
 - [Sessions and streaming](../reference/sessions.md): events your
   channel can subscribe to

package/docs/hillclimbing.md

@@ -72,9 +72,9 @@ Pin the input first. A moving fixture is noise. For GitHub agents, use `agent-sd
 
 ## How do I lock a hillclimb improvement with an eval?
 
-Every kept change needs an eval that would have failed before the change: a tool-choice gate, an `action.result` count bound, or an output-shape check. Run `agent-sdk eval --dir . --json` between rounds. Never weaken an existing gate to pass the round.
+Every kept change needs an eval that would have failed before the change: a tool-choice gate, a `maxToolCalls` bound, or an output-shape check. Run `agent-sdk eval --dir . --json` between rounds. Never weaken an existing gate to pass the round.
 
-Details live in [Evals](./evals.md). The evals skill will author the case with you.
+Details live in [Keep improvements with regression evals](./evals.md#keep-improvements-with-regression-evals). The evals skill will author the case with you.
 
 ## What habits help hillclimbing stay reliable?
 

package/docs/reference/channels.md

@@ -8,7 +8,8 @@ description: "The authoring reference for defineChannel, the built-in HTTP chann
 A channel is the surface an agent lives on. The built-in HTTP session
 channel is always mounted. Custom channels declare their own routes
 under `/v1/channels/<id>`. The Slack and GitHub packs are prebuilt
-channels with platform transports. This page is the authoring reference;
+channels with platform transports. GitLab and Bitbucket packs cover their
+hosted and self-managed products. This page is the authoring reference;
 for the walkthrough, see the [Webhooks guide](../guides/webhooks.md).
 
 ## Built-in HTTP channel
@@ -134,7 +135,7 @@ Handlers receive the Fetch `Request` and an args object:
 `workspaceFiles`, `workspaceDir`, `cloud` (attach cloud repos for this
 session), `auth` (defaults to the request principal), `state` (starting
 channel state for new sessions), `title` (session display title), and
-`purpose` (`"eval"` skips sticky A/B enrollment).
+`purpose` (`"eval"` marks the session as regression traffic).
 
 ## Events
 
@@ -215,7 +216,19 @@ model turn), `{ task }` (host work), or `null`, and CLI tooling for
 replay and live forwarding. Author `agent/channels/github.ts` with
 `githubChannel()`. Opt-in `progress.commitStatus` and `progress.banner`
 converge a merge-box check and sticky PR comment from default stream
-events. Guide: [GitHub](../guides/github.md).
+events. Supports GitHub.com and GitHub Enterprise Server. Guide:
+[GitHub](../guides/github.md).
+
+**GitLab** (`@cursor/july/channels/gitlab`): verified project hooks for
+merge requests, notes, pipelines, pushes, and custom event types. Supports
+GitLab.com and self-managed GitLab. Author `agent/channels/gitlab.ts` with
+`gitlabChannel()`. Guide: [GitLab](../guides/gitlab.md).
+
+**Bitbucket** (`@cursor/july/channels/bitbucket`): verified repository hooks
+for pull requests, comments, pushes, and custom event types. Supports
+Bitbucket Cloud and Bitbucket Data Center through one normalized hook API.
+Author `agent/channels/bitbucket.ts` with `bitbucketChannel()`. Guide:
+[Bitbucket](../guides/bitbucket.md).
 
 **Deployments** (`@cursor/july/channels/deployments`): pull deploy
 events. Declare `events` and handle each one in `onEvent`. Each event

package/docs/reference/cli.md

@@ -366,8 +366,10 @@ agent-sdk eval status <evalId> --prod --slug pr-approver
 agent-sdk eval cancel <evalId> --prod --slug pr-approver
 ```
 
-`eval` runs `evals/**/*.eval.{ts,js}` on an ephemeral server or against
-`--url`. Select one or more exact case IDs, file ID prefixes, or tags.
+`eval` runs `evals/**/*.eval.{ts,js}` on an ephemeral server. With
+`--prod` or `--url`, the target server runs its own evals as a
+server-side batch. Select one or more exact case IDs, file ID prefixes,
+or tags.
 Omit selectors to run all cases. Repeated `--tag` flags use OR matching.
 
 An eval run requires `evals/evals.config.{ts,js}` with `maxConcurrency`
@@ -378,13 +380,13 @@ between 1 and 200. Timeout priority is the case's `timeoutMs`, the CLI's
 | --- | --- |
 | `--list` | Print discovered cases without running. `--list --json` prints them as an array. |
 | `--tag <tag>` | Run cases with this tag. Repeated flags use OR matching. |
-| `--json` | Print `{ ok, passed, failed, results }`. |
+| `--json` | Print `{ ok, passed, failed, scored, skipped, strict, results }`; see [Run evals in CI](../evals.md#run-evals-in-ci) for the result shape. |
 | `--verbose` | Stream `t.log` lines and reply snippets. |
 | `--no-stream` | Hide live progress on stderr. |
 | `--strict` | Exit `1` when a scored case misses a soft threshold. |
 | `--max-concurrency <n>` | Override `maxConcurrency` from `evals.config.ts`. |
 | `--junit <path>` | Write JUnit XML for CI annotations. |
-| `--artifacts <dir>` | Write run artifacts here. The default is a timestamped directory under `<state-root>/evals/`. |
+| `--artifacts <dir>` | Write run artifacts here. The default is a timestamped directory under `evals/` in the project state directory (not affected by `--state-root`). |
 | `--no-artifacts` | Skip run artifacts. |
 | `--skip-report` | Ignore reporters from `evals.config.ts` and eval files. |
 | `--out <path>` | Also write the full results JSON to this path (also for `eval status <evalId>`). |

package/docs/reference/extensions.md

@@ -59,7 +59,6 @@ namespace:
 | `subagents/<id>/` | subagent `<ns>__<id>` |
 | `instructions.md` / `.ts` / dir | appended to the agent's system prompt |
 | `sandbox/workspace/**` | seeded into each local session workspace |
-| `ab.ts` / `ab/<name>.ts` | A/B experiment `<ns>__<name>` |
 | `artifacts.ts` | artifact kinds `<ns>__<kind>` |
 
 The root agent still needs its own `instructions.md`. Extension
@@ -76,7 +75,6 @@ or is outside discovery:
 | `agent.ts` | One `defineAgent` runtime per agent |
 | `storage.ts` | One `host.kv` / `host.files` backend |
 | `otel.ts` | One OTLP exporter |
-| `ab.config.ts` | One experiment-platform config; `ab.ts` / `ab/` still merge |
 | `playground/` | Custom chips are a Vite glob of the agent tree, not a discovery walk |
 | `extensions/` | Nested mounts are not loaded |
 | `sandbox.ts` | Custom sandbox backends stay on the agent |
@@ -117,7 +115,6 @@ it alive.
 | `schedules/<name>.ts` | `disableSchedule()` |
 | `subagents/<id>.ts` | `disableSubagent()` |
 | `instructions.ts` | `disableInstructions()` |
-| `ab.ts` / `ab/<name>.ts` | `disableAB()` |
 | `artifacts.ts` | `disableArtifacts()` |
 
 `disable()` is the same brand as the slot helpers above and works in

package/docs/reference/hooks.md

@@ -88,7 +88,7 @@ exported from `@cursor/july`.
 
 | Member | What it is |
 | --- | --- |
-| `ctx.session` | Read-only session info: `id`, `channelId`, `mode` (`chat` or `task`), `purpose` (`live` or `eval`), `auth`, plus `title`, `sdkAgentId`, and `abs` when set |
+| `ctx.session` | Read-only session info: `id`, `channelId`, `mode` (`chat` or `task`), `purpose` (`live` or `eval`), `auth`, plus `title` and `sdkAgentId` when set |
 | `ctx.agent` | `{ name }` of the agent the event belongs to |
 | `ctx.channel` | `{ id, continuationToken }`. The token is `null` when the session can't take follow-ups |
 | `ctx.host.kv` | Durable JSON, shared by every session of the agent; the [storage backend](../storage.md#author-kv-ctx-host-kv) decides whether it survives a hosted replace. Prefix keys with `ctx.session.id` for per-session state |
@@ -119,17 +119,17 @@ Each event reaches a hook at most once. A restart doesn't replay the log
 into hooks, so a mirror needs no dedupe, and the event log rather than
 the hook's copy is the source of truth.
 
-## Hooks, channel events, evals, or A/B?
+## Hooks, channel events, or evals?
 
 All of them consume the same stream, for different jobs:
 
-| | Hooks | Channel `events` | Evals | A/B (`defineAB`) |
-| --- | --- | --- | --- | --- |
-| Scope | every session of the agent | sessions the channel owns | one test turn | every live session; enrollment at creation, metrics on each turn |
-| Job | observe: audit, metrics, mirrors, derived state | deliver: replies back to the channel's surface | assert: gates over the trajectory | compare: sticky arms, then fold the stream into `onSample` metrics |
-| Context | `ctx.host`, `ctx.artifacts`, session info | `channel.state`, `setContinuationToken`, `ctx.host`, session info | the `t` assertion helpers | per-session samples in `onSample` |
-| Can affect the run | no | yes, it owns the surface | n/a | yes through arm instructions or `session.abs`; collection is observe-only |
-| Authored at | `agent/hooks/*.ts` | channel config | `evals/**/*.eval.ts` | [`agent/ab.ts` or `agent/ab/*.ts`](../ab.md) |
+| | Hooks | Channel `events` | Evals |
+| --- | --- | --- | --- |
+| Scope | every session of the agent | sessions the channel owns | one test turn |
+| Job | observe: audit, metrics, mirrors, derived state | deliver: replies back to the channel's surface | assert: gates over the trajectory |
+| Context | `ctx.host`, `ctx.artifacts`, session info | `channel.state`, `setContinuationToken`, `ctx.host`, session info | the `t` assertion helpers |
+| Can affect the run | no | yes, it owns the surface | n/a |
+| Authored at | `agent/hooks/*.ts` | channel config | `evals/**/*.eval.ts` |
 
 ## When not to use a hook
 
@@ -141,7 +141,6 @@ All of them consume the same stream, for different jobs:
 | Block, approve, or rewrite a tool call | [`needsApproval`](./tools.md#gate-a-tool-on-human-approval) on the tool |
 | Act on the final assistant text, or fail a bad turn | [`defineResult`](./result.md) |
 | Gate a change on behavior | [Evals](../evals.md) |
-| Compare two prompts on live traffic | [`defineAB`](../ab.md) |
 
 ## Patterns
 
@@ -267,5 +266,3 @@ Continue with these pages:
 - [Deployment](../deployment.md#observability): runtime logs and export
   paths
 - [Channels](./channels.md#events): the delivery-side counterpart
-- [Live A/B metrics](../ab.md): sticky variants over the same event
-  stream

package/docs/reference/http-api.md

@@ -152,12 +152,11 @@ These read-only routes describe the running agent.
 
 | Route                  | What it does                                                                                                                                                                             |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `GET /v1/info`         | The discovered surface: model, tools, skills, MCP connections, subagents, channels and routes (with schemas), schedules, hooks, A/B experiments, diagnostics |
+| `GET /v1/info`         | The discovered surface: model, tools, skills, MCP connections, subagents, channels and routes (with schemas), schedules, hooks, diagnostics |
 | `GET /v1/tools`        | The live tool catalog: authored server tools plus advertised MCP passthroughs under model-facing names, as light `{ name, title?, source? }` entries. `session` / `continuationToken` query parameters bind the listing to a session identity (advertised inventories can be tenant-scoped); a connection whose listing fails is skipped and reported in `connectionErrors` |
 | `GET /v1/tools/:name`  | One catalog tool's full description: description, execution, `needsApproval`, `effect`, input and output schemas, source connection. Same session binding as the listing; unknown names get `404` with the available names |
 | `GET /v1/health`       | Per-agent liveness, no auth                                                                                                                                                              |
 | `GET /v1/logs?after=N` | Recent server log lines, with a polling cursor                                                                                                                                           |
-| `GET /v1/abs`          | [Live A/B metrics](../ab.md): per-session assignments and aggregate arm totals                                                                                                           |
 
 ## Artifacts
 
@@ -216,7 +215,7 @@ the final `completed` or `failed` status. Batch errors appear on the
 snapshot returned by the poll. Entries within `filterIds` and `tags`
 use OR semantics. When both fields are present, a case must match one
 entry from each field. Listed runs persist across restarts when storage is configured; see
-[Storage](../storage.md#eval-and-a-b-tables). Otherwise they are
+[Storage](../storage.md#eval-table). Otherwise they are
 process-memory only.
 
 ## Dev-mode routes

package/docs/reference/playground.md

@@ -37,8 +37,6 @@ Use the playground to chat, try channel routes, and inspect sessions.
   an [extension](./extensions.md) cannot contribute them.
 - **Raw events pane**: flip it on to inspect the event stream.
 - **Logs tab**: recent server log lines, polled from `GET /v1/logs`.
-- **A/Bs tab**: per-session and aggregate
-  [live A/B metrics](../ab.md) from `GET /v1/abs`.
 
 In multi-agent mode each agent has its own playground at
 `/<slug>/playground`, and `/` is an index of them all.
@@ -61,5 +59,3 @@ Continue with these pages:
 - [Sessions and streaming](./sessions.md): the streams it renders
 - [Human-in-the-loop](../guides/human-in-the-loop.md): the approval
   buttons in context
-- [Live A/B metrics](../ab.md): the assignments and results in the A/Bs
-  tab

package/docs/reference/project-layout.md

@@ -11,8 +11,7 @@ how the Agent SDK loads it.
 
 ## Folder structure
 
-For the capabilities below, identity usually comes from the path. A/B
-experiments can override their file-derived name.
+For the capabilities below, identity comes from the path.
 
 | Path | Resolves to |
 | --- | --- |
@@ -24,8 +23,6 @@ experiments can override their file-derived name.
 | `agent/extensions/ci.ts` | extension mount `ci`; its contributions become `ci__<name>` |
 | `agent/extensions/notion.ts` | Cursor plugin mount `notion` (`cursorPlugin`); its skills, agents, and MCP servers become `notion__<name>` |
 | `agent/channels/drive.ts` | channel `drive`, routes under `/v1/channels/drive` |
-| `agent/ab.ts` | A/B experiment `ab` unless `name` overrides it |
-| `agent/ab/concise.ts` | A/B experiment `concise` unless `name` overrides it |
 
 The root agent takes its name from `package.json` `name`, falling back
 to the directory name. When serving multiple agents, the slug is the
@@ -77,8 +74,6 @@ Each path maps to a capability and a reference page.
 | `agent/channels/*.ts` | HTTP surfaces beyond the built-in session API; `slack.ts` and `github.ts` use the platform packs | [Channels](./channels.md) |
 | `agent/hooks/*.ts` | Observe-only event subscribers, never fatal | [Hooks](./hooks.md) |
 | `agent/otel.ts` | `defineOtel` OTLP export (traces, metrics, optional logs) | [OpenTelemetry](../guides/opentelemetry.md) |
-| `agent/ab.ts`, `agent/ab/*.ts` | `defineAB` experiments with sticky variants and live metrics | [Live A/B metrics](../ab.md) |
-| `agent/ab.config.ts` | `defineABConfig` shared A/B settings | [Live A/B metrics](../ab.md) |
 | `agent/storage.ts` | `defineStorage` backend for the durable `host.kv` / `host.files` APIs | [Storage](../storage.md) |
 | `agent/artifacts.ts` | `defineArtifacts` kinds, the `tag_artifact` opt-in, and retention | [Artifacts](./artifacts.md) |
 | `agent/result.ts` | `defineResult` host `commit` on the final assistant text | [Turn result](./result.md) |
@@ -115,6 +110,4 @@ Continue with these pages:
 
 - [Agent config](./agent-config.md): the runtime config at the root
 - [Tools](./tools.md): add typed actions under `agent/tools/`
-- [Live A/B metrics](../ab.md): compare variants from `agent/ab.ts` or
-  `agent/ab/`
 - [Concepts](../concepts.md): why the filesystem is the interface

package/docs/reference/sessions.md

@@ -80,7 +80,7 @@ within one session. The `at` field is an ISO-8601 timestamp.
 
 | Phase | Events | What they tell you |
 | --- | --- | --- |
-| Session | `session.started`, [`ab.assigned`](../ab.md#assign-sticky-variants), `session.waiting`, `session.completed`, `session.failed` | Session creation, A/B enrollment, readiness, and task completion |
+| Session | `session.started`, `session.waiting`, `session.completed`, `session.failed` | Session creation, readiness, and task completion |
 | Agent | `agent.bound` | Cloud conversation URL |
 | Input | `message.received` | A user message was accepted |
 | Turn | `turn.queued`, `turn.started`, `turn.completed`, `turn.failed` | Queue position under a [`maxRunningTurns` cap](./agent-config.md#concurrency), then turn status, final result, and token usage |
@@ -164,5 +164,4 @@ view.
 
 - [HTTP API](./http-api.md)
 - [Hooks](./hooks.md)
-- [Live A/B metrics](../ab.md)
 - [How the Agent SDK works](../concepts.md)

package/docs/skills/index.md

@@ -1,6 +1,6 @@
 ---
 title: "Coding-agent skills"
-description: "Task guides that ship with the Agent SDK for scaffolding, evals, channels, and hillclimbing."
+description: "Task guides that ship with the Agent SDK for scaffolding, deployment, evals, channels, and hillclimbing."
 ---
 
 # Coding-agent skills
@@ -17,10 +17,10 @@ to use each one.
 | [framework-map](./framework-map.md) | Learn the project layout and runtimes |
 | [create-agent](./create-agent.md) | Scaffold and verify a new agent |
 | [evals](./evals.md) | Write fixtures and regression checks |
-| [ab](./ab.md) | Compare variants on live traffic |
 | [otel](./otel.md) | Export OpenTelemetry traces |
 | [hillclimb](./hillclimb.md) | Improve an agent against fixed inputs |
 | [github](./github.md) | Add GitHub webhooks and replay events |
 | [setup-slack](./setup-slack.md) | Connect an agent to Slack |
 | [mcp-auth](./mcp-auth.md) | Authorize host MCP OAuth |
+| [deploy](./deploy.md) | Deploy with an attached service account |
 | [debug](./debug.md) | Diagnose a local run |

package/docs/storage.md

@@ -6,8 +6,8 @@ description: "Point the Agent SDK's durable storage at a backend you own with de
 # Storage
 
 The Agent SDK owns durable storage for sessions, continuation tokens,
-reminders, playground eval history, and live A/B samples. It chooses the
-keys, when to read and write, and how to restore after restart.
+reminders, and playground eval history. It chooses the keys, when to
+read and write, and how to restore after restart.
 
 The Agent SDK owns key encoding. Backends must accept the keys they are
 given. Do not fail `put` to enforce a shorter cap.
@@ -41,9 +41,9 @@ export default defineStorage({
 ## Which fields to provide
 
 Implement the small KV core (`put`/`get`/`delete`/`list` plus the `cas`
-group) and you get **full functionality**: eval-run and A/B history are
-derived over the core automatically. The dedicated `evals` / `abs` groups
-are backend-native optimizations, not required-or-lose-history hooks.
+group) and you get **full functionality**: eval-run history is derived
+over the core automatically. The dedicated `evals` group is a
+backend-native optimization, not a required-or-lose-history hook.
 
 | Field | Required | Role |
 | --- | --- | --- |
@@ -54,36 +54,28 @@ are backend-native optimizations, not required-or-lose-history hooks.
 | `delete` | For cleanup | Remove a key |
 | `name` | No | Label surfaced on `GET /v1/info` diagnostics |
 | `policy` | No | Timing knobs; see [Policy](#policy) |
-| `evals` | No | Backend-native eval-runs table; derived over the core when omitted. See [Eval and A/B tables](#eval-and-a-b-tables) |
-| `abs` | No | Backend-native A/B metrics table; derived over the core when omitted. See [Eval and A/B tables](#eval-and-a-b-tables) |
+| `evals` | No | Backend-native eval-runs table; derived over the core when omitted. See [Eval table](#eval-table) |
 
 A throwing `put` is logged and dropped. It never fails a turn. When
 resolving a missing continuation token, a throwing `get` fails the
 follow-up so a store outage does not open a new session. Return
 `undefined` only for a real miss.
 
-## Eval and A/B tables
+## Eval table
 
-Two dedicated table groups carry structured rows instead of opaque KV
-values. Both are **optional optimizations**: when a group is not
-authored, `defineStorage` derives it over the KV core, so a backend that
-implements only the core loses nothing. Author a group only when the
-backend has a better native shape (a real database table, an analytics
-pipeline). The built-in `fileKv` and `cursorHostedStorage` both do.
+The dedicated `evals` table group carries structured rows instead of
+opaque KV values. It is an **optional optimization**: when the group is
+not authored, `defineStorage` derives it over the KV core, so a backend
+that implements only the core loses nothing. Author the group only when
+the backend has a better native shape (a real database table, an
+analytics pipeline). The built-in `fileKv` and `cursorHostedStorage`
+both do.
 
 `evals` keeps playground eval batches across restarts (`put`, `delete`,
 `list` over run snapshots keyed by `runId`). A core missing `delete` or
 `list` leaves eval history in memory until restart.
 See [Evals](./evals.md#configure-eval-runs).
 
-`abs` exports live A/B metrics: `putSample` appends one cumulative
-metric sample per enrolled experiment on each completed or failed turn;
-optional `putSnapshot` / `getSnapshot` store and serve back the latest
-aggregate so a replacement host can still serve the A/Bs surface.
-`putSample` and `putSnapshot` need only core `put`; `getSnapshot` needs
-core `get`. Session event logs remain the assignment source of truth
-either way. See [Live A/B metrics](./ab.md).
-
 ## Policy
 
 Two knobs change behavior:
@@ -118,8 +110,7 @@ With `get` and `list`, serve can rebuild local state from your store:
 - At startup, the Agent SDK loads recent sessions up to the restore caps.
 - On demand, a missing continuation token resolves through the store
   and resumes that session.
-- Playground eval history and A/B aggregates can load from the same
-  sink.
+- Playground eval history can load from the same sink.
 
 A turn in flight at crash time is not replayed. The next follow-up
 resumes from the last flushed state.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cursor/july",
-  "version": "0.1.108",
+  "version": "0.1.109",
   "description": "(early alpha) Filesystem-first framework for defining Cursor agents as markdown and TypeScript and serving them over channels with the Cursor SDK.",
   "license": "SEE LICENSE IN LICENSE.md",
   "repository": {
@@ -214,12 +214,6 @@
       "import": "./dist/evals/loaders.js",
       "default": "./dist/evals/loaders.js"
     },
-    "./ab": {
-      "anysphere-source": "./src/ab.ts",
-      "types": "./dist/ab.d.ts",
-      "import": "./dist/ab.js",
-      "default": "./dist/ab.js"
-    },
     "./artifacts": {
       "anysphere-source": "./src/artifacts.ts",
       "types": "./dist/artifacts.d.ts",