One folder per package for patches, tests and recipe files #220

Follow-up to #217 (the monorepo moving to vinca-rs).

Today a package's RoboStack-specific files live in three places per layer (shared/ and distros/<d>/):

• patch/<pkg>[.<platform>].patch: source patches;
• tests/<pkg>.yaml and tests/<pkg>/: package tests and their assets;
• files/<pkg>/: files copied into the recipe directory (since Generate recipes, snapshots and build workflows with vinca-rs #217: ros_workspace's activation scripts).

They are all the same kind of thing: files about one package, found by its name, in either layer. The only real difference is how vinca-rs wires them into the recipe, and that can be decided from the file name.

Proposal

One folder per package and layer, e.g. shared/packages/ros2-ros-workspace/ or distros/humble/packages/ros2-rclcpp/:

pkg_additional_info.yaml stays a single file per layer: it holds short per-package entries, and robostack-bot and the stale-build tooling edit it. (With #217 it also holds the dependency fixes that were in patch/dependencies.yaml.)

Open question

Today a distribution's entry replaces the shared one for that package. With folders, merging per file is more natural: e.g. humble adds one patch to a package that also has shared patches, without copying them.

Work

• vinca-rs: one folder scan instead of three (patches, tests, files).
• Move about 1,140 patches (46 shared, 250–320 per ROS 2 distribution), 35 test files, 4 test folders and the files/ folder, by script.
• Update tools/ (check_patches_clean_apply.py, check_orphaned_platform_patches.py, package_tests.py, import_distro.py, maintenance.py, robostack.py), the package-tests workflow, README, AGENTS.md and the skills.
• Check: the generated recipes are identical before and after.

After #217 is merged, so that only vinca-rs reads this layout.

— Claude (AI assistant), on behalf of @Tobias-Fischer. Sorry in advance: this issue was written by an AI agent.