Add issue templates, CODEOWNERS, and commit/PR conventions

[dmccoystephenson]

Summary

Three of the four artifact gaps recorded in #89 are closed here, along with that issue's README.md nit.

• Commit/PR conventions (Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 4) — CONTRIBUTING.md now documents the branch prefixes already in use (feature/, fix/, docs/, chore/, each with a real branch from this repository's history as its example), the imperative commit-subject style, the squash-merge default, Closes #<number> linking, the HEREDOC + Co-Authored-By trailer convention, and when a CHANGELOG.md entry is expected. Step 8 of "Making Changes" previously asked only that the issue be linked "with #<number>", which does not close it on merge; it now specifies Closes #<number>.
• Issue templates (Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 2) — .github/ISSUE_TEMPLATE/bug_report.md and feature_request.md were added, with bracketed title tags matching the bug and improvement labels that already exist on this repository. The environment block asks for the dimensions this plugin actually varies over: plugin version, server software, Java version, database (H2 or MariaDB), and interacting plugins. Both templates carry a privacy prompt, since IP disclosure is the failure mode this plugin has been hardened against.
• CODEOWNERS (Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 3) — .github/CODEOWNERS was added in the minimal * @dmccoystephenson form requested.
• README nit (part of Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 6) — the "Known Bugs" link was moved from Roadmap into Support, and the bug-report link now points at /issues/new/choose so the new templates are offered.

Two claims from the #89 audit were re-verified against the full history before being written down, since that audit ran against a shallow clone:

• Squash merging is confirmed dominant (Remove /aaf ips command that exposes player IP addresses - Issue #44 #57 through Add unit tests for /aaf subcommand routing and tab-completion #87 all carry (#N) subjects), but 28f4a7b — the most recent commit — is a merge commit, so the wording does not claim merge commits are only historical.
• Both Co-Authored-By and Co-authored-by are in active use. Git matches trailer keys case-insensitively, so the doc names one preferred spelling and notes the other is equivalent rather than declaring existing commits wrong.

Not in this pull request

• Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 1 (root CLAUDE.md) — deferred deliberately. Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 itself notes that a new CLAUDE.md would overlap .github/copilot-instructions.md and that "the two should be reconciled rather than duplicated". That file is stale (tracked in .github/copilot-instructions.md is out of date (stale AafIpsCommand, missing encryption/ package, wrong test-framework status) #62) and editing agent-loaded configuration requires separate maintainer authorization, so writing a correct CLAUDE.md now would leave two agent-facing documents disagreeing with each other. Both are best done in one authorized pass.
• Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 5 (branch protection on main) — not verifiable from this session; the repository administration API is outside this session's permissions. Confirmation is still requested from the maintainer.
• Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 item 6's optional docker-build CI job — .github/workflows/* is a protected path that is not modified autonomously in this repository.
• .github/copilot-instructions.md is out of date (stale AafIpsCommand, missing encryption/ package, wrong test-framework status) #62 — deferred for the authorization reason above.
• Encryption #47 (Encryption epic) — an untouched tracking epic with no body; nothing actionable was scoped from it this cycle.

#89 is therefore referenced rather than closed, and a comment enumerating what remains will be left on it.

Test plan

• No Java source, plugin.yml, config.yml, migration, or build.gradle file is touched — the change is Markdown documentation and GitHub repository metadata only.
• The Build workflow passes on this pull request's head. It is the external anchor here; note that its scope does not extend to the changed files, none of which are compiled or executed.
• Manual verification after merge: opening a new issue offers both templates, and the applied labels match the bracketed title tags.
• Manual verification after merge: the maintainer is auto-requested as reviewer on the next pull request.

Part of #89.

This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).

[dmccoystephenson]

Self-review rubric, scored against the diff and command output rather than judgment:

• Scope: PASS — git diff --name-only origin/main...HEAD lists exactly CONTRIBUTING.md, README.md, .github/CODEOWNERS, .github/ISSUE_TEMPLATE/bug_report.md, .github/ISSUE_TEMPLATE/feature_request.md. Each maps to an item in Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89's "Requested work". No unrelated formatting or renames are present.
• Tests-new: N/A — no public method or function is added; the diff contains no Java.
• Tests-fix: N/A — no bug fix is present, so the stash-and-run check has nothing to exercise.
• Sibling structure: PASS — the two templates share an identical frontmatter block shape and ## -level section structure; CONTRIBUTING.md's new subsections sit at ### under "Making Changes" alongside the pre-existing "User-Facing Strings".
• Sibling renames: N/A — no identifier is renamed.
• Docs: PASS with one carve-out — README.md and CONTRIBUTING.md are updated in this diff. plugin.yml, COMMANDS.md, USER_GUIDE.md, CONFIG.md and config.yml describe runtime behavior that is unchanged. No CHANGELOG.md entry was added, because nothing a server operator would notice changed; that is the same bar the new "Changelog" subsection states. The carve-out is .github/copilot-instructions.md — see the findings below.
• Issue resolution: PASS — Align repository with dms-conventions (CLAUDE.md, issue templates, CODEOWNERS, commit/PR conventions) #89 is referenced, not closed, precisely because items 1, 5 and part of 6 are not done; the PR body enumerates each and why.
• CI: PASS — gh pr checks 90 --watch reports build pass on head 69da71e. Its scope does not extend to any changed file, so it confirms only that nothing was broken, not that the change is correct.
• Privacy: PASS — no code path is added. Both templates instruct reporters to redact IP addresses, and feature_request.md carries a "Privacy Impact" section asking whether a proposal would surface a player's IP, which pushes in the opposite direction from the disclosure this plugin was hardened against.
• plugin.yml — permissions: N/A — plugin.yml is untouched and no permission is referenced by the diff.
• plugin.yml — commands: N/A — no subcommand or completion branch is added.
• @OverRide coverage: N/A — no Java is added.
• MariaDB compatibility: N/A — no Flyway SQL is added.
• Encryption determinism: N/A — IpEncryption and the lookup paths are untouched.
• Migration safety: N/A — no migration is added.

Findings folded in from the diff read, none of them blocking:

• .github/ISSUE_TEMPLATE/feature_request.md:2-5 — the template is named "Feature Request" but tags titles [Improvement] and applies the improvement label. Tag and label match each other, which is what the convention asks for, but this repository's README maps "Planned Features" to the Epic label and "Planned Improvements" to improvement. Epic was deliberately not applied, since Encryption #47 shows it is used for large groupings rather than individual requests. Renaming the template to "Improvement" would remove the last of the mismatch, and is left as a maintainer call rather than churned here.
• .github/copilot-instructions.md:36 — "Reference the related GitHub issue in every pull request description" is now weaker than the Closes #<number> rule added to CONTRIBUTING.md, and the same file's "Contribution Workflow" says nothing about branch prefixes or commit style. Reconciling it was not attempted: it is agent-loaded configuration whose editing needs separate maintainer authorization, and it is already stale for unrelated reasons under .github/copilot-instructions.md is out of date (stale AafIpsCommand, missing encryption/ package, wrong test-framework status) #62.
• .github/ISSUE_TEMPLATE/ — no config.yml was added, so the blank-issue option remains available alongside both templates. That is deliberate; audit and epic issues filed on this repository fit neither template.
• README.md:33 — the bug-report link was pointed at /issues/new/choose, which only offers a chooser once the templates in this same PR land. The two changes are therefore coupled and should not be split across pull requests.
• One item was fixed during this review rather than left as a comment: the "Changelog" subsection originally said an entry "gets an entry under [Unreleased]", but CHANGELOG.md has no such heading today, making the instruction unfollowable. Commit 69da71e says to add the heading above the most recent release.

This review comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).