Problem

Issues and PRs without enforced structure end up missing acceptance criteria, repro steps, and invariant linkage. Reviews then become discovery sessions instead of approval gates.

Proposed solution

Port .github/ISSUE_TEMPLATE/{feature,bug,eval-regression}.md + config.yml (blank issues disabled). Port .github/pull_request_template.md. Port .github/CODEOWNERS with the repo owner as global owner. Port .github/branch-protection/README.md.

Acceptance criteria

• Opening a new issue forces choice between feature/bug/eval-regression (no blank option).
• Opening a new PR auto-fills the PR template.
• CODEOWNERS routes reviews to the repo owner globally.

Priority rationale

High: this template will be cloned by other people; the structured-issues norm is part of what they're cloning.

Depends on

#1