[FOUNDATION] Create PULL_REQUEST_TEMPLATE/config.yml with routing rules

[ashleyshaw]

Create configuration file documenting PR template routing rules (which template to use for each branch type).

Details

• GitHub doesn't support automatic PR template routing based on branch names
• Need explicit mapping: feat/ → pr_feature.md, fix/ → pr_bug.md, etc.
• This config serves as canonical reference for automation and docs
• Format: YAML with branch patterns mapped to template filenames

Template Routes to Map

feat/ → pr_feature.md
fix/ → pr_bug.md
hotfix/ → pr_bug.md
refactor/ → pr_refactor.md
chore/ → pr_chore.md
docs/ → pr_docs.md
test/ → pr_test.md
perf/ → pr_perf.md
ci/ → pr_ci.md
build/ → pr_ci.md
deps/ → pr_deps.md (if exists) or pr_chore.md
security/ → pr_security.md (if exists) or pr_chore.md
design/ → pr_design.md (if exists) or pr_feature.md
a11y/ → pr_a11y.md (if exists) or pr_improve.md
release/ → pr_release.md
research/ → pr_research.md (if exists) or pr_feature.md

Acceptance Criteria

• PULL_REQUEST_TEMPLATE/config.yml created with all branch prefixes mapped
• Mapping aligns with BRANCHING_STRATEGY.md
• All existing PR templates referenced
• File includes comment explaining routing strategy

Metadata

Issue Type: Task
Priority: High
Phase: 1 - Foundation & Configuration
Effort: 1h
Depends on: #1

Project: Template Enforcement & Governance

[linear-code]

LS-855

[ashleyshaw]

Status Update: Backlog published to develop ✅

Template enforcement project backlog is now live. This issue is Phase 1 (Foundation) and blocks Phase 2 issues (#712–#716).

Complete backlog: .github/projects/active/template-enforcement-governance/ISSUES.md
Action plan: .github/projects/active/template-enforcement-governance/ACTIONS.md

---

Generated by Claude Code