Roadmap: Prepare rclnodejs for ROS 2 Lyrical Luth

[minggangw]

ROS 2 Lyrical Luth is expected in May 2026 as the next ROS 2 LTS release. For rclnodejs, the main work before release is support enablement rather than major API redesign.

Key Focus

• Add lyrical to distro detection and internal version mapping.
• Add Lyrical to docs, CI, prebuild workflows, install logic, and native-loader resolution.
• Keep Rolling green and use it as the main pre-release signal for Lyrical readiness.
• Review RMW support for the Lyrical cycle, especially rmw_zenoh_cpp compatibility and default-policy handling.
• Define a clearer support policy for Humble, Jazzy, Kilted, Lyrical, and Rolling.

Roadmap Checklist

• Add lyrical to distro detection and runtime mapping.
• Add Lyrical to README.md and scripts/npmjs-readme.md.
• Add Linux x64 Lyrical CI coverage.
• Add Linux ARM64 Lyrical CI coverage if upstream packages are available.
• Add Lyrical to prebuild generation and artifact naming.
• Update install and native-loader logic for Lyrical binaries.
• Keep Rolling green and treat relevant failures as Lyrical blockers.
• Define support levels for Humble, Jazzy, Kilted, Lyrical, and Rolling.
• Review rmw_zenoh_cpp support and the default RMW policy in lib/rmw.js.
• Validate newer graph and service endpoint APIs on Rolling and Lyrical.
• Verify rcl_logging_implementation behavior with rclnodejs initialization.
• Add Windows Lyrical coverage once upstream Windows artifacts are stable.

Support Policy

• Full support: Lyrical, Jazzy, Rolling
• Transitional support: Kilted
• Compatibility support: Humble