max / goingson

Drop a connective dash from a go-mcp tool description Tool descriptions are program output, so the no-connective-dash rule applies. The set_subtask_completed text used " -- " to join two sentences; a period does the same job. Swept the rest of the sites the triage row named (frontend JS strings, commands/attachment.rs, the go-mcp and got CLI help) against the full brand checklist. This was the only violation left; the rest read clean already.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-07-28 03:28 UTC

Signed with PGP, not checked

Commit: bcb4c91d671e030db6c4efa1bec490ffa010f5c2

Parent: 24f5494

1 file changed, +1 insertion, -1 deletion

M crates/go-mcp/src/tools/task.rs +1 -1

			@@ -720,7 +720,7 @@
720	720		"set_subtask_completed"
721	721		}
722	722		fn description(&self) -> &'static str {
723		-	"Check or uncheck a subtask: pass `completed` true or false. Idempotent: setting a subtask to the state it already holds is a no-op, so a retry cannot flip it back. `task_id` is the parent task, `subtask_id` comes from `get_task`. A linked subtask cannot be set here -- its state follows the task it links, so complete that task instead."
	723	+	"Check or uncheck a subtask: pass `completed` true or false. Idempotent: setting a subtask to the state it already holds is a no-op, so a retry cannot flip it back. `task_id` is the parent task, `subtask_id` comes from `get_task`. A linked subtask cannot be set here. Its state follows the task it links, so complete that task instead."
724	724		}
725	725		fn kind(&self) -> ToolKind {
726	726		ToolKind::Write(caps::task_subtask_update())