Prepare the v0.2.0 release #35

Goal

Agree the scope and publish the next release after v0.1.0.

main has gained runtime/CI work, S32Z2 and X5H support, CAN–CARLA integration and SI supervision. Decide what ships in v0.2.0; do not treat all of #60 as an automatic release requirement.

Done when

• Confirm included changes and which remaining Complete SI-supervised Autoware and VisionPilot integration #60 work is a release blocker versus explicitly deferred. Use CycloneDDS as the current middleware direction (Proposal: ROS client API & middleware strategy — standardise on CycloneDDS, retire micro-ROS/XRCE, time-box a nano-ros evaluation #25), not the superseded micro-ROS proposal (Minimize actuation_module diff vs upstream Autoware (rclcpp facade + micro-ROS runtime) #14).
• Select the artifact matrix for Zephyr FVP/S32Z and FreeRTOS POSIX/S32Z2/X5H. State which hardware targets are build-from-source only and which require licensed SDK inputs.
• Decide whether Zephyr, CycloneDDS and Autoware pins change; record the actual versions and compatibility checks.
• Define the minimum CI/runtime/regression bar and verify the release workflow for the selected targets on the release commit.
• Update documentation/changelog.rst, upgrade/operator notes and known limitations, including unfinished supervision guarantees.
• Verify release artifacts and checksums, then publish v0.2.0 with the agreed scope.

Implementation progress belongs in #60 and its sub-issues; this issue tracks release decisions and readiness only.