Fix spurious check_token_telemetry failure in Smoke Cursor workflow

[Copilot]

The check_token_telemetry job in the Smoke Cursor workflow was failing on every run because token_usage.jsonl was always empty for Cursor.

• Root cause: the Cursor engine calls its own API (api2.cursor.sh) directly rather than through gh-aw's universal LLM provider proxy, so it never produces token_usage.jsonl. The telemetry check assumes proxy-routed engines and was misapplied here.
• Fix: removed the shared/token-telemetry-check.md import from smoke-cursor.md, aligning it with shared/aider.md and other direct-API engines that already omit this check for the same reason.
• Regenerated smoke-cursor.lock.yml via gh aw compile, which drops the now-unneeded check_token_telemetry job.

• Fixes [aw] Failed jobs: Smoke Cursor #57302

[pelikhan]

@copilot reconfigure cursor.md to
Go through api-proxy

[Copilot]

@copilot reconfigure cursor.md to
Go through api-proxy

Looked into this before making further changes: cursor-agent (the underlying CLI) has no supported way to redirect its API calls to a custom/local base URL — it always talks directly to Cursor's own backend (api2.cursor.sh) using CURSOR_API_KEY, unlike the openai-compat CLIs (crush, deepseek-harness, aider, etc.) that discover an AWF endpoint via /reflect and point their own provider config at it.

Separately, even if cursor-agent could be redirected, the AWF api-proxy's /reflect and token-usage parsing (actions/setup/js/awf_reflect.cjs) currently only understands the github/openai/anthropic protocols — there's no Cursor-specific request/response parser.

So routing Cursor through api-proxy isn't achievable from cursor.md alone; it would need upstream support in both cursor-agent (custom endpoint) and the github/gh-aw-firewall api-proxy (Cursor protocol parsing). Given that, I've kept the fix as removing the token-telemetry-check import for now (matching the fact that this check is only valid for proxy-routed engines). Happy to file a follow-up issue against gh-aw-firewall if you'd like to track adding Cursor protocol support there.

[github-actions]

Great work, @Copilot! 🎉 This fix correctly addresses the root cause of the spurious check_token_telemetry failures in the Smoke Cursor workflow. The analysis is clear: Cursor's direct API routing bypasses the LLM provider proxy, so the telemetry check does not apply—just like with Aider and other direct-API engines.

The changes are focused and well-explained:

• Removed the misapplied telemetry import from smoke-cursor.md
• Regenerated smoke-cursor.lock.yml via gh aw compile
• Aligned with the existing pattern used by similar engines

The PR looks ready for review and merge. Nice alignment with the project's workflow patterns!

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• github.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.com"

See Network Configuration for more information.

Generated by ✅ Contribution Check · copilot · auto · 39.6 AIC · ⌖ 7.36 AIC · ⊞ 9.3K · ◷

[github-actions]

Category: bug | Risk: medium | Score: 46/100 (impact 16/50, urgency 14/30, quality 16/20) | Action: defer | Batch: workflow-automation

Generated by 🔧 PR Triage Agent · copilot · mai10 · 35.4 AIC · ⌖ 2.7 AIC · ⊞ 15.2K · ◷

[github-actions]

Category: bug | Risk: medium | Score: 46/100 (impact 16/50, urgency 14/30, quality 16/20) | Action: defer | Batch: workflow-automation

Generated by 🔧 PR Triage Agent · copilot · mai10 · 35.4 AIC · ⌖ 2.7 AIC · ⊞ 15.2K · ◷