MarekWo 4effa47fe1 fix(ui): multi-byte path rendering across contact list, DM modal, retry ...

Same root cause as the previous console fix: meshcore lib 2.x stores
out_path_len as the masked hop count and out_path_hash_mode separately.
Several UI surfaces and the DM retry logic were still decoding the
hash-size mode from the upper bits of out_path_len, which always yields
1 for in-memory contact data and silently truncates multi-byte paths.

Fixed sites:
- /api/contacts/detailed: path_or_mode and outgoing payload now use
  out_path_hash_mode; the field is included in /api/contacts too.
- dm.js: Contact Info modal computes hashSize for the import button
  from out_path_hash_mode.
- console "contacts" command: same correction as "path".
- device_manager._paths_match / _extract_path_hex: accept hash mode as
  a parameter; callers (_dm_retry_task, _delayed_path_backfill, Phase 2
  rotation dedup) pass contact.out_path_hash_mode.
- PATH event handlers: derive hash_size from path_hash_mode instead of
  decoding it from an already-masked path_len.

2026-06-05 08:54:29 +02:00

..

css

feat(ui): user-configurable sidebar breakpoint width

2026-05-06 21:35:56 +02:00

images

Feature: Add favicon and PWA manifest for better branding

2025-12-22 09:53:32 +01:00

js

fix(ui): multi-byte path rendering across contact list, DM modal, retry

2026-06-05 08:54:29 +02:00

vendor

feat: Add interactive meshcli console with WebSocket support

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

favicon.ico

Feature: Add favicon and PWA manifest for better branding

2025-12-22 09:53:32 +01:00

manifest.json

fix: Remove maskable purpose from icons to prevent cropping

2026-01-05 14:56:35 +01:00