ci: enable Cursor Max Mode for cursor-agent workflow

[rgarcia]

Summary

The fix-ci.yaml workflow invokes cursor-agent with --model ${{ vars.CURSOR_PREFERRED_MODEL }} (claude-opus-4-8-xhigh), which requires Cursor Max Mode. CI was failing with Max Mode Required.

A fresh cursor-agent install defaults to maxMode=false, and the setting must be persisted to the CLI config file. On GitHub-hosted runners, 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 alone is ignored unless CURSOR_CONFIG_DIR is also pinned.

Fix

Adds an Enable Cursor Max Mode step immediately after the Cursor CLI install step:

• Writes {"maxMode": true} to cli-config.json.
• Pins CURSOR_CONFIG_DIR via $GITHUB_ENV so the agent step reads the right config.

Note

This also requires the CURSOR_API_KEY account to be Max-Mode entitled.

Made with Cursor

---

Note

Low Risk
CI-only workflow configuration with no application or security logic changes; depends on Max Mode entitlement for the API key.

Overview
The Fix CI Failures workflow now turns on Cursor Max Mode right after installing the Cursor CLI so cursor-agent can run with the configured high-tier model (CURSOR_PREFERRED_MODEL) without hitting Max Mode Required.

The new step writes {"maxMode": true} to cli-config.json under $HOME/.cursor and sets CURSOR_CONFIG_DIR in $GITHUB_ENV, so the agent step picks up that config on GitHub-hosted runners (where the default XDG config path would otherwise ignore ~/.cursor alone).

^{Reviewed by Cursor Bugbot for commit 49e6711. 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 configuration for cursor-agent workflow, but it's unclear which service in the kernel mono repo is affected; please clarify the implicated service or opt in manually.

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