[deep-report] Tighten vague ellipsis-heavy status messages in smoke-cursor.md

### Description
`.github/workflows/smoke-cursor.md` (lines 49, 51) uses vague, unfinished status messages with trailing ellipses: `run-started` reads "Cursor initializing... ... begins on this {event_type}..." and `run-failure` reads "...Cursor encountered unexpected challenges...". These read as filler rather than concrete status, and this workflow posts them frequently (every 2 days on schedule, plus on-demand). Flagged in the 2026-09-15 User Experience Analysis Report.

### Expected Impact
Clearer, more professional status messages for maintainers scanning PR/issue comments — failure messages point to run logs instead of trailing off.

### Suggested Fix
Update the `messages` block in `smoke-cursor.md`:
- `run-started`: "🖱️ [{workflow_name}]({run_url}) starting Cursor smoke test on this {event_type}."
- `run-failure`: "⚠️ [{workflow_name}]({run_url}) {status}. See run logs for details."

### Suggested Agent
Delight / docs-focused agent

### Estimated Effort
Quick (< 30 min)

### Data Source
DeepReport Intelligence Briefing analysis, 2026-09-15 cycle 3 — derived from User Experience Analysis Report - 2026-09-15 (#61155)

> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `api.anthropic.com`
>
> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "api.anthropic.com"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>

> Generated by [🔬 Deep Report](https://github.com/github/gh-aw/actions/runs/35007359021) · claude · agent · 221.8 AIC · ⌖ 11.2 AIC · ⊞ 12.8K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw%2Fdeep-report%22&type=issues)
> - [x] expires on Sep 17, 2026, 10:41 AM UTC-08:00

Open .github/workflows/smoke-cursor.md and inspect the messages block around lines 49 and 51. Replace the vague ellipsis-heavy run-started and run-failure wording with the concrete messages specified in the issue; done means both frequent workflow status messages are clear and point failures to run logs.

Written by the indexing model from the issue text.