Confirm terminating roles logic from spec

In https://github.com/php-tuf/php-tuf we are making sure we have the logic correct around terminating delegations. As we have updated our implementation of the spec from v1.0.9(the release when we started) to the most recent releases we have notice there has been some changes to wording in this area of the spec.

To make sure we get the logic correct for terminating delegations I have created this simple example to make sure our assumptions are correct(actually we don't all have same assumptions these are mine)

Constraints

term = terminating delegation
non-term = non terminating delegation
Priority: The roles in each level are ordered from left to right in the order they would appear under [delegations][roles]
All roles have paths = [‘assets/*’] (just to provide matches for every role only focus on terminating logic now)
Target being searched for = 'assets/always-match.txt’

Expected outcome

Expected role evaluation:
Targets -> A > B > C > D

Am I correct?

Begin with the terminating-delegation rules in the current TUF specification and the diagram/example in this issue; compare the expected Targets → A → B → C → D evaluation with the wording from v1.0.9 and newer releases. Done means the ordering and stopping behavior are confirmed or corrected, with the relevant specification wording recorded.