refine pull request standards

Author: fqjony

docs/pull-requests.md

@@ -6,6 +6,7 @@ Useful pull requests are not just code dumps. They explain the operational chang
 
 - state the problem first
 - summarize the actual change in a short `Changes` section
+- describe the real diff between the base branch and the PR branch, not the idealized change you wish the branch contained
 - keep the scope coherent instead of mixing unrelated work
 - start from a branch that is reasonably fresh against the target base branch
 - include docs or examples when behavior or workflow changes

docs/todo.md

@@ -12,6 +12,7 @@
 - expose more explicit engineering-contract guidance for agents, including preferred edit boundaries and validation order
 - add machine-readable improvement priority or severity so agents can plan fixes more predictably
 - improve CLI and output UI so factor status, evidence, and guidance are easier to scan quickly
+- think through a dedicated `dev.kit` GitHub module or mode for PRs, issues, workflows, and repo operating signals
 
 ## Validation