feat: Telegram connector UI — settings panel wired to opencode-router

[Anurag13075]

What

Adds a Telegram Bot connector panel to OpenWork settings.
Users can connect a bot to their workspace in one click — no config files.

Why

AGENTS.md lists Telegram connectors as a core composability goal.
The opencode-router binary (grammy adapter) + server proxy routes already exist.
This PR adds the missing UI layer to make it usable.

Files Added (all new, zero breakage risk)

• apps/app/pr/telegram-connector.md — PRD
• apps/app/src/app/connections/telegram/telegram-api.ts — API client
• apps/app/src/app/connections/telegram/telegram-store.ts — Solid store
• apps/app/src/app/connections/telegram/telegram-settings.tsx — UI panel
• apps/app/src/app/connections/telegram/index.ts — barrel export

Architecture compliance

• UI never calls opencode-router directly (proxied via openwork-server)
• Bot token is write-only, never stored in state after submit
• opencode-router stays optional — this PR cannot crash OpenWork
• CUPID domain structure followed

Next steps (follow-on PRs)

• Wire panel into Settings/Connections page nav
• Add IPC command to toggle opencode-router sidecar from desktop
• Add unit tests for telegram-api.ts

Happy to iterate fast on any feedback!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	May 2, 2026 4:01am

[vercel]

@Anurag13075 is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

The following comment was made by an LLM, it may be inaccurate: