ci: enable Cursor Max Mode for cursor-agent workflow

[rgarcia]

Problem

The update-cli-coverage workflow invokes 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. The setting must be written to the CLI config file (cli-config.json, key {"maxMode": true}). 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. So writing ~/.cursor/cli-config.json is ignored unless CURSOR_CONFIG_DIR is also pinned.

Fix

Adds an Enable Cursor Max Mode step immediately after the Cursor CLI install step that writes {"maxMode": true} to $HOME/.cursor/cli-config.json and pins CURSOR_CONFIG_DIR via $GITHUB_ENV so later steps (the agent invocation) read the right config.

Note: this requires CURSOR_API_KEY to be entitled for Max Mode.

Made with Cursor

---

Note

Low Risk
Workflow-only change with no application code; depends on CURSOR_API_KEY being entitled for Max Mode.

Overview
Adds an Enable Cursor Max Mode step to update-cli-coverage right after installing the Cursor CLI.

The step writes {"maxMode": true} to $HOME/.cursor/cli-config.json and sets CURSOR_CONFIG_DIR in $GITHUB_ENV so cursor-agent picks up that config on GitHub-hosted runners (where default config paths would otherwise ignore ~/.cursor). This unblocks the workflow’s preferred model, which requires Max Mode.

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