Delete a doc (members). It stays in the history and can be brought back with restore_doc_version.
delete_docDelete a doc (members). It stays in the history and can be brought back with restore_doc_version.
Pass the version from get_doc. Only delete when the user asked for it. The doc stays in its history and restore_doc_version brings it back. Never delete a doc to "fix" a bad edit — use get_doc_history + restore_doc_version instead.
WRITE: version must be the version from your latest read of this file (get_issue for issues, list_comments for comments, list_sprints for sprints, get_doc for project docs, read_file for md files). If the file changed since, the call fails with 409 version_conflict and the error contains the current file (details.current, details.current_version): re-read it, re-apply your change on top of the current content and retry with the new version. Never overwrite someone else's change blindly — if your change and theirs disagree, ask the user which to keep.
You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Project docs (spec D76): `brief` = why the project exists, goals, business and tech structure; `notes` = working notes / progress; `handoffs` = hand-over to teams or the whole project; `company_brief` = the company's rules and guidelines (read-only in project routes). | |
| slug | Yes | File name of a doc without `.md`: lowercase a–z 0–9 and `-` (brief, notes, company brief) or `H-{n}` (handoffs). | |
| version | Yes | Version of the file you read. Required on every delete (spec principle 7). | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |