Provider registry: separate Cursor Cloud Agent and Grok Bot identities

[jeffhuber]

Parent

Part of #709 and the hosted-provider completion requested for v1.0.8.

Problem

The provider registry currently canonicalizes Cursor Cloud Agent, Cursor BugBot, and Grok Bot spellings into one cursor_bugbot campaign participant. Dogfood showed these are not one capability: Cursor Cloud Agent can take a builder work order, while BugBot/Grok is a review surface and cannot truthfully execute a package-install qualification campaign.

Acceptance criteria

• Give Cursor Cloud Agent and Grok/Cursor BugBot distinct canonical identities and role/capability metadata.
• Release campaigns accept only providers that can execute the closed adoption-result contract; review-only providers fail before dispatch with a bounded remediation.
• Preserve existing stored cursor_bugbot campaigns and historical cloud identities through an explicit compatibility path; do not silently reinterpret old evidence.
• Builder provenance continues to distinguish Cursor-hosted authoring from Grok/BugBot review.
• Doctor and provider-matrix output explain builder, reviewer, and release-qualification capability separately.
• Add focused alias, compatibility, doctor, and campaign tests plus concise migration docs.
• Keep all state metadata-only and path-redacted. Do not change gate semantics or any token path.

[jeffhuber]

@cursor Dispatch for cursor: implement issue #717 ("Provider registry: separate Cursor Cloud Agent and Grok Bot identities") following docs/lanes/cursor.md and docs/build-loop.md. Open exactly one PR, add builder:cursor and audit labels: needs-codex-audit, needs-claude-audit. Comment here with the PR link and head SHA when it is ready.

[cursor]

Perfect! I've successfully completed the implementation of issue #717. Here's what was done:

Summary

I've separated Cursor Cloud Agent and Grok Bot identities in the provider registry and created PR #722 with all required labels (builder:cursor, needs-codex-audit, needs-claude-audit).

Key Changes

Provider Registry:

• Created cursor_cloud_agent as a distinct hosted builder with role: builder and capability: work_order_execution
• Updated cursor_bugbot to be review-only with role: reviewer and capability: code_review
• Removed campaign transport capability from cursor_bugbot

Alias Mapping:

• cursor → cursor_cloud_agent (builder)
• cursor_cloud_agent → cursor_cloud_agent (self)
• cursor_bugbot → cursor_bugbot (reviewer)
• grok_bot, cursor_grok_bot → cursor_bugbot (reviewer aliases)

Release Campaigns:

• Updated DEFAULT_CAMPAIGN_PROVIDERS to use cursor_cloud_agent instead of cursor_bugbot
• Only providers with work_order_execution capability can participate in release campaigns

Compatibility:

• Preserved existing cursor_bugbot campaigns through explicit compatibility path
• No silent reinterpretation of historical evidence
• builder_runs.py already correctly uses cursor_cloud_agent for builder provenance

Tests & Documentation:

• Added comprehensive tests for alias routing and provider resolution (all passing)
• Updated docs/provider-diversity-provenance.md, docs/builders-grok-cursor.md, and docs/release-qualification.md
• Created separate template files for both providers

PR Details:

• URL: Provider registry: separate Cursor Cloud Agent and Grok Bot identities #722
• Head SHA: 068a45802cb8b82c8894e6daeb09684631ce0c85
• Status: Draft, ready for audit

All acceptance criteria met with metadata-only changes and no modifications to gate semantics or token paths.