raiden-pico

Firmware-change discipline for Raiden Pico — ANY change to the firmware (src/*.c, src/*.pio, include/*.h that alters the built raiden_pico.uf2's behavior or output) MUST bump the firmware version string in the SAME change. The version is what the VERSION command prints, in src/command_parser.c. Invoke whenever you edit firmware source, or are about to build + flash a firmware change.

CLI discipline for Raiden Pico. (1) Every command/sub-command/argument MUST emit an explicit error on unrecognized, mistyped, or malformed input — never silently no-op or fall through to a wrong/default branch. (2) Every CLI add/change/rename MUST update the config_none pytest regression tests AND the docs/HELP in the same change. Invoke whenever you add, change, rename, or review a CLI command path in src/command_parser.c (verbs, sub-commands, argument parsing, dispatch branches) or the matchers in command_parser_match / match_and_replace.

GPIO pin-assignment rules for Raiden Pico (RP2350). Invoke whenever you add, change, move, or claim a GPIO pin — e.g. editing pin

Keep requirements.txt and requirements-dev.txt in sync with the actual third-party Python imports across the repo. Invoke whenever you add, remove, or move a Python `import` of a non-stdlib package in any .py file — especially before committing changes that touch .py files. The repo's dependency graph on GitHub reads these manifests.

Fetch open GitHub issues for the current repo so we catch problems users have reported. Use at least once per working day, ideally at the start of a session, and again when the user mentions "issues", "bugs", "reports", or asks "anything new?".

Build and flash firmware to Pico2. Use after code changes to deploy to hardware.