[dkropachev]

Issue

Automatic bug reporting asks AI to repeat repository discovery, choose a destination and format the final issue body. Those mechanical steps make reports less consistent and consume investigation work that can be handled deterministically.

Fix

Capture private repository context before investigation, including pinned templates and guidance, label catalogs and bounded duplicate candidates. Keep evidence investigation, ownership explanations, template selection, duplicate assessment and narrative writing with AI. Derive the destination from the component and render and validate the completed draft in code.

Supported Markdown layouts and issue forms keep their headings and field order. Missing or unsupported layouts use a standard report with a limitation note. Missing required facts request information; unsupported choices, invented attestations and contradictory findings are rejected. Reported issues exposes the rendered draft and fallback notice through its existing evidence and recovery controls.

Retain the six MCP inputs and existing response fields. Pin the new output contract per investigation, preserve legacy workflows and drafts, and retain publication claims so uncertain creation is never repeated. Reconcile the reporting-flow and UI specifications with the implementation.

Decisions

• Choice: AI retains investigation and prose interpretation; code owns repository routing, metadata collection, rendering and validation. Reason: move repeated mechanical work out of AI while preserving judgment. Source: the approved implementation plan.
• Choice: Generic formatting remains subject to repository security/support restrictions and publication checks for authentication, destination availability and source provenance. Reason: layout fallback must preserve reporting authority. Source: the approved implementation plan.
• Choice: Existing investigation generations, drafts and claimed publication intents retain their original contract and identity. Reason: recovery must not reinterpret a retained draft or repeat a possibly dispatched creation. Source: the approved implementation plan.
• Choice: Acceptance remains fixture-only. Real-provider calls, live issue filing and installed-host testing are outside this PR. Reason: those operations require separate authorization. Source: the approved implementation plan.