chore(pulse): format report and polish workflow 🧹

.github/workflows/pulse.yml

@@ -73,11 +73,24 @@ jobs:
           ${{ steps.pulse.outputs.report }}
           EOF
 
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Format report with pre-commit
+        run: |
+          pip install pre-commit
+          # Run the Markdown formatting hooks on the generated report only.
+          # pre-commit exits non-zero when it reformats a file, so don't fail the job.
+          pre-commit run mdformat end-of-file-fixer trailing-whitespace \
+            --files reports/${{ env.DATE }}.md || true
+
       - name: Create Pull Request
         uses: peter-evans/create-pull-request@v8.1.1
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: "Add weekly pulse report for ${{ env.DATE }}"
+          commit-message: "docs: Add weekly pulse report for ${{ env.DATE }}"
           add-paths: reports/${{ env.DATE }}.md
           branch: ${{ env.SOURCE_BRANCH }}
           base: ${{ env.TARGET_BRANCH }}

reports/2026-06-08.md

@@ -1,14 +1,13 @@
 # 📊 GitHub Pulse Scout — areal-project/AReaL
 
-**Window:** 2026-06-01T04:35:04.613Z → 2026-06-08T04:35:04.613Z  
-**Issues fetched:** 14
+**Window:** 2026-06-01T04:35:04.613Z → 2026-06-08T04:35:04.613Z **Issues fetched:** 14
 
 ## Activity
 
 | Metric            | Count |
 | :---------------- | ----: |
 | 🆕 New issues     |     4 |
-| ✅ Closed issues   |     6 |
+| ✅ Closed issues  |     6 |
 | 📂 Currently open |     8 |
 
 ## Response efficiency
@@ -32,27 +31,45 @@
 
 ## 🔥 Hottest issues
 
-- [#1302](https://github.com/areal-project/AReaL/issues/1302) — [Roadmap] 2026 Q2 Milestones (💬 **8**)
-- [#1382](https://github.com/areal-project/AReaL/issues/1382) — [Question] areal 环境依赖问题 (💬 **5**)
-- [#1298](https://github.com/areal-project/AReaL/issues/1298) — [BUG] clear_batches() crashes non-DP-head ranks on TP/PP > 1 (regression from #1282) (💬 **4**)
-- [#1260](https://github.com/areal-project/AReaL/issues/1260) — [Feature] Migrate the primary megatron integration lib from `mbridge` to `megatron-bridge` (💬 **4**)
-- [#1243](https://github.com/areal-project/AReaL/issues/1243) — [RFC] Integrate Ray Core RDT for Weight Syncing (💬 **4**)
+- [#1302](https://github.com/areal-project/AReaL/issues/1302) — [Roadmap] 2026 Q2
+  Milestones (💬 **8**)
+- [#1382](https://github.com/areal-project/AReaL/issues/1382) — [Question] areal 环境依赖问题
+  (💬 **5**)
+- [#1298](https://github.com/areal-project/AReaL/issues/1298) — [BUG] clear_batches()
+  crashes non-DP-head ranks on TP/PP > 1 (regression from #1282) (💬 **4**)
+- [#1260](https://github.com/areal-project/AReaL/issues/1260) — [Feature] Migrate the
+  primary megatron integration lib from `mbridge` to `megatron-bridge` (💬 **4**)
+- [#1243](https://github.com/areal-project/AReaL/issues/1243) — [RFC] Integrate Ray Core
+  RDT for Weight Syncing (💬 **4**)
 
 ## 🤖 AI Summary
 
 # Pulse summary — last **7 days**
 
 ### Overall
-Activity is steady with modest throughput and healthy contributor diversity, but **21-day** average close time and **6** stale-tagged open items signal slower follow-through. Momentum is focused on roadmap planning and backend integrations rather than rapid bug triage.
+
+Activity is steady with modest throughput and healthy contributor diversity, but
+**21-day** average close time and **6** stale-tagged open items signal slower
+follow-through. Momentum is focused on roadmap planning and backend integrations rather
+than rapid bug triage.
 
 ### Trends & focus
-- Throughput is balanced (4 new, 6 closed) yet aging: long-lived bugs and RFCs linger while roadmap issues dominate discussion (#1302, #1381).
-- **21.4 days** average close time and multiple stale labels point to limited maintainer bandwidth for cleanup and validation.
-- Participation is broad (**12** unique authors) with emphasis on backend upgrades (FP8, awex/CUDA-IPC, Ray RDT) and reliability regressions (#1298).
+
+- Throughput is balanced (4 new, 6 closed) yet aging: long-lived bugs and RFCs linger
+  while roadmap issues dominate discussion (#1302, #1381).
+- **21.4 days** average close time and multiple stale labels point to limited maintainer
+  bandwidth for cleanup and validation.
+- Participation is broad (**12** unique authors) with emphasis on backend upgrades (FP8,
+  awex/CUDA-IPC, Ray RDT) and reliability regressions (#1298).
 
 ### Recommendations
+
 - Triage and close or revive stale items to reduce noise and clarify priorities.
-- Set service-level targets (e.g., 7-day first response, 14-day close) for bugs and regressions.
-- Add short “help wanted” notes to roadmap and CC-labeled tasks to convert interest into progress.
+- Set service-level targets (e.g., 7-day first response, 14-day close) for bugs and
+  regressions.
+- Add short “help wanted” notes to roadmap and CC-labeled tasks to convert interest into
+  progress.
 
-<small>Generated on 2026-06-08T04:35:04.616Z by [GH Pulse Scout](https://github.com/oss-infra/gh-pulse-scout), a tool that analyzes GitHub issue data to provide insights into project health and trends with AI 💖.</small>
+<small>Generated on 2026-06-08T04:35:04.616Z by
+[GH Pulse Scout](https://github.com/oss-infra/gh-pulse-scout), a tool that analyzes
+GitHub issue data to provide insights into project health and trends with AI 💖.</small>