fix(cloud): explain signed-out first-send refusal
A signed-out Cloud first send now keeps its stable not_signed_in refusal code while returning the actionable Cloud sign-in instructions as the failure message. The composer remains unlocked and the prompt stays available for retry or a different destination.
The native refusal previously sent the raw code as both code and message. The web progress card therefore had no recovery text and fell back to its generic failure copy.
Base: 5f937c4fc4ef776facb88382c6fb1973a0c9a766
Validation:
git diff --check- Added
CloudStartChatMachineTests.aSignedOutFirstSendCarriesActionableRecoveryCopy. - Fleet test/build not yet run; this PR is the focused repair from HQ #6236 brief 02.
Overlap/prior art: read and acknowledged all prior-art items for the two changed paths, including #32244, #32052, #31969, and #30002. No open PR changes this refusal mapping.
Agent session: agent session
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3-3x.png)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
A signed-out Cloud first send now keeps its stable not_signed_in refusal code but returns the actionable Cloud sign-in instructions as the failure message, so the web progress card shows recovery copy instead of the generic failure text. The composer stays unlocked and the prompt remains available for retry or a different destination. Adds a test covering the refusal message mapping.