name: Bug report about: Report a defect, crash, or unexpected behavior so the team can reproduce and fix it. title: "" labels: ["bug", "triage"] assignees: []
Before submitting
- Search existing issues (open + closed) — yours may already be tracked.
- This is for defects against the approved spec/architecture. For new behavior, use the Feature request template. For "X doesn't work as I expected" where the spec is silent, say so — we will route it to the roadmap instead.
Description
A concise summary of what is broken and how it affects the user.
Steps to reproduce
Exact, ordered steps that reproduce the problem from a clean state:
- Go to …
- Click on …
- See error …
Include the exact UI path (workspace → page → …) and any keyboard input. For API-level bugs, paste the curl command instead.
Expected behavior
What the spec/architecture says should happen (cite PRODUCT-SPEC.md /
ARCHITECTURE.md / the phase task file if you can).
Actual behavior
What actually happens, including the exact error text / status code / log line.
Environment
| Field | Value |
|---|---|
| OS | (e.g. macOS 14.5, Ubuntu 22.04, Windows 11) |
| Browser | (e.g. Chrome 125, Firefox 126, Safari 17) |
| App version | (commit SHA or git describe --tags --always) |
| Deploy mode | (local docker-compose / k8s / terraform-ec2 / other) |
| Node / pnpm | (from node -v and pnpm -v) |
Screenshots / screen recording
Drag images here. For editor/drag-and-drop bugs a short screen recording is much more useful than screenshots.
Logs
Relevant server / browser-console output. Redact secrets.
paste logs here
Additional context
Anything else: workarounds found, related PRs, whether it is intermittent, rough frequency, and the last commit where it worked (if known).