Promo eligibility status is cached on disk with a configurable max age

What

When Claude Code starts, it may check whether your account is eligible for a promotional credit and whether you have already claimed it. That answer used to be kept only in memory for the running program, so every startup asked the server again. Now:

• promoStartupStatusCache saves the eligible and claimed status in the global config file, separately for each account and each server address (endpoint).
• The saved answer is reused for up to 3600 seconds (one hour) instead of asking the server on every startup.
• The status is asked again after /clear, the command that starts a new conversation.
• The promo claim config gains statusMaxAgeSeconds (minimum 0, default 3600), which is passed as maxAgeSeconds to the status request.
• When statusMaxAgeSeconds is not zero, the local cache is no longer rewritten from the fetched status. Before, it was updated whenever the eligible or claimed value differed.

Why

In practice Claude Code makes fewer network requests about promotions when it starts. If a promo's status changes on the server, it can take up to the configured max age before a new startup notices.