Problem
The v1.1.1 Cursor Cloud Agent qualification proved that the GitHub transport, durable issue binding, and trusted-author posture work, but the first hosted reply improvised a report-shaped object instead of returning the closed code_mower.adoptionResult.v1 document. Code Mower correctly rejected it. A correction telling the agent to run the built-in release qualify command and wrap its output verbatim passed on the next attempt.
The current dispatch says to see the release-qualification documentation, but does not place the executable, schema-safe path directly in the comment the hosted agent receives.
Ask
- Make hosted release-campaign dispatch comments prescribe the exact candidate
code-mower release qualify command for the bound release tag, package spec, package source, qualification context, starting version, provider, and executor.
- Tell the provider to embed the generated output object unchanged in the
code_mower.releaseCampaignResult.v1 wrapper.
- Keep campaign identity and idempotency binding authoritative; do not accept loose aliases or normalize unsupported report fields.
- Add focused tests for cold-install and upgrade dispatches and for shell-safe comment rendering.
- Add one documentation line to the hosted-provider setup flow.
Privacy
No source, diffs, prompts, transcripts, issue-body text, raw stdout/stderr, auth output, local paths, or secrets may enter stored campaign evidence, Board, or uploads.
Discovered during the six-provider v1.1.1 campaign tracked by #820 and epic #816.
Problem
The v1.1.1 Cursor Cloud Agent qualification proved that the GitHub transport, durable issue binding, and trusted-author posture work, but the first hosted reply improvised a report-shaped object instead of returning the closed
code_mower.adoptionResult.v1document. Code Mower correctly rejected it. A correction telling the agent to run the built-inrelease qualifycommand and wrap its output verbatim passed on the next attempt.The current dispatch says to see the release-qualification documentation, but does not place the executable, schema-safe path directly in the comment the hosted agent receives.
Ask
code-mower release qualifycommand for the bound release tag, package spec, package source, qualification context, starting version, provider, and executor.code_mower.releaseCampaignResult.v1wrapper.Privacy
No source, diffs, prompts, transcripts, issue-body text, raw stdout/stderr, auth output, local paths, or secrets may enter stored campaign evidence, Board, or uploads.
Discovered during the six-provider v1.1.1 campaign tracked by #820 and epic #816.