Feature idea: in-app annotated-screenshot bug reporting from the widget (with auto-captured technical context)

[iPLAYCAFE-dev]

Hi maintainers — thanks for Quackback; we run it in production and it's been great.

One gap we've hit versus dedicated bug-report tools: when an end-user reports a bug through the widget, there's no built-in way for them to attach an annotated screenshot, and no automatic capture of the technical context an engineer needs to reproduce it. A "it's broken" report often arrives with none of the reproduction signal.

We've built this as a fork patch and wanted to gauge whether it's something you'd welcome upstream before investing in polishing it to your conventions.

What it does — a "report a bug" widget entry (shortcut + SDK command) that captures the page as an image the user can annotate (pen/arrow/rectangle/redact) + a one-line summary + one-tap impact; plus automatic privacy-first capture of route, build/commit id, a correlation/request id (join client↔server logs), tenant id, a console/error ring buffer, and the last failing request — every string deep-masked client-side before it leaves the browser. DOM-based (shadow-DOM-friendly), lazy-loaded, behind a config flag (default off). The structured context rides the existing post flow + surfaces on the post.created webhook.

Why it fits — raises report rate (low friction) + makes each report rich enough for automated triage/AI — squarely the feedback-tool value prop; additive + flag-gated (no behavior change).

Questions — (1) in-core or intentionally out of scope? (2) preferences on capture approach / masking / webhook shape before a PR? (3) same appetite as #118 ("Add the image as an attachment")?

Happy to open a PR adapting to your conventions if there's interest. Thanks!