How Commit Guard generates commit messages.

Where generation happens

• IntelliJ: use the commit UI action to generate a message from the included changes.
• Terminal: blank commit messages can be prefilled through the managed prepare-commit-msg hook when the repo sidecar and daemon are active.

Template behavior

The saved default template is shared across IntelliJ and terminal generation.

• Templates can include Jira ticket placeholders like WD-<ticket-number>.
• Commit Guard tries to reuse a real WD-123 style ticket from the current Git branch or draft message.
• If no ticket is detected, the placeholder is preserved instead of inventing a value.

Expected shape

feat(WD-123): add editable commit templates

Description:
- Add a settings UI for viewing and editing commit templates.

Motivation:
- Let teams control commit format without changing code.

Changes:
- Added persistent template storage
- Added template editor UI
- Applied the default template to terminal commits

Terminal conditions

• The repo must have the managed hooks installed.
• IntelliJ must be open on the same repository.
• The local background service must be available.
• The commit message must be blank. Explicit messages such as git commit -m are left untouched.