[Feature] Messaging bot connection

[maximedogawa]

User Story

As a user
I want connect my mobile messaging client to the local PEngine app during setup
So that I can send and receive messages between my smartphone and the desktop/web app.

Description

The proof of concept should focus on establishing a basic messaging connection with minimal features:

• Only support adding connected devices
• No advanced messaging features (e.g., history sync, attachments, etc.)
• Focus on validating end-to-end communication

Functional Requirements

• Setup Wizard Integration
• Extend the setup wizard to include a “Messaging Connection” step

Provide a UI to:

• Display or accept a connection URI
• Guide the user through connecting their smartphone
• Connection Flow
• The connection URI is generated or retrieved from the web app
• The user copies this URI into the locally installed PEngine app

The local PEngine app:

• Establishes the messaging connection
• Registers the device as “connected”
• Persistence
• The local PEngine app must:
• Store the connection data locally
• Reuse it across restarts
• Remove it only when the user explicitly disconnects
• Device Management (PoC level)

Maintain a simple list of:

• Connected devices
• No editing or advanced management requiredlocal with Tauri.

Acceptance Criteria

• Botfather connection flow
• Device Connection verification
• Connection details store from website to local running pengine instance
• Verify setup works
• create e2e connection with real data

Design Considerations

• UI/UX considerations
• User flow
• Visual mockups or wireframes (if applicable)

Technical Implementation

• Rust telebot libary
• connection service running locally and listens on localhost