submission-checklisted

# /submission-check, deliverables gate The last thing that runs before submitting. Its job is to catch the defects that make good work score zero. Two failure modes it exists for, both stated by the organisers as absolute: 1. A submission that depends on environment modifications, or does not run correctly inside the provided Docker image, **will not be evaluated**. 2. A submission whose launch file does not accept `shelf_column_number` and `book_colour` correctly **will not be evaluated**. Neither is a deduction. Both discard everything. ## Steps Work through all four blocks. Report every unchecked item, and do not summarise a partial pass as a pass. ### Block 1: evaluation risk, check these first Anything failing here means the submission is not graded at all. - [ ] `solution.launch.py` accepts both arguments, tested with the **literal** organiser command: `ros2 launch <package> solution.launch.py shelf_column_number:=2 book_colour:=red` - [ ] **Every** dependency declared in `package.xml`, verified by a fresh-clone build in a fresh container, not by reading the file - [ ] No modification to the provided Docker environment: OS, ROS 2 distribution, Gazebo version, robot model - [ ] Fresh clone into a fresh container: `colcon build` clean with **zero** manual fixes - [ ] Runs on a second machine, if one exists - [ ] Repository is public and the link resolves without a login - [ ] Scored topic names and types exactly as specified, never renamed: `/erc/shel