There is no end to confusion on the part of the devops user when Gearset displays differences "differently" when comparison is org-org vs. org-VCS

For example: https://docs.gearset.com/en/articles/3491009-are-profile-permissions-showing-up-as-new-or-deleted-when-you-know-it-s-not-the-case

Gearset should apply a consistent principle - to see a Profile subcomponent, the compare filter should include both sides of the subcomponent (e.g. Profile + ApexClass to see ApexClassPermissions; Profile + Layout to see layoutAssignments; etc.)

If both sides of the subcomponent are not included in the filter, then there's no difference to show.

Note that these use cases must also be supported:

Profile deleted in org; org->VCS compare should delete .profile file
Custom field/object/layout/tab/class/page deleted in org and those type(s) in filter: Given repo cleaner, Profiles and Permission sets need not be included in filter but if present, then corresponding permissions/assignments should show as deleted