Key rotation: Verifier should support N keys.

Currently key rotation is difficult; the verifier needs to start verifying with the new key at the same moment the new key is used by the signer. In a high-traffic environment this can be near impossible without dropping requests.

It should be possible to pass multiple keys to the verifier, so that both old and new keys can be accepted for a period of time. Either N keys, or a static limit of two keys (current and previous) would work.

This could be represented by passing an array of keys per ID; using the first for signing, and using all of them for verification. Or… something else?

Look at the verifier class and its key management. The issue suggests modifying the verifier to accept an array of keys per ID, using the first for signing and all for verification. Start by reading the existing signing and verification logic to understand the current key interface. Determine how to adjust the API to support multiple keys without breaking existing usage. Check for any existing tests around verification to update.

由索引模型根据 Issue 内容生成。