This is completely wrong. Do not build a completely new way to deploy nats. Just use the existing deployment method in the module and create a score on top of the same method for the simple deployment.
That should be renamed to something harmony-reconcile-operator or fleet manager or distributed deployment reconcile operator . Capture the essence of the decentralized fleet (iot or datacenters or whatever) management.
Delete that, hardcoded subuids/gids is a bug waiting to happen when multiple users on the same machine
The feature is correct but the implementation of the nats node primitive is wrong, see previous comment.
This one looks good, we might be able to improve type safety a bit but it's already looking good to me.
a616204b1c
refactor(nats): extract typed single-node primitive; NatsBasicScore becomes a thin wrapper
9b35bc5314
refactor(iot): delete legacy AgentStatus path; event-driven aggregation is now authoritative
2f08643aa0
refactor(iot): DeploymentName + Revision newtypes; LifecycleTransition models deletion; fixes bugs #1 and #2 from the review
367d63cfba
test(iot/smoke-a4): clarify parity summary — matches are DEBUG-level so don't report them
MUCH better but still dumb. Why do we have to do mode from mode.as_str() ????