Commit Release Notes

Keep three kinds of text separate: the short commit description, detailed notes on that commit, and release-wide marketplace publication notes. Writing detailed notes does not publish a release.

The #297 interface is implemented; see verification evidence and remaining live checks. If installed source branch commit --help lacks the notes options, check the installed build; version 0.5.8 alone does not distinguish builds before and after the merge. Prepare the notes file without bypassing the CLI's validation, organization checks, confirmation, or explicit selection.

Choose the requested operation

• Draft notes: inspect changes and prepare text/files; drafting alone does not authorize a commit.
• Commit with notes: apply the draft workflow, preserve the authorized branch/config scope, then use the CLI transport below.
• Read notes: follow retrieval below; no mutation is needed.
• Add notes to an already completed commit: inspect available metadata, but do not create a replacement commit. #297 defines commit-time input, not an edit-existing-commit operation; report that boundary if no supported edit operation exists.