chore(repo): add monthly curation workflow for community plugins

.github/workflows/curate-community-plugins.yml

@@ -0,0 +1,43 @@
+name: Curate Community Plugins
+
+on:
+  schedule:
+    # 1st of every month at 9am UTC
+    - cron: '0 9 1 * *'
+  workflow_dispatch: # allow manual trigger
+
+permissions: {}
+
+jobs:
+  curate:
+    if: ${{ github.repository_owner == 'nrwl' }}
+    permissions:
+      contents: write # to push branch
+      pull-requests: write # to create PR
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+
+      - uses: pnpm/action-setup@7088e561eb65bb68695d245aa206f005ef30921d # v4.1.0
+        with:
+          version: 10.28.2
+
+      - name: Setup Node
+        uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
+        with:
+          node-version: '24'
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Configure git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Assess and prune community plugins
+        run: pnpm exec tsx scripts/documentation/assess-community-plugins.ts --prune
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

astro-docs/src/content/docs/extending-nx/publish-plugin.mdoc

@@ -35,9 +35,17 @@ Nx provides a utility (`nx list`) that lists both core and community plugins. Yo
 }
 ```
 
-{% aside type="caution" title="Unmaintained Plugins" %}
-We reserve the right to remove unmaintained plugins from the registry. If the plugins become maintained again, they can be resubmitted to the registry.
-{% /aside %}
+### Ongoing maintenance requirements
+
+An automated check runs once a month and removes plugins that meet any of these criteria:
+
+- The GitHub repository no longer exists or has been archived
+- No npm publish in the last 24 months
+- The declared `@nx/devkit` (or `@nx/workspace`/`nx`) range does not support any of the last three Nx major versions
+
+The 24-month cutoff reflects the Nx release cadence. Nx ships a major version every six months, so a plugin with no publish in two years is four Nx majors behind — past the point where compatibility can be assumed.
+
+If a removed plugin becomes maintained again, you can resubmit it.
 
 Once those criteria are met, you can submit your plugin by following the steps below: