Yes, you’re right, I’ve reproduced…I don’t see any way around it though. From my client logs I can see the source fixlet become relevant
At 14:21:39 -0500 - CustomSite_Check_This_Out (http://BES-Dev-Root:52311/cgi-bin/bfgather.exe/CustomSite_Check_This_Out)
Relevant - test baseline component relevance (fixlet:7722)
And I can see the Baseline containing the component become relevant:
At 14:22:38 -0500 - CustomSite_Check_This_Out (http://BES-Dev-Root:52311/cgi-bin/bfgather.exe/CustomSite_Check_This_Out)
Relevant - Test Baseline Component Relevance (fixlet:7723)
However it doesn’t look like there’s any point at which the client reports which components of the Baseline are relevant. That has to be calculated at the server/console based only on the source fixlets, so when the source fixlet changes it can’t tell anymore (and on mine it goes to 0 immediately upon un-syncing the component, same as you observe).
I don’t see a way around this right now.