The folder-trust prompt now lists commands a repo would run to mint HTTP headers.
What's wrong with this entry?
The folder-trust screen lists commands the repo's own settings would run to mint HTTP headers, alongside the existing marketplace, OpenTelemetry and proxy helper warnings, so a repo cannot introduce a command that runs on first fetch without appearing in the prompt.
- The preview now walks
extraKnownMarketplacesincluding alias keys, and lists URL-source and per-pluginheadersHelperentries plus command-source plugin entries, rendered as<key>: <command> → <url>with truncation. - Project and local
.mcp.jsonand settings MCP servers that declare aheadersHelperare listed too. - Trust telemetry gained
hasRepoHeadersHelpers. - Dependency resolution will not auto-install a plugin whose archive is fetched through an entry
headersHelper; that requires an explicit/plugin install. - Plugin autoupdate gained the failure classes
entry_helper_disabled_by_policy,entry_helper_remote_policy_unconsentedandentry_helper_not_inlined, plus deferred and policy-blocked counters.
This folder runs commands to mint HTTP headers (headersHelper), declared in , extraKnownMarketplaces[
Strings lifted out of the shipped bundle, so the claim above can be checked against them.