Add Raspberry Pi LumaBot control and autonomy integration

[patmakesapps]

What changed

• Add the Raspberry Pi 5 deployment profile and Python 3.13 ARM compatibility updates.
• Add structured LumaBot status, drive, sequence, stop, reboot, poweroff, and autonomous-driving tools.
• Add per-conversation Off, Agent, and deterministic no-LLM Remote modes across web, Telegram, and CLI surfaces.
• Add watchdog-safe timed, continuous, and sequenced motion scheduling.
• Add renewable activity leases so the NeoSlider pulses purple during interactive Agent turns.
• Make autonomous driving owner-only, always approval-gated, and unavailable to autonomous background tasks.
• Teach STOP to cancel both scheduled/manual motion and local autonomous roaming.
• Add owner-only, always-confirmed whole-Pi reboot and poweroff actions with exact sudoers rules.

Why

LumaKit is the conversational control layer for the physical robot, while the separate LumaBot daemon owns hardware access, obstacle avoidance, and motor safety. Starting ongoing physical movement requires explicit owner intent and approval; stopping remains immediate.

User impact

Owners can ask LumaKit to start autonomous roaming, inspect live distance/tilt/collision state, or stop the robot naturally. The hardware daemon refuses autonomy unless motors, fresh distance, motion, tilt, and battery safety checks all pass.

Checks

• .venv/bin/python -m pytest -q — 114 passed.
• The LumaBot tool group loads the approved lumabot_start_autonomy action.
• Approval-policy tests confirm autonomy is owner-only, always confirmed, and refused in autonomous tasks.
• The live LumaBot daemon reported fresh distance and zero motor output during validation.