docs(coreapi): correct cache-TTL comment to match cachedTokenTTL

e1ed824→main·

toothbrush·4w ago·1 file·+3 added/-2 removed

The struct doc claimed the cache TTL "matches the foreign-session token's lifetime (5 minutes)" while cachedTokenTTL is 4m. Describe the actual expires_in-honoring, buffered behavior.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Sessions

c6abc0aac791View transcript

[?
Review PR Comments on Cross-Jurisdiction RoutingClaude Code·Opus 4.8[1m]·2 steps](/content/gh/entireio/cli/session/2d6d6a51-951b-44ac-be1b-df81b4957e30#timeline-c6abc0aac791/index.html)

Changes

1

• internal/coreapi

• Mcross_juris_transport.go+3/-2

63 unmodified lines

64
65
66
67
68
67
68
69
70
71
72

63 unmodified lines

// recursion is a server bug we want to surface, not paper over.
//
// Per-origin token cache lives on the transport instance, scoped to one
// CLI invocation. TTL matches the foreign-session token's lifetime (5
// minutes).
// CLI invocation. A cached token's TTL honors the exchange response's
// expires_in (minus a safety buffer), capped at cachedTokenTTL so we
// never present a token near expiry.
//
// # Trust anchors for server-supplied URLs
//

Minternal/coreapi/cross_juris_transport.go+3/-2