feat(diagnostics): Help → Report Issue with snapshot-based body

[YakiHugo]

Summary

• Adds Help → Report Issue... that captures a fixed-shape diagnostics snapshot and pre-fills a GitHub issues/new URL in the user's browser.
• Snapshot covers app/Electron/Chromium versions, GPU feature status, displays, window visibility, and per-terminal render state. No titles, paths, labels, or PTY content.
• Falls back to copying the body to the clipboard when the URL would exceed 6000 chars (mirrors VS Code's MAX_URL_LENGTH cutoff).

This is slice 2 of the render-recovery v2 plan. Slice 1 was #162.

Snapshot field allowlist

Reviewable in one place — shared/diagnostics-snapshot.ts:

Section	Fields
app	appVersion, electronVersion, chromiumVersion, nodeVersion, platform, arch, locale
gpuFeatureStatus	feature → status map from app.getGPUInfo('basic')
displays[]	id, scaleFactor, rotation, isPrimary, size
window	isVisible, isFocused, isMinimized, isFullScreen
renderer	visibilityState, documentFocused, devicePixelRatio, innerWidth, innerHeight
terminals[]	id (UUID), rendererMode, status, mode, hasXterm, isAttached, isFocused, cols, rows
webglPool	poolSize, maxContexts, focusedTerminalId, trackedTerminalIds, contextLossCount, lastContextLossAt

Forbidden by design: window titles, terminal labels, cwd / worktree paths, file names, ANSI / PTY content, command lines, URLs the user is visiting. The collectors (getTerminalDiagnosticSnapshots, getWebGLPoolDiagnosticSnapshot, collectMainSnapshot) only return the shapes above — adding a field requires touching the schema, which is the single audit point.

Why snapshot, not breadcrumb / ring buffer

Documented in the header of `shared/diagnostics-snapshot.ts`. Short version: an open event log requires per-event privacy review forever, while a fixed snapshot schema makes "no labels / no paths / no PTY content" a property of the schema, not contributor discipline. Mirrors VS Code's `baseIssueReporterService.ts` (which submits snapshots, not its rotating logs).

Submission tiers

Same shape as VS Code's reporter, minus the GitHub OAuth tier:

1. URL prefill (default) — `https://github.com/blueberrycongee/termcanvas/issues/new?title=...&body=...\` opened via `shell.openExternal`.
2. Clipboard fallback — when the URL > 6000 chars: body written to clipboard, empty new-issue page opened, in-app toast prompts user to paste.

Logs are NOT auto-attached

The rolling JSONL log written by PR 1's `render-diagnostics.ts` is referenced by path in the issue body (so reviewers know where to look), but its content is not bundled. Users who want to share it paste it manually. This matches VS Code's separation of Issue Reporter (snapshot) from `Developer: Show Logs...` (raw logs).

Test plan

• `pnpm typecheck` passes
• `pnpm exec tsx --test` for diagnostics-snapshot, visibility-observer, render-throttling-coordinator, terminal-runtime-store, terminal-runtime-policy, terminal-focus-scheduler — 47/47
• Privacy-leak test (`buildIssueBody does not leak privacy-sensitive content`) passes
• macOS QA: click `Help → Report Issue...` with several terminals open; default browser opens with body filled
• macOS QA: simulate long body (e.g. spawn 50 terminals); verify clipboard fallback fires and toast appears
• macOS QA: verify the rendered body contains no terminal titles, no cwd paths, no PTY output

Out of scope (intentional)

• OpenTelemetry / external telemetry — diagnostics stay local + manual export.
• Sentry-style breadcrumb event log — see schema header for rationale.
• VS Code's GitHub-OAuth POST tier — extra surface for a small return; URL prefill + clipboard already covers >99% of report bodies.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website	Ready	Preview, Comment	May 10, 2026 6:25am