feat: cross-app feedback intake to GitHub backlog

[SebastianBoehler]

Idea

Add a feedback / feature-request intake feature across apps that converts user requests into GitHub issues or tickets, giving the project one centralized backlog of product feedback and implementation ideas.

User value

• Users can submit feature requests or feedback from any app surface.
• Requests are captured as structured GitHub issues instead of getting lost in chat, notes, or app-local state.
• Codex automations or agents can later review the backlog and decide whether to discard, refine, or implement each request.

Possible flow

1. User submits feedback or a feature request in an app.
2. The app normalizes it into a structured request payload.
3. A backend/service creates a GitHub issue in the central backlog repo.
4. The issue includes source app, user context if permitted, request text, category, priority hints, and reproduction/details if relevant.
5. Codex automation periodically triages issues into discard, needs clarification, ready for implementation, or implemented.

Product questions

• Should all apps write into this repo, or should each app have its own repo with a shared label convention?
• What user identity/context can be attached safely and with consent?
• Should users be able to see issue status after submitting feedback?
• Do we need moderation/spam protection before creating GitHub issues?
• Should duplicate detection happen before issue creation or during automation triage?

Implementation notes

• Do not create mock tickets or fallback data; surface clear errors if GitHub issue creation fails.
• Define a common request schema shared by app clients and the ticketing backend.
• Use labels such as feedback, feature-request, needs-triage, source:, priority:.
• Consider a Codex automation that regularly reviews new issues and proposes discard/clarify/implement actions.

Captured from project memory request.