From f1a4f42a1ddd9f469811740f9b122e385fee18d5 Mon Sep 17 00:00:00 2001
From: Austin Smith <austinsmith23@gmail.com>
Date: Sat, 11 Jul 2026 16:42:41 -0700
Subject: [PATCH] correct github templates

---
 .github/pull_request_template.md | 6 +-----
 AGENTS.md                        | 3 ++-
 2 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 2601541..4d0d7ca 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -12,11 +12,7 @@
      If the change involves motion or interaction, include a short video.
      Delete this section if not applicable. -->
 
-## Related Issues
-
-<!-- Link related issues, for example: Closes #123. Delete this section if not applicable. -->
-
 ## Validation
 
-<!-- List the builds, tests, and manual checks performed, including results.
+<!-- List the builds, tests, lint checks, and manual checks performed, including results.
      If none were performed, explain why. -->
diff --git a/AGENTS.md b/AGENTS.md
index f71fddf..66ed949 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -39,7 +39,8 @@ This file defines project constraints for coding agents working in this reposito
 - Write commit messages entirely lowercase. Use the imperative mood for the subject, keep each commit focused on one logical change, do not use type or scope prefixes, and do not end the subject with a period. Add a body when the reason or important tradeoffs are not clear from the subject.
 - Keep each pull request focused on one coherent change.
 - Write concise, specific, imperative pull request titles in sentence case. Do not use prefixes or trailing periods, and make the title understandable without the branch name.
-- Pull request descriptions must include `What Changed`, `Why`, and `Validation`. Include `UI Changes` only when the pull request changes the UI. Include `Related Issues` when applicable. Keep descriptions concise, self-contained, complete, and accurate to the final diff.
+- Pull request descriptions must include `What Changed`, `Why`, and `Validation`. Include `UI Changes` only when the pull request changes the UI. Keep descriptions concise, self-contained, complete, and accurate to the final diff.
+- Link any related issues in the pull request description; do not include issue numbers in branch names.
 - Review the complete diff before opening a pull request. Update the title and description whenever the scope changes, and remove unrelated changes.
 
 ## Issues