Patch v2.2.6 - Tournament Anti-Interference Compliance

v2.2.6 - Tournament Anti-Interference Rules Compliance

Implements the organizer's rules update (upd.docx, 避免外部连接干扰比赛-解决方案). Referees pull system logs during matches; non-compliant external connections are penalized. Functionally identical to v2.2.5 otherwise.

What changed

Automated by this patch

• Bundled the official scripts/kill_booster_server.sh (verbatim from the organizer's attachment - do not modify): stops the boosterserver / server.motion service that provides phone-App and Bluetooth connectivity. Handles firmware 1.7 (bdb service), 1.6 (bdb container), and pre-1.6 (BoosterServer process) automatically.
• scripts/start.sh runs it in the background at the exact position the official doc specifies (after ./scripts/stop.sh, before jetson_clocks):
  sudo -v && sudo -b bash ./scripts/kill_booster_server.sh >/dev/null 2>&1
  The service auto-starts on every boot, so each match start re-disables it. After it runs, the rear breathing light turns red - this is the expected Bluetooth-off indicator, not a fault. Daily (non-match) App usage is unaffected: the service returns after a reboot.

Manual steps per robot (cannot be automated - do before the match)

1. Block booster-studio connections: sudo passwd booster (studio logins require the user password).
2. Report each robot's wireless IP to the organizers: run ifconfig and read the wlP1p1s0 inet address. Only the registered eight robot IPs are permitted on the field network - anything else is removed and blacklisted.
3. Do not connect to the field network outside of matches.

Packaging

• Repository source folder v2.2.6/ excludes TensorRT .engine model files.
• Release asset v2.2.6.zip contains the full patch folder, including model engines.

Validation

• kill_booster_server.sh shipped byte-identical to the official attachment; LF endings verified on it and the modified start.sh.
• No brain/vision code changes vs v2.2.5 - no rebuild required if v2.2.5 is already built on the robot; just update scripts/.