fix: revert to colon-based wildcard syntax for git permissions

[ashwin-ant]

Summary

Reverts #929 — the change from Bash(git commit:*) (colon syntax) to Bash(git commit *) (space syntax) broke git commit permissions in tag mode.

Problem

After #929, Claude's git commit commands were being denied despite Bash(git commit *) being in the allowed tools list. This caused tag mode runs to fail to commit and push changes (e.g. this run on issue #206).

The colon-based syntax (Bash(git commit:*)) is what the Claude Code CLI actually uses for matching — the space syntax doesn't work correctly.

[claude]

This git permission list is duplicated in src/create-prompt/index.ts (lines 60-66). That duplication is what allowed the original regression — #929 changed the syntax in both places, but there's no shared constant enforcing consistency. Consider extracting these 7 strings into a shared constant (e.g., GIT_BASH_TOOLS in a common module) to prevent future drift. Not blocking for this fix, but worth a follow-up.

Also, test/modes/tag.test.ts is a stub with no behavioral tests, so these lines have zero test coverage. If the syntax were reverted here but not in create-prompt/index.ts, no test would catch it.

[claude]

PR Review

This is a clean, well-scoped revert that fixes a real regression. The change is correct -- all occurrences of the space-based syntax have been updated to colon-based syntax across both code paths and tests, and existing docs already use colon syntax consistently.

See inline comment on src/modes/tag/index.ts for the one follow-up suggestion (extracting duplicated tool lists into a shared constant to prevent this class of regression).