ci: enable Cursor Max Mode for cursor-agent workflow

[rgarcia]

Problem

The update-cli-coverage.yml workflow runs cursor-agent with --model ${{ vars.CURSOR_PREFERRED_MODEL }} (currently claude-opus-4-8-xhigh). That model requires Cursor Max Mode, so CI fails with Max Mode Required.

A fresh cursor-agent install defaults to maxMode=false, and it must be explicitly enabled via cli-config.json.

Fix

Add an "Enable Cursor Max Mode" step immediately after the Cursor CLI install step and before the agent invocation:

• Writes {"maxMode": true} to cli-config.json.
• Pins CURSOR_CONFIG_DIR and propagates it via $GITHUB_ENV. GitHub-hosted runners set XDG_CONFIG_HOME=/home/runner/.config, and cursor-agent resolves its config dir as CURSOR_CONFIG_DIR || $XDG_CONFIG_HOME/cursor || ~/.cursor. Without pinning CURSOR_CONFIG_DIR, a ~/.cursor/cli-config.json write would be ignored.

This mirrors the proven fix already applied in kernel/kernel.

Requirements

The CURSOR_API_KEY secret used by the workflow must be Max-Mode-entitled for this to take effect.

Note

This repo is auto-generated by Stainless; only the workflow YAML was modified.

Made with Cursor

---

Note

Low Risk
Workflow-only change; no application or runtime behavior beyond fixing CI agent configuration.

Overview
Fixes update-cli-coverage CI failures when cursor-agent runs with a model that requires Max Mode (e.g. claude-opus-4-8-xhigh via CURSOR_PREFERRED_MODEL), which errors with Max Mode Required on a fresh install.

Adds an Enable Cursor Max Mode step right after installing the Cursor CLI: writes {"maxMode": true} to cli-config.json under $HOME/.cursor and sets CURSOR_CONFIG_DIR in $GITHUB_ENV so cursor-agent picks up that config instead of ignoring it when runners use XDG_CONFIG_HOME.

^{Reviewed by Cursor Bugbot for commit 9726171. Bugbot is set up for automated code reviews on this repo. Configure here.}

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: PR modifies CI workflow configuration for cursor-agent, but unclear which service in the kernel monorepo is implicated; please clarify the affected service or opt in manually.

To monitor this PR anyway, reply with @firetiger monitor this.