Managed settings text corrected for npm marketplace entries

What

Organisations can control Claude Code through managed settings, settings an administrator sets for everyone. The built-in descriptions of two of these settings changed.

• The managed npm marketplace list (strictKnownMarketplaces) now says a scope wildcard such as "@acme/*" still parses in a managed list but matches no marketplace package. Before, the text said such an entry matched every package under the scope.
• The allowManagedPermissionRulesOnly description no longer lists npm-direct (package@npm) plugins as keeping their allowed-tools frontmatter. Frontmatter is the settings block at the top of a plugin file. The removed text covered plugins "whose recorded resolution a registry-pinned managed npm strictKnownMarketplaces entry names". It still says host and path patterns and enabledPlugins ids do not vouch.

The option-select list also changed:

• It accepts a declineValue.
• It passes disablePrintableKeybindings to its key handler.
• In the compact layout, an option's label can use its own labelColor.

Why

Administrators who relied on "@acme/*" wildcards or on npm-direct plugins keeping their allowed tools should review their managed lists. The members report only the description text. The sweep agent suggests enforcement may also have changed for managed organisations.