Commit Graph

8 Commits

Author SHA1 Message Date
cj-vana
852fcc4bff forge: patch 6 fix — apply auto-overwrite default after loadPrefs
Move the AUTO_ADD_OVERWRITE_OLDEST assignment to after _store->loadPrefs()
so existing bots with autoadd_config=0 saved on flash get the bit set on
every boot. Previously the assignment was in the constructor (before
load), so loadPrefs() would overwrite our default with the persisted
zero, meaning the fix only took effect on factory-fresh prefs.
2026-05-16 19:07:27 -06:00
cj-vana
707f492a05 forge: add patch 6 — bot advert marker + auto-overwrite
- All self-advert paths (CMD_SEND_SELF_ADVERT, CMD_EXPORT_CONTACT,
  MyMesh::advert()) now use bot advert name with [MCBOT] suffix when
  bot_prefs.enabled, via new getAdvertNodeName() helper
- Initial flood advert at 120s after boot instead of 24h, so other
  nodes see [MCBOT] in the contact name shortly after the bot boots
- AUTO_ADD_OVERWRITE_OLDEST set by default on CMESH_BOT builds, so
  bots don't silently stop accepting contacts when the table fills

Patches 0001-0005 re-exported (cosmetic series-count bump 1/5 -> 1/6).
2026-05-16 18:59:03 -06:00
cj-vana
5af562c6be ci: pin submodule to upstream base and apply patches at build time
The submodule had been pointing at a local MeshCore commit that included
all 5 patches applied on top of upstream. That commit only exists in the
local working tree — CI's `submodules: recursive` checkout couldn't
fetch it from github.com/meshcore-dev/MeshCore and failed with
"fatal: not our ref d2ad3ac8".

Resets vendor/MeshCore to upstream main (910b1bee, the same base our
patches were authored against) so CI can fetch it normally, and adds an
explicit `apply-patches.sh` step to the firmware-build workflow before
the verify and build steps run. The release workflow already applies
patches explicitly so no change there.

Subsequent verify/build steps set MESHCORE_SKIP_APPLY_PATCHES=1 to avoid
re-applying patches on the now-dirty tree.
2026-05-16 13:05:24 -06:00
cj-vana
d26979ed94 forge: add patch 5 — hop-aware bot coordination
Bundles in-progress utility commands (TIME, LORA, ID, NEIGHBORS), neighbor
tracking, received_at_timestamp / personalized acks, and per-hop response
delay coordination. Tunes the coordinator so multi-hop senders actually get
responses: hop step 5s→1.5s, hop bias capped at 8s, pending TTL 15s→45s.

Verified on Heltec V3 bench bot: responds to #bot at 2, 4, and 6 hops.

BOT_PREFS_VERSION bumped 2→3, so existing bots will reset bot prefs (channel
names, known bots) to defaults on first boot of this firmware.
2026-05-16 12:48:00 -06:00
cj-vana
6b7de37630 forge: allow prefixless firmware bot dms 2026-05-15 20:10:23 -06:00
cj-vana
98d2dc556d forge: harden firmware bot coordination 2026-05-15 19:59:45 -06:00
cj-vana
dc7004f7f1 forge: step 13 — validate bot parity and export patch 2026-05-15 11:50:37 -06:00
cj-vana
346ca7cb93 forge: step 1 — bootstrap wrapper workflow 2026-05-14 12:08:59 -06:00