rcourtman 098ba4eaa9 Hash relationship identity, not observation stamps, into plan resource versions ...

Docker adapters restamp relationship ObservedAt/LastSeenAt on every
~15s report, and the action planner folded those stamps into the plan's
resource version, so any reviewed action against a relationship-bearing
container (start, stop, restart, and the restored update) drifted to a
409 action_plan_drift before a human could read the review dialog and
click approve. Relationship edges now count by identity (source,
target, type, active, discoverer, metadata), the same
identity-versus-timestamp boundary change emission drew for issue
#1496. Found live: the UI update journey failed with plan drift on
every attempt slower than one report cycle.

2026-07-14 12:22:02 +01:00

..

planner_test.go

Hash relationship identity, not observation stamps, into plan resource versions

2026-07-14 12:22:02 +01:00

planner.go

Hash relationship identity, not observation stamps, into plan resource versions

2026-07-14 12:22:02 +01:00