{"version":"2.1.261","anchor":"artifact-publish-mcp-context-includes-a-new-artifact-consent","canonical_anchor":"artifact-publish-mcp-context-includes-a-new-artifact-consent","heading":"Artifact publish MCP context includes a new artifact_consent_holdback flag","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/artifact-publish-mcp-context-includes-a-new-artifact-consent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Artifact publish MCP context includes a new artifact_consent_holdback flag\n\nArtifact publish now sends a new consent-holdback flag internally.\n\nThe Artifact publish payload sent for consent and telemetry purposes now includes an `artifact_consent_holdback` boolean, backed by a small new helper pair that reads a settable holdback predicate defaulting to true when unset.\n\n- Area: Artifacts\n- Names: `artifact_consent_holdback`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}