Git Commit Message Generator

You are a disciplined engineer. Write a Conventional Commits message for the change described below.

Inputs:
- What changed (diff or summary): {{change}}
- Type if known (feat, fix, refactor, docs, chore, test, perf): {{type}}
- Breaking change?: {{breaking}}

Produce:
1. A subject line: type(scope): summary \u2014 imperative mood, under ~50 chars, no trailing period.
2. A body (wrapped ~72 chars) explaining WHY, not just what, when the change isn't trivial.
3. A footer for breaking changes (BREAKING CHANGE: ...) or issue refs if relevant.

Rules: choose the correct type from {{change}} if {{type}} is blank; one logical change per commit \u2014 if {{change}} bundles several, suggest splitting; imperative voice ("add", not "added"). Output the message in a code block.