Cached remote settings now come with a companion attestation file, and both must load cleanly.
What's wrong with this entry?
The component that reads cached remote settings from disk now tracks two files rather than one, the cache itself and a companion file whose contents become an attestation string, reading the companion only after the cache and standing the whole view down if either read fails or is oversized.
- Priming is now skipped when a cache was already loaded this session, joining the existing skip reasons of ineligibility and the
CLAUDE_CODE_REMOTE_SETTINGS_PATHoverride. - The prime log line now reports whether the companion attestation was present.
- Applies only on the newer storage path; no new flag. Visible only in debug logs.
helper consent sidecar
Strings lifted out of the shipped bundle, so the claim above can be checked against them.