MarekWo 2764e1c551 feat(dm): Add PATH-based delivery tracking for flood DMs ...

When sending DM to contacts without a known path (flood mode), ACK is
piggybacked inside the PATH response packet and not visible on stdout.
This adds PATH_UPDATE event parsing to confirm flood DM delivery.

Changes:
- Enable print_path_updates in meshcli init for PATH_UPDATE events
- Parse PATH echoes from json_log_rx -> .path.jsonl log (diagnostics)
- Parse PATH_UPDATE events to confirm flood DM delivery by public_key
- Replace "skip retry for no-path contacts" with proper flood retry
  (max 3 attempts, matching standard Meshcore app behavior)
- Split _retry_send into _retry_send_flood and _retry_send_direct
- Refactor _get_contact_path_len -> _get_contact_info (returns both
  out_path_len and public_key)
- Add GET /paths endpoint for diagnostics
- Add flood_only config param for auto-retry

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-27 10:33:39 +01:00

..

bridge.py

feat(dm): Add PATH-based delivery tracking for flood DMs

2026-02-27 10:33:39 +01:00

Dockerfile

upg: Meshcore-cli upgrade to 1.4.2

2026-02-15 16:06:49 +01:00

requirements.txt

feat: Add interactive meshcli console with WebSocket support

2026-01-09 08:27:42 +01:00