Feature request: first-class flow for filing issues discovered mid-session (assistant-drafted, user-approved)

Motivation

When Claude itself diagnoses a harness or plugin defect mid-session, turning that diagnosis into an actionable report is entirely manual today. Concrete case: #79395 (silent Workflow stall). The assistant had already diagnosed the failure from agent transcripts, but filing it required: checking for gh (not installed), falling back to the raw GitHub API with credentials extracted via git credential fill, hand-writing environment info (CLI version, entrypoint, OS, model) that the harness already knows, and manually deciding which repository the report belongs to. Every piece of evidence was already in the session; it all had to be retyped.

Proposal

A first-class "report an issue from this session" flow:

• A /report-issue command (or a dedicated tool) that automatically collects environment (CLI version, entrypoint, OS, model, active plugins and versions), lets the assistant attach a sanitized evidence bundle (relevant transcript or workflow-journal excerpts, script hashes, timing data), and pre-fills a draft against the target repo's issue template.
• Proactive offers: when the assistant detects a probable harness bug (silent tool failures, contract violations, watchdog-less stalls), it can offer "file this as an issue?" with the draft ready. Submission is always user-approved, never automatic.
• Routing: harness issues go to anthropics/claude-code; plugin issues go to the plugin's declared repository. Plugin manifests should be able to declare a bugs/repository URL for this; in my case the correct target had to be dug out of known_marketplaces.json by hand.
• Privacy: an explicit redaction pass plus a full preview; nothing leaves the machine without the user seeing exactly what will be posted.

Why it pays off

Session-diagnosed defects are the highest-signal bug reports available (exact repro context, transcripts, timings), and today most of them are lost to friction. Lowering the cost from "manual API archaeology" to "review and approve a prefilled draft" should measurably raise the quality and volume of actionable reports.

Related: #79395