@contentrain/skills 0.9.1 → 0.9.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/skills",
-  "version": "0.9.1",
+  "version": "0.9.3",
   "license": "MIT",
   "description": "AI agent skills for Contentrain — workflow procedures, framework integration guides",
   "type": "module",
@@ -61,9 +61,9 @@
     "tsdown": "^0.21.0",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0",
-    "@contentrain/mcp": "3.3.1",
-    "@contentrain/rules": "0.7.1",
-    "@contentrain/wp-import": "0.2.2"
+    "@contentrain/mcp": "3.3.3",
+    "@contentrain/rules": "0.7.2",
+    "@contentrain/wp-import": "0.4.1"
   },
   "scripts": {
     "build": "tsdown src/index.ts --format esm,cjs --dts",

package/skills/contentrain/references/mcp-tools.md

@@ -93,6 +93,8 @@ Create or update a model definition (upsert).
 | `description` | string | No | Model description |
 | `content_path` | string | No | Framework-relative path for content files |
 | `locale_strategy` | string | No | `"file"` (default), `"suffix"`, `"directory"`, `"none"` |
+| `form` | object | No | Runtime-owned public form settings (Studio). Not a tool input — an existing block is preserved across structural edits and named in `preserved_blocks` |
+| `comments` | object | No | Runtime-owned public comments settings (Studio). Preserved the same way |
 
 Notes:
 - Upserts by model ID: existing model is updated, new model is created

package/skills/contentrain-migrate-wordpress/references/wordpress-mapping.md

@@ -50,11 +50,19 @@ WordPress status becomes Contentrain meta, not a field:
 | WP | Contentrain |
 |---|---|
 | `publish`, `inherit` | `published` |
-| `future` | `draft` + `publish_at` (the scheduled date survives) |
+| `future` | `published` + `publish_at` (a `future` post with no valid date fails the import) |
 | `pending` | `in_review` |
 | `trash` | `archived` |
 | everything else (`draft`, `private`, …) | `draft` |
 
+A scheduled post arrives as `published`, not as a draft, because `publish_at` is a
+delivery gate on top of status and never changes it: a past `publish_at` does not
+publish a draft, so `draft` + `publish_at` would keep a scheduled post invisible
+forever. Tell the user that whatever renders the site must honour the publication
+window — status alone is not enough, or an embargoed post ships early. The query
+generator and the Astro loader do this in public-build mode
+(`contentrain generate --published [--at <ISO>]`).
+
 Comments map by approval: `1` → published · `spam`/`trash` → archived · anything else → `in_review`.
 
 ## Custom fields
@@ -68,7 +76,7 @@ Inferred types are a guess from one value. Check `meta_fields` and `acf_fields`
 
 ## What is not imported
 
-Post types matching `attachment|nav_menu_item|wp_*|jp_*|pattern|revision|oembed_cache|customize_changeset|user_request|custom_css` are skipped and listed in `report.skipped_types`. Attachments are not skipped content — they arrive as the `media` collection.
+Post types matching `attachment|nav_menu_item|wp_*|jp_*|pattern|revision|oembed_cache|customize_changeset|user_request|custom_css` are skipped and listed in `report.skipped_types`, and so are theme / page-builder internals that store design rather than content: GeneratePress elements (`gp_elements`, `gp-elements`), GenerateBlocks styles (`gblocks_*`, `gblocks-*`), Elementor templates (`elementor_library`, `e-landing-page`) and form definitions (`wpcf7_contact_form`, `wpforms*`). Membership and other content-bearing CPTs stay; ACF field records stay too, since their cross-model parents are part of the lossless import. Attachments are not skipped content — they arrive as the `media` collection.
 
 Also outside the import: themes, widgets, plugin settings, users' passwords and roles, and the media **files** themselves (only their metadata and URLs come across).