Integration: Connection manager for remote products (TrapFall, Rungu)

[ajianaz]

Description

Split from #36. Hub connection manager for remote CodeCora products.

Products

TrapFall (Issue Tracker)

• Type: Remote (HTTP API)
• Base: /api/0/
• Endpoints: GET /projects, GET /projects/{slug}/issues, GET /issues/{id}/events, WS /api/0/ws
• Hub access: read-only

Rungu (Project Management)

• Type: Remote (HTTP API)
• Base: /api/
• Endpoints: GET /projects, GET /projects/{slug}/posts, GET /projects/{slug}/roadmap
• Hub access: read-only

Tasks

• Connection model: add/remove/test remote product connections
• Config: store connections in ~/.codecora/connections/{product}.json
• API clients: TrapFall + Rungu HTTP clients (reqwest)
• Connection health check command
• Settings UI: manage connections
• Graceful degradation: show cached data when offline

Dependencies

• Blocked by: Architecture: Centralized data directory (~/.codecora/) with local + remote product integration #36 (centralized data directory)
• Related: Hub: Multi-product dashboard (Uteke, Cora, TrapFall, Rungu) #19 (multi-product dashboard)

Notes

• Remote products are read-only from Hub — create/edit stays in respective web apps
• API keys stored in connection config files (chmod 600)
• Consider WebSocket support for TrapFall real-time updates

[ajianaz]

Connection manager fully shipped in v0.2.0 — 8 Tauri commands, ConnectionManager.svelte (591 LOC), health polling, trait-based ProductAdapter + MemoryBackend. Closing as completed.