Filing Issues

Use GitHub Issues to track bugs, feature ideas, and dev tasks. A good issue saves time for whoever picks it up — include enough context so someone can start working without asking questions.

Bug Report

**Summary**
Brief description of the bug.

**Steps to Reproduce**

1. Go to ...
2. Click on ...
3. Observe ...

**Expected Behavior**
What should happen.

**Actual Behavior**
What happens instead.

**Environment**

- Browser/device:
- Screenshots (if applicable):

Feature Request

**Problem**
What problem does this solve? Who is affected?

**Proposed Solution**
Describe what you'd like to happen.

**Alternatives Considered**
Any other approaches you thought of (optional).

Dev Task

**Description**
What needs to be done and why.

**Acceptance Criteria**

- [ ] Criteria 1
- [ ] Criteria 2

**Related Files/Areas**
List relevant files or areas of the codebase.

Tips

• Use labels: bug, feature, chore to match branch prefixes.
• Assign yourself if you plan to work on it.
• Reference issues in your PR description with Closes #123.