github-telegram-feedback-pipelinelisted

# Feedback Pipeline — CF Pages + GitHub + Telegram One widget, one Pages Function, two delivery channels. Secrets stay server-side. ``` [FeedbackTrigger / Sheet] ──POST──> [functions/api/feedback.ts] ├─ GitHub Issue (label: feedback) └─ Telegram message ``` **Success rule:** any one channel succeeding is enough. Telegram-only or GitHub-only both work. Do **not** fail the whole request because the second channel failed. ## Provenance (do not reverse) | Source | What to take | |---|---| | **dieline-generator** | Preferred **architecture**: controlled `FeedbackModal` once at app root + `FeedbackTrigger` in chrome + tiny open store; robust Function (attempts[], one-channel-ok, length cap) | | **BrainRush** | Useful **UX behavior/voice** reference: top utility cluster, Esc/outside/X, short product copy. Its visual treatment is not the default skin, and its Function is **older** (all-channels-must-succeed) — do not copy either blindly | | **pep-words** | Same older Function pattern as BrainRush — treat as fleet debt if touched | | **This skill `references/`** | Portable delivery and UI baseline to copy. It is the source of the default; prefer it over mining an installed app | Product owns final copy and optional product-context fields. Skill owns delivery + chrome contract. ## Positioning (why this skill exists) **Job:** give every Liz CF Pages product a same-origin “one sentence felt wrong” p