Branch prefixes do not cover every commit prefix in git.md

[braboj]

As a maintainer of a downstream project, I want the branch-prefix rule to name a prefix for every commit prefix so that a branch carrying only tests, a refactor or a style change has a compliant name without a judgement call.

What

templates/base/core/git.md allows seven commit prefixes (feat:, fix:, chore:, docs:, refactor:, style:, test:) and four branch prefixes (feat/, fix/, chore/, docs/). A branch whose one commit is test: … has no prefix that names what it does. Either add test/, refactor/ and style/ to the Branching list, or state that those three commit prefixes branch as chore/.

Why

Measured in pxtrend-prm on 2026-09-18: a branch named test/both-backends was renamed to chore/integration-both-backends before its first push, because the project's CLAUDE.md inherits the four-prefix list verbatim. The rule is applied on every branch, so the gap is met on every test-only or refactor-only change, and each downstream project resolves it its own way.

Acceptance criteria

• The Branching section of templates/base/core/git.md names a branch prefix for every commit prefix the Commit messages section allows, or states the mapping for the ones it does not list
• Any generated context file, example or check that restates the branch list is regenerated or updated in the same pull request