Update to teem

{
  "description": "Draft teem changelog entries and Help Center articles from what shipped, and publish them when asked. Use when someone wants release notes, a changelog entry, a help article, or to tell customers something is live.",
  "included_files": [],
  "name": "release-drafting",
  "skill_md_contents": "---\nname: release-drafting\ndescription: Draft teem changelog entries and Help Center articles from what shipped, and publish them when asked. Use when someone wants release notes, a changelog entry, a help article, or to tell customers something is live.\n---\n\n# Release drafting\n\nEverything in this workflow starts as a draft. Drafts stay inside the team. Publishing is a\nseparate step that happens only when the person says \"publish\".\n\n## Find what shipped\n\n1. Call `list_posts` with `status: \"shipped\"` for requests the team marked shipped.\n2. Call `list_changelog` to see what's already written. An entry with `status: \"published\"` is\n   live; `status: \"draft\"` isn't. Its `posts` list shows which requests it covers.\n3. Requests that shipped but appear in no entry are the ones to write up. Call `get_post` on each\n   for the details and the customers' own words.\n\n## Write a changelog draft\n\n1. Write for customers: what they can do now and where to find it. Name the request it answers.\n   No internal names, tickets or code.\n2. Call `create_changelog_entry` with `title`, `body` and the request ids in `post_ids`. The\n   result has `status: \"draft\"`.\n3. Show the person the title and body and say it's saved as a draft in teem's changelog.\n4. To change a draft, call `list_changelog` first, check the entry is still a draft, then call\n   `update_changelog_entry`. On a published entry, a title or body edit goes live at once: say\n   so and confirm before you call it.\n\n## Publish\n\n- Call `publish_changelog_entry` only after an explicit \"publish\". It marks the linked requests\n  shipped and emails everyone who voted on them. Before you call it, add up the `votes` on the\n  linked requests and say how many people will get the email.\n- Publishing is safe to retry: teem never sends the same announcement twice.\n\n## Help Center articles\n\n1. `create_help_article` saves a new draft. Nothing goes public.\n2. To edit an article, call `get_help_article` right before `update_help_article` and pass its\n   `revision` as `expected_revision`. A revision conflict means someone else edited it;\n   read it again and show the person what changed.\n3. `get_help_article` returns the editable draft and the current publication side by side.\n   Customers see only the publication. Say which one you're quoting.\n4. Use `preview_help_article` to show how the Markdown renders, without saving.\n5. Call `publish_help_article` only after an explicit \"publish\", with the revision you just read.\n"
}