feat: enforce pull request readiness reviews

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,35 @@
+## Intent
+
+<!-- What user or maintainer problem does this solve? What behavior changes? -->
+
+## Non-goals
+
+<!-- What nearby behavior is intentionally outside this PR? Write "None" only when the scope is unambiguous. -->
+
+## Affected surfaces
+
+<!-- Name affected packages, runtimes, user-visible states, and persisted/external contracts. Explain why an apparently applicable runtime is unaffected. -->
+
+## Repository guidance
+
+<!-- List the AGENTS.md rules, matching project skills, required skill references, and nearest README/DOCUMENTATION.md files used for this change. Explain why each applies and the important constraints you followed. Do not merely list filenames. -->
+
+| Guidance | Why it applies | How the change complies |
+|---|---|---|
+|  |  |  |
+
+## Validation
+
+<!-- Report exact commands/manual checks and results. State what was not verified. Do not claim runtime behavior from type-check/lint alone. -->
+
+| Check | Result |
+|---|---|
+|  |  |
+
+## Visual evidence
+
+<!-- User-visible change: attach current before/after screenshots or recordings for the affected desktop/mobile, narrow/wide, theme, and interaction states. No visible change: explain concretely why the diff cannot affect rendered behavior. -->
+
+## Risks and failure behavior
+
+<!-- Cover relevant failure, rollback, cleanup, compatibility, security, performance, data-loss, and cross-runtime concerns. State "None identified" only with a concrete reason. -->