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.
Feature-flag settings files are re-read against a pinned expected content instead of trusting one visit.
What's wrong with this entry?
Anonymous. No account, no email.
What
The startup settings context now resolves the expected contents of the flag settings file from a pinned value with a fallback, and new accessors read and replace that pinned value. The settings loader re-reads the flag settings file even when its path was already visited, if expected content is present.
Evidence
flagSettingsFilePinnedContent
Strings lifted out of the shipped bundle, so the claim above can be checked against them.