# #38 status (ppdata, 11 Oct)
- pwguard: parked (prewatch parked), mesh checks removed. stale.py (laneradar): cron retired by ops #1540.
- judgeguard + lanecheck: mesh already has freshness checks for judgeguard.ok / lanecheck.ok / radar3.beat. Both guards are FIXERS (restart laneradar3, requeue missing pools); the mesh only restarts units on stale files. Moving them = delete fixer logic.
- CONFLICT: tm-keepkill lists laneradar3 as KILL, guard-routing says lane radar is an input of aipick5 (KEEP); laneradar3 is active and lanes.db is read by ~10 /opt/hist scripts. Need Manager: KEEP or KILL laneradar3? KILL -> retire judgeguard, lanecheck with it (no migration). KEEP -> mesh restart-on-stale of radar3.beat (already present) is enough; retire both fixers after 24 h side by side.
- pdguard (112 lines): cron re-adder + unit checks; mesh already has 6 "M PP data ..." checks incl. cron lines. Remaining gap: chainlogs progress + disk (diskguard is Test Manager's). Retire after 24 h dry compare; not started because guard config edits need ops.