feat(cursor): plugin for Cursor in the shared skills layout

.release-please-manifest.json

@@ -1,3 +1,4 @@
 {
-  "dist/copilot": "0.1.1"
+  "dist/copilot": "0.1.1",
+  "dist/cursor": "0.2.2"
 }

CONTRIBUTING.md

@@ -82,7 +82,7 @@ Each host is its own release-please package (`dist/<host>`), with its own versio
 
 ### Mirror repos
 
-Some installs name a repo of their own instead of a folder here: `copilot plugin marketplace add ZenRows/copilot-zenrows` reads that repo's root. Such a repo is a mirror: `mirror: ZenRows/copilot-zenrows` in the host's `vars.yaml` makes each release of the host replace the mirror's contents with `dist/<host>/`, plus the host's marketplace catalogs at the same paths, listing only that host with `source` set to `./` (the mirror's root), and a banner in its README pointing here. So the catalog is edited in one place, and `npm run validate` fails if a mirrored host has none. Nobody edits a mirror by hand; only its deploy key can push to it.
+Some installs name a repo of their own instead of a folder here: `copilot plugin marketplace add ZenRows/copilot-zenrows` reads that repo's root, and so do the Cursor Marketplace and ClawHub. Such a repo is a mirror: `mirror: ZenRows/copilot-zenrows` in the host's `vars.yaml` makes each release of the host replace the mirror's contents with `dist/<host>/`, plus a banner in its README pointing here. If the host has marketplace catalogs, the mirror gets them at the same paths, listing only that host with `source` set to `./` (the mirror's root), so the catalog is edited in one place. A host that reads its plugin from the repo root, like Cursor or OpenClaw, needs no catalog. Nobody edits a mirror by hand; only its deploy key can push to it.
 
 - The release workflow runs `.github/workflows/mirror.yml` for each released host. It makes one normal commit (`release copilot-v0.1.2 from ZenRows/zenrows-integrations@<sha>`), never a force-push, and tags the mirror `v<version>`. No commit is made when nothing changed, so a re-run is safe.
 - It pushes with the deploy key in the `MIRROR_KEY_<HOST>` secret of the `release` environment. The key, the mirror's branch protection and its settings are in [iac-bootstrap](https://github.com/ZenRows/iac-bootstrap).

README.md

@@ -9,6 +9,7 @@ Each host's guide covers installing the plugin and signing in to Zenrows. You si
 <!-- hosts:start (generated by npm run render from platforms/; don't edit) -->
 | Host | Setup guide |
 |---|---|
+| Cursor | [dist/cursor/README.md](dist/cursor/README.md) |
 | GitHub Copilot | [dist/copilot/README.md](dist/copilot/README.md) |
 <!-- hosts:end -->