report-bug

Draft a Synergy Bug Report

Own the Boundary

Reporting and diagnosing are different jobs. /debug plus find-logs, inspect-sessions, and architecture own the root-cause work; this skill packages an existing finding into an issue draft for the user to review. Do not open a GitHub issue yourself and do not treat a draft as authorization to publish — the user reviews the full text and files it. Redaction is enforced by the shared outbound-text rule in git-guide: no absolute paths, SYNERGY_HOME values, session or Scope IDs, raw logs or traces, credentials, provider endpoints, or internal identifiers. Project-relative source paths are allowed.

Verify the underlying claim before drafting. A report built on an unverified hypothesis wastes maintainer time; rerun the failing command or test and cite its current behavior. If verification is impossible right now, say so in the draft instead of writing an unqualified claim.

Draft From the Template

Produce the complete issue body in fenced Markdown for one-shot copying. It must answer every field the repository bug form asks for — what happened, expected behavior, reproduction steps, environment, and supporting evidence — as structured by .github/ISSUE_TEMPLATE/bug_report.yml, and split the diagnostic evidence into observed, inferred, and unknown. Every section below is required except Additional context, which should be dropped when empty rather than padded:

## Summary

<One paragraph: what is broken, where it lives, and the confirmed root cause or current best-supported theory.>

## User-visible behavior

<What a user observes, as facts separate from interpretation.>

## Steps to reproduce

<Minimal numbered steps. Name the runtime (installed release or `bun dev` mode) and whether the failure is deterministic.>

## Expected behavior

<The invariant the violated behavior breaks, not just the symptom's absence.>

## Actual behavior

<The observed failure, including the exact error text or minimal stack frames.>

## Diagnostic findings

### Observed

<Evidence verified at runtime: failing test name and result, log or observability excerpt with timestamps trimmed, reproduction command. Cite the evidence source and time window.>

### Inferred

<Causal chain from the evidence, stated as theory with its supporting observation.>

### Unknown

<What the current evidence cannot establish. Unverified claims and unrecovered details belong here, not in Observed.>

## Environment

- OS:
- Synergy version: (`synergy --version` or dev branch/commit)
- Bun version: (`bun --version`)

## Reproducibility

<deterministic / intermittent (approximate rate) / not reproduced — with one sentence on what varies.>

## Additional context

<Linked issues, prior postmortems, regression window, or proposed fix — only when real.>