People outside the project can report a bug or ask for a feature without maintainer-only fields#394

Outcome

A person outside the project who picks Send Feedback… in Miri can file a bug report or a feature request without fields that only maintainers can fill in. GitHub's list of issue forms shows them only the forms meant for them.

Context

• #352 makes Send Feedback… open github.com/samanyudas/miri/issues/new/choose, and the Copy Diagnostics preview open the bug report form.
• On 9 November 2026 Sam chose to make simpler public forms a separate task before the public release (decision record).
• On main at 604b8551, bug_report.yml requires Acceptance criteria, and feature_request.yml requires Acceptance criteria, Requested by, and Release.
• The same list of forms shows the maintainer forms Task or spec and Decision.
• AGENTS.md, CONTRIBUTING.md, and the command guard in .claude/hooks/guard-command.py read these templates, so a change to a form must keep the agents' filing rules working.

Acceptance criteria

• The bug report form that Miri opens requires only fields a user can fill in: what happened, the steps, the Miri and macOS versions, and the diagnostics field with id: diagnostics (review of the YAML, plus FeedbackTests passes).
• The feature request form requires no maintainer field such as Acceptance criteria, Requested by, or Release (review of the YAML).
• The list of forms at issues/new/choose either hides the maintainer forms or marks them as for maintainers (manual check in a browser while signed in as a non-collaborator, or in a private window).
• Agents can still file issues that pass the command guard, and make lint passes.

Verification level

make lint and make swift-test, plus a manual look at issues/new/choose in a browser. No hardware or permission grant is needed.

Out of scope

• Prefilling fields from the Mac. Sam chose addresses that name only the form on 9 November 2026.
• Moving support questions off GitHub.