{"version":"2.1.265","anchor":"new-helper-reads-a-typelock-slug-on-agentskill-type-objec","canonical_anchor":"frozen-artifact-type-publish-note-now-supports-a-customizabl","heading":"Type-locked Artifact publishing gets customizable messaging and a typeLock field","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-helper-reads-a-typelock-slug-on-agentskill-type-objec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Type-locked Artifact publishing gets customizable messaging and a typeLock field\n\nPublishing to a type-locked Artifact URL now shows a per-store customizable notice, backed by a new typeLock slug field\n\n**What**\n\nThe notice shown when publishing data files to a type-locked Artifact URL can now be produced dynamically per-store, based on `storeDeclared`, `release`, and `typeSlug`, instead of always showing the same fixed message. A new helper reads a `typeLock.slug` value, falling back to the existing `typeSlug` field when it's not set.\n\n**Why**\n\nThis points to a new `typeLock` field being introduced alongside `typeSlug`, and lets the message shown to users be tailored to the specific store and release involved rather than using generic wording.\n\n- Area: Artifacts\n- Names: `typeLock`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}