Update issue template to ask for visuals

[clairep94]

Issue:

Fixes # -- maintainer discussion from Oct 2nd:

• Update the issues template to nudge/give instructions to ask for visuals.

Demo:

Changes:

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• has no typecheck errors (npm run typecheck)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123
• meets the standards outlined in the accessibility guidelines

[Copilot]

Copilot review overview

🟢 Approval recommended

The issue-form updates are valid, consistent, and fulfill the stated purpose.

Review effort: Balanced
Findings: None

What changed in this PR

Updates issue forms to encourage contributors to include visuals when reporting bugs or proposing features.

Changes:

• Requests screenshots or recordings for actual bug behavior.
• Adds visual-upload guidance to feature request and enhancement forms.

File	Description
.github/​ISSUE_TEMPLATE/​found-a-bug.yml	Expands guidance for attaching visuals.
.github/​ISSUE_TEMPLATE/​feature-request.yml	Adds screenshot and recording instructions.
.github/​ISSUE_TEMPLATE/​existing-feature-enhancement.yml	Adds screenshot and recording instructions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.