Integrate health monitor v0.1.0

[xbattlax]

Summary

• pin xbattlax/health-monitor release v0.1.0 in the Raspberry Pi Jazzy
  runtime installer and the Jazzy development image
• assert the installed package and exact release in the real arm64 build job
• exercise the ROS 2 deadman path end to end, including a roster published
  before monitor startup and MCU-heartbeat suppression after a critical
  component becomes stale
• regression-test pinned detached checkouts and document the runtime command,
  QoS contract, and intentional ref override

Why

This turns the stack-health prototype accepted in makerspet/oomwoo#36 into a
reproducible runtime dependency instead of leaving it as an unbuilt design
artifact. It complements the source migration in makerspet/oomwoo#47 and
keeps the safety monitor available on the lower-cost Pi runtime profile.

Verification

• shellcheck -S error and bash -n for all shell scripts
• python3 -m unittest ci/test_runtime_benchmark.py
• python3 ci/test_sim_mcu_serial.py
• bash ci/test_updates_pocket.sh
• bash ci/test_pinned_source_ref.sh
• actionlint
• Jazzy package build in makerspet/oomwoo:jazzy-dev
• real inter-process ROS 2 smoke:
  PASS: latched roster armed the late monitor; stale work stopped the MCU heartbeat

[xbattlax]

Post-push verification is complete:

• Static + unit checks: passed
• Full runtime install (arm64, real build): passed in 6m 6s
• the full installer built and exposed oomwoo_health_monitor
• the checkout resolved exactly to release v0.1.0
• the real ROS 2 smoke received a roster published before monitor startup, armed
  the stack, detected a stale critical work path, and stopped the MCU heartbeat
• the simulated serial link also passed on arm64

Review sweep: no issue comments, reviews, inline threads, or failing checks.