Command the Grocery Bot fleet.

Write the program that steers a swarm of Grocery Bots. Pick the goods, dodge the traffic, deliver every order.

curl -fsSL https://grocerybot.no/static/install.sh | sh

curl -fsSL https://grocerybot.no/static/install.sh | sh

Help me build a competitive Grocery Bot for the NM i AI challenge at https://grocerybot.no.

Start by checking my operating system and available Python/Node.js versions. Ask which language I want to use if it is unclear. Install the participant CLI using https://grocerybot.no/static/install.sh on macOS/Linux/WSL (Python 3.11+), after inspecting the script. If the service is still behind its launch countdown, explain that installation is not available yet and stop there.

Use `grocerybot --help` and the relevant command help to understand the CLI. Create a new project with `grocerybot init my-bot` (Python) or `grocerybot init my-bot --template javascript` (Node.js). Never overwrite an existing project. Read the generated README.md, PROTOCOL.md and grocerybot.toml, plus https://grocerybot.no/how-to-play, before changing the bot. For another language, implement the same process protocol and set bot.command accordingly.

Explain the task: coordinate robots to collect requested goods from adjacent shelves and load docked trucks. Inventories hold three items; robots block each other; moves resolve in robot ID order. Score one point per delivered item and five per completed truck. Each difficulty has a fixed store; orders and truck timing vary. The leaderboard keeps my best game score in each difficulty and sums those five best scores. A lower score in a later game does not reduce my best score. Follow the current protocol and rules rather than guessing fields or action names.

Keep the bot alive for the whole game. Read newline-delimited JSON on stdin, reply to hello with ready/protocol_version 1, and answer each game_state with its matching round and an actions array. Flush stdout and put diagnostics on stderr. Use only the public state; never depend on engine internals, hidden seeds or future orders. Handle game_over, game_end and EOF.

Run `grocerybot doctor` to check the bot before playing. Show me how to run `grocerybot login`, read the rules and choose my leaderboard name. Let me complete browser login and accept the joining disclosure myself. Never request or expose my password, API key or credentials. Once I authorize playing, start one game with `grocerybot play --store easy` and show its recorded score.

Improve pathfinding, item assignment, collision avoidance and truck scheduling in small steps. Use benchmarks and recorded replays to compare changes across difficulties and unseen seeds. Report measured scores and regressions; do not claim improvements without running the bot. Ask before starting additional games unless I have already authorized them, since games use the daily allowance.