chore: quality review fixes + maintenance auto-close (#6)

* fix: bump-version log output and deploy script hardcoded project name

- scripts/bump-version.js: the success log always printed 'new → new'
  because it read pkg.version after mutating it, then .replace()'d
  next with itself. Save the previous version before mutation so the
  log correctly shows 'old → new'.
- package.json deploy script hardcoded '--project-name my-site'. If a
  user renamed the package, local 'npm run deploy' would silently
  target the wrong Cloudflare Pages project. Use \$npm_package_name so
  the deploy target follows the package name automatically.
- Add Python MCP Server to the Related Starters list; bold current.

* ci: close maintenance issue when CI is green

The existing open-issue-on-failure job opened a `maintenance`
labeled issue whenever the weekly CI run broke, but there was no
counterpart job to close that issue once the underlying problem
got fixed. As a result the 12 starters accumulated stale open
issues that made the repos look broken to outside visitors even
after every fix had landed.

The new close-issue-on-success job runs whenever the re-triggered
CI is green, lists all open issues with the `maintenance` label,
leaves a comment linking back to the resolving run, and closes
them. Future regressions will reopen a fresh issue, so no signal
is lost.

Author: heznpc

.github/workflows/maintenance.yml

@@ -48,3 +48,47 @@ jobs:
                 `---\n_Opened automatically by the Maintenance workflow._`,
               labels: ['maintenance'],
             });
+
+  close-issue-on-success:
+    needs: ci
+    if: success()
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            // Close any open maintenance issues — the most recent CI run
+            // proves the underlying problem is resolved. Without this job
+            // the issues opened by `open-issue-on-failure` linger forever
+            // and the repo looks broken to outside visitors even after the
+            // fix lands.
+            const open = await github.rest.issues.listForRepo({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'open',
+              labels: 'maintenance',
+            });
+            if (open.data.length === 0) {
+              console.log('No open maintenance issues to close.');
+              return;
+            }
+            const run = await github.rest.actions.getWorkflowRun({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              run_id: context.runId,
+            });
+            for (const issue of open.data) {
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issue.number,
+                body: `Maintenance CI is green again — closing automatically.\n\n**Run:** ${run.data.html_url}`,
+              });
+              await github.rest.issues.update({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issue.number,
+                state: 'closed',
+              });
+              console.log(`Closed issue #${issue.number}`);
+            }