Git Commit

Create semantic git commits that match the existing history in this repo. Analyze the actual diff to pick the right type, an optional scope, and a subject that reads well next to git log --oneline. Body explains the why — the diff already shows the what.

Commit format

<type>(<optional-scope>): <imperative subject>

[optional body — WHY, not WHAT]

[optional footer(s)]

• Subject: imperative mood, English, ≤ 70 characters. No trailing period.
• Scope: the single module or package most affected. Omit when the change is cross-cutting.
• Body: explain motivation (constraint, incident, decision). The diff already shows what.
• Footers: Closes #123, BREAKING CHANGE: …, etc.