Change a sprint's name, dates or goal (project_admin, or members with sprint_control: members — D141; D61). Send the version you read.

Planned and active sprints: name, start, end, goal. Closed sprints: name and goal only (dates are history) — dates on a closed sprint → 409 sprint_closed. end must not be before start (400). Publishes core.sprint.changed.

Rename a sprint, move its dates or change its goal. Requires project_admin, or a member when the project's sprint_control is members. Call list_sprints first and pass the sprint's version; send only the fields to change (name, start, end as YYYY-MM-DD, goal — null clears it) — all of them in ONE call. Planned and active sprints accept every field; a CLOSED sprint keeps its dates (they are history): sending start or end for it fails with 409 sprint_closed — change only name/goal there. end must not be before start (400). Moving an active sprint's dates changes its burndown date range. Do not use write_file on sprints/*.md for this.

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.