Share learnings about Reflex itself as GitHub issues, with the user's approval #49

Why. Some things Reflex learns are about Reflex, not about the user: a default that keeps being overridden, a missing feature the user keeps working around, a recurring error. Those should reach Reflex's developers.

What to build.

• Jev sorts each learning: "Is this about Reflex's own behaviour, rather than the user or their project?"
• Matching learnings collect in a "Suggestions for Reflex" list (on the Memory or Observability page).
• For each, Reflex drafts an issue for kaustav1996/reflex: what happened, how often, a minimal example. Secrets are masked and paths, project names and personal details are stripped; the user sees the exact text and can edit it.
• Nothing is sent without an explicit click. Submit with the user's own gh login if present, otherwise open a prefilled "new issue" page in the browser.
• Check for an existing matching issue first and offer a 👍 or comment instead of a duplicate.

Roadmap item 6.7 · effort M · details in docs/ROADMAP.md.

Blocked by: #48

Related: #50, #52