proposal_create write

Propose a new description for a document. Use it when issue_update refuses a description change because the editing model says it must be a proposal: a draft somebody else owns, a document in review while the workspace freezes review, or an approved document. body is the whole new text, not a patch, and note says why. The proposal waits for the document's owner, its assignee, who accepts or declines it; a document with no owner is decided by anyone. Accepting writes the description as an ordinary issue_update, so links into the document go stale as they would for any amendment. A work item is refused: edit it directly. Only the author may withdraw a proposal, with proposal_decide.

Arguments

Name	Type	Description
`body` required	string	the whole new description, markdown, at most 65536 characters; the owner sees it as a diff against the current text
`issue` required	string	the document, by key like ENG-142 or ULID; work items are edited directly with issue_update
`note`	string	why this change, at most 2000 characters; the owner reads it on the proposal card

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "body": {
      "description": "the whole new description, markdown, at most 65536 characters; the owner sees it as a diff against the current text",
      "type": "string"
    },
    "issue": {
      "description": "the document, by key like ENG-142 or ULID; work items are edited directly with issue_update",
      "type": "string"
    },
    "note": {
      "description": "why this change, at most 2000 characters; the owner reads it on the proposal card",
      "type": "string"
    }
  },
  "required": [
    "issue",
    "body"
  ],
  "type": "object"
}