DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Remote settings responses carry the identity that fetched them
Under the hood
Useful2Signal3
Settings
Recorded consent is now attributed to the identity that actually fetched the remote settings.
What's wrong with this entry?
Anonymous. No account, no email.
What
The remote settings fetcher now returns the identity used for the request on every path, including a cached 304, an empty 204 or 404, a parsed settings body and the caught-404 fallback. The caller hands it to the consent-recording step, so a recorded consent is attributed to the identity that actually fetched the settings.
Evidence
consentIdentity
Strings lifted out of the shipped bundle, so the claim above can be checked against them.