chore(ci): revert stale.yml to shipping state after write-path verification

Stale write-path confirmed end-to-end (run 24503276447):
- Added "Stale" label to PR #2830 ✓
- Posted stale comment on PR #2830 ✓
- Statistics: "Added PRs labels: 1, Added PRs comments: 1"
- Side effects cleaned up (label removed, comment deleted)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Debug Agent

.github/workflows/stale.yml

@@ -6,7 +6,6 @@ name: Close stale issues
 on:
     schedule:
         - cron: 30 1 * * *
-    workflow_dispatch: # temporary — write-path verification
 
 permissions:
     issues: write
@@ -21,15 +20,15 @@ jobs:
             - uses: actions/stale@v10
               with:
                   repo-token: ${{ secrets.GITHUB_TOKEN }}
-                  stale-issue-message: This issue is stale because it has been open for 40 days with no activity. Remove the stale label or leave a 
+                  stale-issue-message: This issue is stale because it has been open for 40 days with no activity. Remove the stale label or leave a
                       comment, otherwise it will be closed in 10 days.
                   stale-pr-message: This PR is stale because it has been open for 40 days with no activity. Remove the stale label or leave a comment,
                       otherwise it will be closed in 10 days.
-                  days-before-stale: 1
+                  days-before-stale: 40
                   exempt-issue-labels: roadmap,backlog
-                  close-issue-message: This issue was automatically closed due to 50 days of inactivity. We do this to help keep the issues somewhat 
+                  close-issue-message: This issue was automatically closed due to 50 days of inactivity. We do this to help keep the issues somewhat
                       manageable and focus on active issues.
-                  close-pr-message: This PR was closed because it had no activity for 50 days. If you feel this was closed in error, and you would 
+                  close-pr-message: This PR was closed because it had no activity for 50 days. If you feel this was closed in error, and you would
                       like to continue the PR, please resubmit or let us know.
                   days-before-close: 10
-                  operations-per-run: 4
+                  operations-per-run: 150