Add one-step report command that exports and submits diagnostics

Summary

Migrated/adapted from MoonshotAI/kimi-cli#2293 because Kimi CLI is evolving into Kimi Code CLI.

Kimi Code already has diagnostic/export work such as /export-debug-zip, but the user flow still appears to require a manual handoff: export a local bundle, find the right support channel, attach it, and describe the failure.

A one-step report command would make support reports more consistent while keeping the upload explicit and user-controlled.

Proposed UX

kimi report            # preview + confirm + submit diagnostic bundle
kimi report --dry-run  # generate the bundle locally only

Expected behavior:

• Reuse the existing debug/export bundle where possible.
• Include structured metadata: Kimi Code version, install source, OS, shell, provider/model, last error class, and redacted account/project/key identifiers when available.
• Show a clear preview/summary before any upload.
• Ask for explicit confirmation before sending anything.
• Upload to an official Moonshot support endpoint and return a report/ticket ID.
• Fall back to the local bundle path plus support contact if upload fails.

Why it matters

Most users will not complete a two-step export-and-email flow after an error. A single consent-based command would preserve privacy while giving maintainers consistent reports that are easier to triage.

Related

• Original kimi-cli request: https://github.com/MoonshotAI/kimi-cli/issues/2293
• Related kimi-code privacy/export work: https://github.com/MoonshotAI/kimi-code/issues/495
• Related local diagnostics idea: https://github.com/MoonshotAI/kimi-code/issues/53

Start by locating the existing /export-debug-zip implementation and the CLI command registration, then review the related privacy/export work in issues #495 and #53. Done means a consent-based kimi report flow can preview and locally generate diagnostics, submit them to the official support endpoint, return a report ID, and provide a local fallback when upload fails.