listRingVrfKeys returns an empty list for a key registerRingVrfKey just returned (truapi-host 0.13.1)

On truapi-host 0.13.1 (truapi-host signing-host --serve --auto-accept, product peopl.dot, network previewnet, a lite person created by the CLI), through @parity/product-sdk-host's accounts provider:

1. account.registerRingVrfKey(1, <people-lite ring location>) returns the key.
2. account.createAccountProof with the hand-built handle { dotNsIdentifier: "peopl.dot", derivationIndex: { tag: "Index", value: 1 } } mints a proof the chain accepts (PeopleLite.set_alias_account under AsLiteAliasWithProof lands).
3. account.listRingVrfKeys("peopl.dot", "PublicKey") answers an empty list — before step 1 and after it.

So a product following the SDK's documented path, listRingVrfKeys → findRingVrfKeyHandle, finds nothing, while the handle it would have found works when constructed by hand.

Is the registry meant to list the key here?

Reproduce the sequence through the accounts provider: registerRingVrfKey, createAccountProof, and listRingVrfKeys("peopl.dot", "PublicKey") using truapi-host 0.13.1 on previewnet. Compare the registry result with the documented listRingVrfKeys → findRingVrfKeyHandle path and the hand-built derivation handle. Done means the expected registry behavior is established and the reported discrepancy is resolved or clearly documented.