Add edit_comment action to modify_reviews for comment task state transitions

[yan-xdt]

Motivation

modify_reviews currently exposes add_comment (which Swarm's create-comment endpoint restricts to taskState = open|comment) but no way to edit a comment afterwards. As a result, the task workflow states addressed and verified are unreachable through the MCP server, even though the Swarm REST API supports them via POST /api/v11/comments/{id}/edit. Agent-driven review flows (author fixes a task -> reviewer verifies it) currently have to fall back to calling the Swarm API directly.

Changes

• models: new EDIT_COMMENT action; TaskState extended with addressed/verified; validation keeps add_comment restricted to open|comment (matching the create-comment endpoint), and edit_comment requires comment_id plus at least one of body/task_state. review_id is not required for edit_comment since the endpoint is comment-scoped.
• services: edit_comment() wrapping POST /api/v11/comments/{id}/edit, sending only the fields provided (body, taskState, notify), following the same auth/response handling as the existing comment methods.
• handlers: dispatch branch for edit_comment.
• tools: edit_comment added to the modify_reviews action literal; task_state literal extended, with descriptions noting Swarm's constraints (only the comment author may edit; open -> verified requires an intermediate addressed step).
• README: action list entry.

Notes

• Purely additive; no behavior change for existing actions other than the stricter (previously unenforced) task_state validation on add_comment, which now fails fast instead of letting Swarm reject the request.
• All modified modules pass python -m py_compile; the change mirrors the existing add_review_comment/mark_comment_as_read implementation patterns.

🤖 Generated with Claude Code

[yan-xdt]

Validated this end-to-end against a production Swarm (API v11) with a real review, driving all calls through the MCP tools. Results:

• edit_comment with task_state: open -> addressed -> verified works as intended (each step reflected in subsequent comments queries; updated changes while edited stays null for state-only edits).
• Interesting finding: the server also accepted open -> verified directly (and verified -> open) — Swarm does not enforce the documented intermediate-step ordering server-side. I've adjusted the tool/service docstrings in 0b64192 to describe the ordering as the documented convention rather than a hard constraint.
• Body-only edit works and sets edited; body is a full replacement.
• Editing another user's comment returns HTTP 403 ("Only the comment author can edit the body of a comment"), surfaced cleanly as a status: error result.

🤖 Generated with Claude Code