Yes great points!
That is why I think one specific way this can be handled is when resolving a comment, simply prompt for another “closing” comment, so it’s possible to see what was done to resolve the conversations. TargetProcess in fact has a great feature where you can configure workflow transitions to require a comment, that would be terrific to see in Fibery!
This is also what I had in mind with this suggestion:
With a feature like this, you could even use entities as “mini conversations” like in the Twist example I showed above. If you required a comment when moving to “closed” state, you can then be sure that those that are resolved have traceability as to what was done.