Un-recommend stalls on products with large attestation history

Problem

In the live browse.dot app, un-recommending a frequently recommended product can remain busy indefinitely. Epoca source-bound packaged-app validation reproduced this after a successful recommendation: run 30854620557 timed out after 900 seconds while the product performed recipient-scoped light-client reads.

revokeLabel enumerates the recipient’s recommendations and launches one getAttestationById contract query per record concurrently. The reproduced target currently has 15 matching records while the current product account has one. A direct chain measurement confirms the attester-scoped lookup finds the live record (id=151, schema=5) through one batched record query in about 2.2 seconds over RPC. The recipient-first fan-out overwhelms the in-app light client even at this modest global count.

Expected

Revocation should look up the current product account’s live attestation with bounded, batched reads and complete under the existing end-to-end timeout.

Start at revokeLabel and inspect how it enumerates recommendations and launches getAttestationById queries. Reproduce the large-attestation case with the mentioned packaged-app validation or RPC measurement, then verify that revocation uses bounded, batched reads for the current product account and completes within the existing end-to-end timeout.