@se-studio/contentful-cms 3.15.6 → 3.15.7

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @se-studio/contentful-cms Changelog
 
+## 3.15.7
+
+### Patch Changes
+
+- Document publish-state checks for linked templates and person entries before a production promote (release verification rule 1).
+
 ## 3.15.6
 
 ### Patch Changes

package/dist/contentful/cma-user-agent.d.ts

@@ -1,5 +1,5 @@
 /** SDK `application` value. Becomes `app cms-edit/<version>` in X-Contentful-User-Agent. */
-export declare const CMA_APPLICATION = "cms-edit/3.15.6";
+export declare const CMA_APPLICATION = "cms-edit/3.15.7";
 export declare function cmaClientOptions(accessToken: string): {
     accessToken: string;
     application: string;

package/dist/generated/version.d.ts

@@ -1,3 +1,3 @@
 export declare const CMS_EDIT_PACKAGE_NAME = "@se-studio/contentful-cms";
-export declare const CMS_EDIT_VERSION = "3.15.6";
+export declare const CMS_EDIT_VERSION = "3.15.7";
 //# sourceMappingURL=version.d.ts.map

package/dist/generated/version.js

@@ -1,4 +1,4 @@
 // Generated by scripts/generate-embedded-assets.mjs — do not edit manually.
 export const CMS_EDIT_PACKAGE_NAME = "@se-studio/contentful-cms";
-export const CMS_EDIT_VERSION = "3.15.6";
+export const CMS_EDIT_VERSION = "3.15.7";
 //# sourceMappingURL=version.js.map

package/docs/editor-tasks/publish-handoff.md

@@ -42,3 +42,13 @@ The signed-in Contentful user must have the matching role permission. AI Editor
 1. Do not apply a plan unless the user has said yes for that plan id.
 2. Do not claim the site is updated until apply succeeds.
 3. There is no scheduled publish.
+
+## Before a production promote
+
+Publishing in Contentful is not the same as a git promote. Before merging integration → production when new or changed entries are involved:
+
+1. List every page, **template**, **person** / person-type, and other linked entries the live pages render through.
+2. Confirm each is published in the production environment with **no pending drafts** (CDA vs CPA, or `check-publish-state`).
+3. Record the result on the promote PR.
+
+Shared templates and person entries are easy to leave draft-only while the page looks fine in preview — that is what broke Brightline provider headshots (7 Oct 2026). Full rules: se-core-product `docs/RELEASE_VERIFICATION.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/contentful-cms",
-  "version": "3.15.6",
+  "version": "3.15.7",
   "description": "CLI tool for AI agents to edit Contentful drafts and, when the user's role allows it, publish after an explicit yes",
   "repository": {
     "type": "git",

package/skills/core/SKILL.md

@@ -867,6 +867,17 @@ cms-edit index dump --reference-only          # Full catalog snapshot in termina
 
 If someone else also changed an entry, ask all versus mine and `publish choose`. The Contentful role must allow it. Unpublish, archive, and revalidate use the same plan-then-yes rule. Do not apply a plan on your own.
 
+### Before a production promote
+
+When pages that use **templates**, **person** entries, or other linked content are about to go live, verify publish state **before** merging the promote (release verification rule 1):
+
+1. List the page(s), linked **template**(s), **person** / person-type entries, and any other content stack pieces the live render walks.
+2. Confirm each is published in the production environment with no pending drafts — compare CDA (Delivery) vs CPA (Preview), or use `@se-studio/site-check/publish-state` / `check-publish-state`.
+3. Record results on the promote PR. A Nick override never skips this check.
+4. Do not assume publishing the page alone published a shared template or person — those often need their own publish (and template webhooks refresh pages that use them).
+
+See `packages/skills/references/agent-session/release-verification.md` and `docs/editor-tasks/publish-handoff.md` (in contentful-cms).
+
 ## Concurrent Sessions
 
 Use `--session <name>` or `CONTENTFUL_CMS_SESSION=<name>` to isolate parallel workflows.