Inkblot commit messages

This convention is only required when the work has a Jira ticket. If there is no ticket, do not invent an ID, do not ask for a ticket, and do not restrict the subject.

Ticket work (required)

<TICKET-ID>: <Concise imperative summary>

1. Full Jira key, uppercase, one ticket per commit (e.g. POD2-2291, not pod2-2291 and not 2-2291)
2. Colon and space after the key, then an imperative summary (“Fix …”, “Add …”, “Rename …”)
3. Sentence case. One line. Aim for ~72 characters. Say the outcome, not a file list.
4. Put the ticket this commit belongs to in the subject — not every ticket on the PR, and not always the branch name.

Do not use Conventional Commits prefixes (feat:, fix:, chore:). The ticket is the classifier.

Multiple tickets on one piece of work