Initial Situation

dp report forced operators to provide --title and --body before it could create a report. That made the command feel like hand-authoring a maintainer issue instead of reporting raw friction.

Issue

Issue #22 asks for AI-generated report titles and an implicit body. The operator should be able to provide raw report text and structured context, then let Harness generate the final title/body.

Plan

1. Make title and body optional in the shared HarnessReportInput schema.
2. Add raw context fields used by the CLI report flow: area, skillPack, command, expected, actual, steps, and labels.
3. Update dp report to accept --message as the primary report input and keep --title / --body as optional compatibility hints.
4. Move final title/body generation into the API report submit path.
5. Use deterministic fallback title/body for public CLI submissions. Use AI SDK with OpenRouter only for authenticated backoffice operator requests when OPENROUTER_API_KEY is configured.
6. Validate with CLI, contract, and API tests.

Result

Resolved. The CLI now submits report drafts to the control-plane API; the API validates raw context and generates final title/body before persistence and GitHub issue creation.