What's Changed
Command auth cache reuse
You can now define a command auth config once and reuse it across requests by referencing just the cache_key. This brings command auth in line with how OAuth cache keys already work.
### First request seeds the cache
# @auth command argv=["gh","auth","token"] cache_key=github-cli
GET https://api.github.com/user
### Later requests reuse it
# @auth command cache_key=github-cli
GET https://api.github.com/user/repos
The first directive with a given cache_key seeds the command config for that environment. Follow-up directives inherit everything - argv, format, JSON paths, TTL and only need the cache key. You can still override header, scheme, and timeout per request.
If two directives try to use the same cache_key with conflicting settings (different argv, format, etc.), Resterm rejects it with error.