# test\(client-runtime\): each Read key signs its own asset URL · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/423865defb0022956d0a4894a497c9a5d5e9fc96)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 423865defb0022956d0a4894a497c9a5d5e9fc96

Requested commit: 423865defb0022956d0a4894a497c9a5d5e9fc96

Commit: 423865defb0022956d0a4894a497c9a5d5e9fc96

Tree: 18d7666fb24602244ba18c53b3a8292823f85592

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
test(client-runtime): each Read key signs its own asset URL

Proves through the production asset query family that one key shares a
request, a new key signs afresh, and the key never reaches the remote or
local media fallback RPC.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [83ba08b363902bec6689db7f2f516639f664b6ed](https://git.cafe/pingdotgg/t3code/commit/83ba08b363902bec6689db7f2f516639f664b6ed?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/423865defb0022956d0a4894a497c9a5d5e9fc96?format=markdown)