@contentrain/skills 0.9.2 → 0.9.3

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@contentrain/skills",
3
- "version": "0.9.2",
3
+ "version": "0.9.3",
4
4
  "license": "MIT",
5
5
  "description": "AI agent skills for Contentrain — workflow procedures, framework integration guides",
6
6
  "type": "module",
@@ -61,9 +61,9 @@
61
61
  "tsdown": "^0.21.0",
62
62
  "typescript": "^5.7.0",
63
63
  "vitest": "^3.0.0",
64
- "@contentrain/mcp": "3.3.2",
64
+ "@contentrain/mcp": "3.3.3",
65
65
  "@contentrain/rules": "0.7.2",
66
- "@contentrain/wp-import": "0.3.0"
66
+ "@contentrain/wp-import": "0.4.1"
67
67
  },
68
68
  "scripts": {
69
69
  "build": "tsdown src/index.ts --format esm,cjs --dts",
@@ -50,11 +50,19 @@ WordPress status becomes Contentrain meta, not a field:
50
50
  | WP | Contentrain |
51
51
  |---|---|
52
52
  | `publish`, `inherit` | `published` |
53
- | `future` | `draft` + `publish_at` (the scheduled date survives) |
53
+ | `future` | `published` + `publish_at` (a `future` post with no valid date fails the import) |
54
54
  | `pending` | `in_review` |
55
55
  | `trash` | `archived` |
56
56
  | everything else (`draft`, `private`, …) | `draft` |
57
57
 
58
+ A scheduled post arrives as `published`, not as a draft, because `publish_at` is a
59
+ delivery gate on top of status and never changes it: a past `publish_at` does not
60
+ publish a draft, so `draft` + `publish_at` would keep a scheduled post invisible
61
+ forever. Tell the user that whatever renders the site must honour the publication
62
+ window — status alone is not enough, or an embargoed post ships early. The query
63
+ generator and the Astro loader do this in public-build mode
64
+ (`contentrain generate --published [--at <ISO>]`).
65
+
58
66
  Comments map by approval: `1` → published · `spam`/`trash` → archived · anything else → `in_review`.
59
67
 
60
68
  ## Custom fields