{"version":"2.1.233","anchor":"runtime-note-wording-now-varies-by-artifact-kind","canonical_anchor":"runtime-note-wording-now-varies-by-artifact-kind","heading":"Runtime note wording now varies by artifact kind","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/runtime-note-wording-now-varies-by-artifact-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Runtime note wording now varies by artifact kind\n\nClaude is told which capabilities each artifact type already provides, per kind.\n\n**What**\n\nThe note appended to productivity skills telling the model what the runtime already provides now picks its wording per kind, saying \"editing and persistence are\" for documents and \"editing, persistence, and commenting are\" for spreadsheets and slides, instead of one string claiming commenting for all three.\n\n**Details**\n\n- Driven by a per-kind commenting flag in the skill registry: document false, sheet and slides true.\n- The note is only appended when the artifact runtime advertises a capabilities field, and the skills are off in this build.\n\n**Evidence**\n\n`editing and persistence are`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}