DappCommandSummary
Recognises the Canton Token Standard transfer inside a dApp submission so an approver can show what moves where instead of an opaque "a transaction".
The recognition is deliberately strict: transferOf returns a summary only for a submission whose commands are exactly one TransferFactory_Transfer exercise with the standard argument shape. Anything else is not an error, it is simply not a transfer the approver can vouch for, and the UI should fall back to describe plus the raw payload. An approver that guessed at half-parsed commands would show the user a summary the signed transaction is not obliged to match.
Functions
One human-readable line per command, for submissions transferOf does not recognise: the command kind plus the choice and template entity, e.g. Exercise AmuletRules_DevNet_Tap on AmuletRules. Unknown shapes degrade to a labelled placeholder rather than being dropped, so the approver never under-reports how many commands are being approved.
The token-standard transfer this submission asks for, or null when the submission is anything other than exactly one recognised transfer.