v0.9.1

capcom — v0.9.1 — 2026-10-19

This release makes capcom stricter and more predictable when a flag is given more than once: flags that take one value refuse a repeat, and body edits on updates now apply every repeat.

Breaking changes

• A flag that takes one value can no longer be repeated — giving --title, --status, --priority, --plan, --json, --standing or any other single-value flag twice to a capcom command now stops with a usage error (exit 2), --<name> given <n> times; give it once, before anything is read or written; before, the last value quietly won. What to do: give each such flag once in your scripts and agent prompts; flags that collect a list, such as --label and --dep, still take every repeat.

Fixed

• Repeated body edits in capcom update and capcom know update all apply — --body-append and the --body-replace-old/--body-replace-new pair can be given several times, and every replacement now runs in the order given, followed by every append, instead of only the last of each being used. If any replacement's old text does not appear exactly once, the whole update is refused with a message naming that pair (for example --body-replace-old #2 "<old>": …) and nothing is written; an unequal number of old and new texts is a usage error naming both counts.