diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 26cef37e..414a56f0 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -24,13 +24,13 @@ jobs:
       - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10.3.0
         with:
           repo-token: ${{ steps.app-token.outputs.token }}
-          days-before-stale: 60
+          days-before-stale: 28
           days-before-close: 7
           stale-issue-label: stale
           stale-pr-label: stale
           stale-issue-message: >
             This issue has been automatically marked as stale because it has not had
-            any activity in the last 60 days. It will be closed in 7 days if no
+            any activity in the last 28 days. It will be closed in 7 days if no
             further activity occurs.
           close-issue-message: >
             This issue has been automatically closed because it has been stale for
@@ -38,7 +38,7 @@ jobs:
             reopen the issue.
           stale-pr-message: >
             This pull request has been automatically marked as stale because it has
-            not had any activity in the last 60 days. It will be closed in 7 days
+            not had any activity in the last 28 days. It will be closed in 7 days
             if no further activity occurs.
           close-pr-message: >
             This pull request has been automatically closed because it has been
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9e6ba882..7db3d8bb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -204,7 +204,7 @@ state why it remains valid. If there is genuinely no user-visible change, say
 so and provide a concrete reason; deleting the evidence section is not an
 exemption.
 
-### Review Enforcement
+### Review enforcement
 
 The automated reviewer performs one unified review of correctness, repository
 guidance compliance, pull request quality, and evidence. It independently
@@ -238,6 +238,16 @@ verify a trustworthy result, in which case it applies `review:automation-failed`
 Each completed review creates a new comment tied to its reviewed HEAD so the
 conversation remains chronological. Previous review comments are not rewritten.
 
+### Keeping PRs active
+
+Stale PRs add review load and make it hard to tell what's still being worked on, so the stale bot keeps the open list current. A PR with no activity for 28 days is automatically labeled `stale`, and closed 7 days later if it stays inactive. To keep a PR open:
+
+- Push updates or respond to review feedback
+- Leave a comment if you're waiting on a reviewer
+- Add the `pinned`, `security`, or `help wanted` label to exempt a long-running PR from the stale bot
+
+Reopening a closed PR is fine if it becomes relevant again.
+
 ## Project Structure
 
 ```