3 Commits

Author	SHA1	Message	Date
cj-vana	ee1b95cc9e	forge: add patch 13 — quadratic hop delay growth ... bias = hop * step + hop^2 * BOT_HOP_GROW_MILLIS Bumps hop_step 3000->2000, adds BOT_HOP_GROW_MILLIS=400, raises cap 15000->50000 and TTL 75000->95000. Forces re-default of hop_step on existing bots via BOT_PREFS_VERSION 5->6. Gap between adjacent hops now grows with hop count (3200ms at hop 1 all the way to 8000ms at hop 8), so a far bot reliably has time to hear a near bot's reply through the mesh before its own scheduled fire time -- previous linear bias kept the gap constant at 3000ms, which wasn't enough at 6+ hops where reply propagation takes ~5-10s.	2026-05-16 22:18:18 -06:00
cj-vana	5f35af7854	forge: add patch 12 — spell out hops/byte, drop channel name in test ack ... Test response now reads: @[user] | 2 hops, 2-byte hashes, SNR -1.25 | recv 21:25:45 (was: @[user] #bot | 2h@2B SNR -1.25 | recv 21:25:45) Path response now reads: Path @[user] 6 hops, 2-byte hashes, SNR -8.50 | <path> (was: Path @[user] 6h@2B SNR -8.50 | <path>) DM responses keep 'direct' indicator. Trace and other commands unchanged for now. Tests updated for the new strings. Submodule pointer stays at upstream 910b1bee so CI submodule clone succeeds; apply-patches.sh applies the queue at build time.	2026-05-16 21:32:19 -06:00
cj-vana	16846a354c	forge: add patch 11 — auto-advert at 5s after boot ... Shortens BOT_PREFS_INITIAL_FLOOD_ADVERT_MILLIS from 120000 to 5000 so the bot announces itself to the whole mesh ~5s after boot instead of 2 minutes after boot. Recurring flood interval still 24h (upstream default); ask if you want that tightened.	2026-05-16 20:49:59 -06:00