7 Commits

Include renames

Author	SHA1	Message	Date
kamilkrzywda	3b1f5de101	Add #loser command — worst packet delivery record over directed sends (v0.21.9)	2026-09-29 20:58:43 +00:00
kamilkrzywda	70be8bdaa7	Add #help command — short single-message list of all commands (v0.21.6) ... Owner request: 'now add #help with short list of all command'. Registered in the CommandService constructor next to #ping; returns a SINGLE multi-line string (one packet, ~203 chars) — not an array, which would drip-feed one spaced packet per line through the v0.21.5 MESH_MULTI_SEND_DELAY_MS loop. Also hardened the v0.21.5 multi-send-spacing spec: its wall-clock assertion ('first send < 8 ms after t0') flaked under full-suite load — replaced with fake timers, which assert deterministically that line 1 is out before any time elapses and lines 2-3 land exactly one delay apart.	2026-09-26 10:52:18 +00:00
kamilkrzywda	1b768b14a7	Space multi-line command replies MESH_MULTI_SEND_DELAY_MS apart (v0.21.5) ... Production incident: '#rss get lublin' returned an array of lines and CommandService sent each one back-to-back within the same second — on the real mesh 3 of 4 items were dropped in RF (the owner saw only the last one). CommandService.onRx now waits MESH_MULTI_SEND_DELAY_MS (new env, default 5000 = 5 s, read at construction like the other timing knobs) between consecutive lines of an array reply — no delay before the first line. The delay sits in the shared per-line loop, so both the respond() path and the legacy sendText fallback are covered by one await.	2026-09-26 10:29:21 +00:00
kamilkrzywda	cdd52a3ddb	Send #rss get summaries as 3-5 separate mesh messages (v0.21.0) ... The single-message summary was too small (owner request). The summarizer prompt now asks for exactly 3-5 lines, one item per line, in the format '<short header>: <one or two short sentences>' with a <=20-char header, no intro/outro/numbering. maxTokens stays 2500 (reasoning-token headroom). The reply is parsed into items: drop empty lines and lines without a ':' header separator, cap at 5; fewer than 3 valid lines sends what we got (no failure/retry), zero valid lines sends nothing. Each item goes out as its own mesh message via respond(id, line) - all threaded to the trigger packet id on its channel. Per-item backstop fitOneLine() hard-cuts any line >185 chars at a word boundary near 180 so every item fits one packet; the old whole-reply fitOnePacket() cut is gone. CommandService sends array replies line by line through the same routing as single replies (respond per line, or legacy sendText fallback per line when there is no packet id). LLM failure path unchanged: single 'summary failed' reply.	2026-09-25 20:09:16 +00:00
kamilkrzywda	eda1cbd125	Add #rss command family with LLM tags and summaries (v0.20.0) ... #rss subcommands on the command channel: help / add <url> <name> / remove <name> / tags / sources / get <name|#tag>. Sources are stored in a new rss_sources table in the existing MESH_DB_PATH file (second node:sqlite connection, case-insensitive names); feeds parsed with fast-xml-parser (RSS 2.0 + Atom); AI tags and headline summaries via injected LlmService.chat() with bounded maxTokens (50/200). CommandService gains prefix registration so one handler owns the whole #rss family while #ping stays an exact match; wired in CommandModule's factory — still no constructor-level cycle, no forwardRef. One dead feed does not sink a tag summary.	2026-09-25 18:44:06 +00:00
kamilkrzywda	9d4c9594af	Route command replies through MeshService.respond() — same channel, threaded quote (v0.18.1)	2026-09-25 17:30:28 +00:00
kamilkrzywda	931b42bb1e	Add channel-2 #command auto-responder (v0.18.0) ... Event-driven CommandService dispatches exact case-sensitive #command matches on COMMAND_CHANNEL (default 2) through a single-registration-point registry; first command #ping -> #pong!. Replies ride COMMAND_CHANNEL: directed DM back to the sender when present, else broadcast. Failing handler/send only logs a warn. DI: CommandModule's factory injects MeshService and attaches itself via MeshService.attachCommands() — a constructor-level cycle leaves one side null in NestJS 12's injector (verified), so no forwardRef is used. Tests 106 -> 121; docs synced (AGENTS.md, MESHTASTIC.md, README).	2026-09-25 17:11:52 +00:00