Release 2.1.6 (2026-06-04)

Bug fixes

• truncate tracking-issue comments to GitHub's size limit GitHub's addComment API rejects comment bodies longer than 65,536 characters. When a release phase failed with a large detail payload (e.g. the confirm-main phase captured a multi-minute CD watch log into ReleaseError.detail), comment_phase_failed tried to post the whole thing and crashed the release in its own failure-reporting path.

Enforce the limit at _comment(), the single choke point every tracking-issue comment flows through. Oversized bodies keep the head (the marker comment and the structured phase/command/error preamble) and the tail (where failure logs put the actual error), dropping the middle with a '[... N characters truncated ...]' marker. This protects the failure, completion, and close-summary callers alike.