Hello Sterling !
On SLES we use zypper, on RHEL and CentOS we use yum and dnf (for RHEL >=8) to resolve the dependencies on CLIENT SIDE.
Those rpms that are initially missing on the server are downloaded dynamically and propagated to package servers and the agent which requires them and finally agent downloads all the required stuff .
In theory for N client machines one may have N different sets of rpms that will be installed in the scope of the same policy, thus it makes the tracking part very challenging. Even without dependencies in a policy there might be M updates and only K of them will be installed and K may be different on each client.
On each client you may somehow see what was downloaded and installed from the agent logs (probably more verbosity needs to be added), but this is not a user friendly approach...
We do not have reports showing "what was installed due to policy X rollout on agent Y" in the latest release as well.
You may see the list of installed rpms on agent X in the "Software" section of a Computer view (Manage->Computers)
Please clarify what you mean by tracking and how do you envision displaying this tracking info.
Regards,
Artur