@se-studio/skills 1.5.1 → 1.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @se-studio/skills
2
2
 
3
+ ## 1.5.2
4
+
5
+ ### Patch Changes
6
+
7
+ - Cap `asset review --include-usage` with `--usage-limit` (default 50) to avoid hosted MCP timeouts on large spaces. Document usage-limit in asset-review help and media-review skill.
8
+
3
9
  ## 1.5.1
4
10
 
5
11
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@se-studio/skills",
3
- "version": "1.5.1",
3
+ "version": "1.5.2",
4
4
  "description": "SE Studio agent skills for marketing site development with Contentful CMS",
5
5
  "repository": {
6
6
  "type": "git",
@@ -123,10 +123,10 @@ Use this extension when the client wants a **reference guide** for all CMS image
123
123
 
124
124
  ```bash
125
125
  cms-edit index sync --space <space-key>
126
- cms-edit --json asset review --include-usage --include-passing --space <space-key> > /tmp/image-inventory.json
126
+ cms-edit --json asset review --include-usage --include-passing --usage-limit 0 --space <space-key> > /tmp/image-inventory.json
127
127
  ```
128
128
 
129
- Each asset in JSON includes `usages[]`: slug-bearing ancestors (page, article, tag, person, etc.) that ultimately use the asset.
129
+ Each asset in JSON includes `usages[]` when resolved: slug-bearing ancestors (page, article, tag, person, etc.) that ultimately use the asset. Default `--usage-limit` is **50** (set `0` for unlimited when running locally). JSON includes `usageLimit`, `usageResolvedCount`, and `usageTruncated` when `--include-usage` is set.
130
130
 
131
131
  To inspect how images relate to a specific page, use `cms-edit open --page-slug /<slug>` + `snapshot`, or `cms-edit peek --page-slug /<slug>` without affecting your session.
132
132
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: contentful-cms-regenerate-editor-pack
3
- description: "Regenerate cms-edit editor-pack for hosted MCP after registrations, guidelines, routing, or cms-editor docs change; validate, commit, and deploy."
3
+ description: "Regenerate cms-edit editor-pack for hosted MCP after registrations, guidelines, routing, or cms-editor docs change; validate, commit, and push (never manual vercel deploy)."
4
4
  ---
5
5
 
6
6
  # Regenerate cms-edit editor pack
@@ -83,28 +83,23 @@ git add cms-edit/editor-pack # or cms-edit/<site>/editor-pack
83
83
  git commit -m "chore(cms-edit): regenerate editor pack"
84
84
  ```
85
85
 
86
- ## Step 6 — Deploy
86
+ ## Step 6 — Publish (commit + push only)
87
87
 
88
- ### Customer repo with `cms-edit/host/` (SE Studio, Pedestal, Headwater)
88
+ **Absolute rule for agents:** hosted MCP is **never** published via `vercel deploy`, `pnpm cms-edit:deploy*`, or `deploy-cms-edit-host.sh`. Commit and push is the only deploy path for customer repos with `cms-edit/host/`.
89
89
 
90
- Commit `editor-pack/`, then push to the branch Vercel watches (usually `develop`). Changes under `cms-edit/**` trigger a host rebuild (`stage-site.mjs` copies committed artifacts).
90
+ ### Customer repo with `cms-edit/host/` (SE Studio, Pedestal, Headwater, Brightline, …)
91
+
92
+ Commit `editor-pack/` (and any other `cms-edit/**` changes), then push to the branch Vercel watches (usually `develop`). Changes under `cms-edit/**` trigger a host rebuild (`stage-site.mjs` copies committed artifacts on the Vercel build).
91
93
 
92
94
  ```bash
93
- git push
95
+ git push origin develop # or the site's configured deploy branch
94
96
  ```
95
97
 
96
- Manual deploy without pushing: `pnpm cms-edit:deploy` (single-site) or `pnpm cms-edit:deploy:<site>` (multi-site) — runs validate, stage, then `vercel deploy --prod` **from the repo root** with `--project <vercel-project>`. Do not `cd cms-edit/host` first (Vercel Root Directory is already `cms-edit/host`).
98
+ Do **not** run `pnpm cms-edit:deploy` or `vercel deploy` after this step.
97
99
 
98
100
  ### Customers without `cms-edit/host/` in their repo
99
101
 
100
- From `se-core-product`:
101
-
102
- ```bash
103
- ./scripts/deploy-cms-edit-host.sh \
104
- --config <customer-repo>/cms-edit/<site>/project.json \
105
- --editor-pack <customer-repo>/cms-edit/<site>/editor-pack \
106
- --prod
107
- ```
102
+ Rare layout — coordinate with the repo owner. Agents still must not run deploy scripts unless explicitly asked.
108
103
 
109
104
  ## Homepage slug reminder
110
105