[raiseCatError]

Summary

Lightweight improvement to existing issue forms and a maintainer-facing evidence/UX research playbook. No app implementation, workflow changes or release operations.

• Keep the five existing issue forms; bug and idea forms gain one optional context field (bug impact/workaround, idea existing alternatives); the feature form's existing workaround question now also asks what an existing control is missing.
• Add docs/ISSUE_TRIAGE.md: classify reported vs verified, research vs approved work, practical P0–P3 provisional prioritization, Apple HIG/Android accessibility research when warranted, do-nothing/reuse/add comparisons, physical testing vs code review, privacy safeguards and acceptance/closure criteria.
• Link maintainer guide from CONTRIBUTING while explicitly saying reporters need not do design research.
• Existing kind/platform labels and release/branch rules remain unchanged.

Research considered

• Existing MeowDisplay issue templates, CONTRIBUTING, BRANCHING and real trackers Window view UX: pane fullscreen toggle, drag-to-remove and discoverability #120, Receiver UX: accessible quick Disconnect and adaptive mobile controls/text #121, Performance lab: repeatable streaming benchmarks, quality/stutter metrics and comparisons #123, Receiver gestures: faster modifier-tray shortcut reveal, haptic feedback and configurable hold timings #131 and current issue patterns.
• Apple HIG Gestures and Accessibility: meaningful custom shortcuts, visible alternatives, system gesture conflicts.
• Actual form patterns of Zed (repro + environment + privacy), VS Code (minimal bug/feature intake) and Godot (tested versions and minimal reproduction). Chose less contributor burden instead of transplanting complex forms.
• GitHub issue form schema.

Related issues (filed independently, not implemented)

• Bug: rapid two-finger double-tap often fails to reset a Window view pane #137 rapid two-finger double tap in Window view
• Window view quality versus Mirror/Extend #138 Window view softer than Mirror/Extend
• Idea/research: temporary floating pane over the receiver workspace #139 floating temporary pane / edge-tuck interaction exploration (no external Reddit link)

Validation

• Verified issue-form IDs remain unique, types are supported and optional fields have no required validation.
• Reviewed changed-file scope: three forms, CONTRIBUTING and new guidance file only.
• CI pending. No Mac/Android/iOS behavior or release configuration changed.

Scope guard

Do not add automation, labels, milestones, due dates, releases, new features, or merge this draft without review. No priority has been assigned to the three new issues as a verified fact.

[raiseCatError]

Review corrections in 9a62dc4 (one commit):

• Evidence terms: added a short table defining observed, reproduced, inferred, proposed and verified, and used the same terms in CONTRIBUTING and the decision step. The guide previously distinguished only reported from verified.
• Priority labels: the repo already has priority:high and priority:medium labels (used on Release and distribution readiness audit #1–Release screenshots/assets checklist #11). The guide said no label taxonomy existed; it now maps them roughly to P1 and P2 and says only the maintainer applies them.
• Feature form: the new "Could an existing control or workflow solve this?" field duplicated "How do you handle this today?", so it is folded into that field's description. One fewer box for reporters.
• Material Design link: the old link returned 404; it now points to the adaptive-design overview (200).

All six forms parse as YAML with valid field types, unique IDs and no new required fields. Not merged.