Optimize PR processes (#1538)

Author: lightwalker-eth

.github/PULL_REQUEST_TEMPLATE/lite.md

@@ -1,6 +1,6 @@
 # Substantial PR
 
-> Use this template for PRs that change behavior, introduce new concepts, or would hurt if they broke.
+> Use this template for PRs that introduce significant changes.
 >
 > This template exists to keep reviewers from reverse-engineering context, risk, and intent from the diff.
 >
@@ -201,4 +201,5 @@ Call out:
 - [ ] I reviewed every line of this diff and understand it end-to-end
 - [ ] I'm prepared to defend this PR line-by-line in review
 - [ ] I'm comfortable being the on-call owner for this change
-- [ ] Relevant changesets are included (or explicitly not required)
+- [ ] Relevant changesets are included (or are not required)
+  - *Tip: [Changesets](https://ensnode.io/docs/contributing/releases/#adding-a-changeset-to-your-pr) should be created / written to optimize for the narrative of the next autogenerated [release notes](https://github.com/namehash/ensnode/releases).*

.github/PULL_REQUEST_TEMPLATE/substantial.md

@@ -1,11 +1,40 @@
-# Choose a PR template
+# Lite PR
 
-Use the appropriate template for this PR:
+## Summary
 
-- [**Light PR**](https://github.com/namehash/ensnode/compare/main...HEAD?template=lite.md)
-  For small, low-risk changes (mechanical refactors, formatting, dependency bumps).
+- What changed (1-3 bullets, no essays).
 
-- [**Substantial PR**](https://github.com/namehash/ensnode/compare/main...HEAD?template=substantial.md)
-  For behavior changes, consumer impact, new concepts, or high-risk work.
+---
 
-If you're unsure, that suggests this PR is a **Substantial PR**.
+## Why
+
+- Why this change exists. Link to related GitHub issues where relevant.
+
+---
+
+## Testing
+
+- How this was tested.
+- If you didn't test it, say why.
+
+---
+
+## Notes for Reviewer (Optional)
+
+- Anything non-obvious or worth a heads-up.
+
+---
+
+## Pre-Review Checklist (Blocking)
+
+- [ ] This PR does not introduce significant changes and is low-risk to review quickly.
+- [ ] Relevant changesets are included (or are not required)
+
+<details>
+<summary>PR Creation Tips</summary>
+
+- If this PR introduces significant changes or is higher-risk to review use the "[Substantial PR](https://github.com/namehash/ensnode/compare/main...HEAD?template=substantial.md)" template instead.
+- [Changesets](https://ensnode.io/docs/contributing/releases/#adding-a-changeset-to-your-pr) should optimize for the narrative of the next [autogenerated release notes](https://github.com/namehash/ensnode/releases). Optimize for how the resulting release notes will read to a developer in the ENS Ecosystem. Communicate all ideas with a positive frame.
+- The "Require PR Description Checks" GitHub Action will report a failing CI check on non-draft PRs where there are unchecked checkboxes in the description. You should therefore make your PR a draft PR until it is ready for review.
+
+</details>

.github/pull_request_template.md

@@ -1,11 +1,12 @@
-name: Require PR Checks
+name: Require PR Description Checks
 
 on:
   pull_request:
-    types: [opened, edited, synchronize]
+    types: [opened, reopened, edited, ready_for_review, converted_to_draft]
 
 jobs:
-  require-pr-checks:
+  require-pr-description-checks:
+    if: ${{ github.event.pull_request.draft != true }} # skip on draft PRs
     runs-on: blacksmith-4vcpu-ubuntu-2204
     steps:
       - uses: mheap/require-checklist-action@v2