From 917342a27bece7a4bbdbce97e79049da6617093a Mon Sep 17 00:00:00 2001 From: Grant Date: Wed, 8 Jul 2026 18:24:38 +0200 Subject: [PATCH] docs: log respawn rollout across stack nodes --- CLAUDE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index c021717..495ce60 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -373,6 +373,14 @@ entries; correct forward with a new dated entry if something needs revising. rov_full.launch.py declares no such arg, so RECORD=false is silently ignored and bags record regardless. Both deferred to a dedicated DIR-9a recorder-rework session — do NOT wire RECORD into the current DIR-9 model. +- 2026-07-08 — Added respawn=True/respawn_delay=5.0 to failsafe_monitor, + motion_controller, ekf_filter_node, depth_node, mission_executor. Deliberately NOT + applied to: mavros_node (respawn could mask/worsen the chronic FCU-link instability + — belongs in that investigation), recording_manager (pending DIR-9a rework), + camera_node/feature_detector (perception not operational yet), foxglove_bridge + (viz-only). NOTE: failsafe_monitor respawn has a coverage gap during the 5s respawn + delay — no failsafe assessment in that window; flagged for future design + consideration. ---