MarekWo 34afa6908d feat(bridge): Implement persistent meshcli session with advert logging ...

Major refactor of meshcore-bridge to maintain a single long-lived meshcli
process instead of spawning new processes per request.

Changes:
- Add MeshCLISession class managing persistent subprocess.Popen session
- Implement thread-safe command queue with event-based synchronization
- Add stdout/stderr reader threads with JSON advert detection
- Log adverts automatically to {device_name}.adverts.jsonl with timestamp
- Add end-of-response markers (echo "___END_{cmd_id}___") for multiplexing
- Implement watchdog thread for auto-restart on meshcli crash
- Update /cli endpoint to delegate commands through persistent session
- Add MC_CONFIG_DIR and MC_DEVICE_NAME env vars to docker-compose.yml

Architecture benefits:
- No more USB port conflicts between concurrent requests
- Continuous advert logging without breaking /cli compatibility
- Better error recovery with automatic session restart
- Reduced overhead from process spawning

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-28 15:41:41 +01:00

..

bridge.py

feat(bridge): Implement persistent meshcli session with advert logging

2025-12-28 15:41:41 +01:00

Dockerfile

build(bridge): Update meshcore-cli to version 1.3.12

2025-12-27 18:52:26 +01:00

requirements.txt

refactor: Implement 2-container architecture to solve USB stability issues

2025-12-23 08:39:10 +01:00