@cleocode/skills 2026.5.110 → 2026.5.111

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": "@cleocode/skills",
3
- "version": "2026.5.110",
3
+ "version": "2026.5.111",
4
4
  "description": "CLEO skill definitions - bundled with CLEO monorepo",
5
5
  "main": "index.js",
6
6
  "types": "index.d.ts",
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-documentor
3
3
  description: Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Coordinates ct-docs-lookup, ct-docs-write, ct-docs-review, ct-spec-writer, and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.
4
- version: 3.4.0
4
+ version: 3.5.0
5
5
  tier: 3
6
6
  core: false
7
7
  category: specialist
@@ -241,6 +241,29 @@ T10366 establishes the registry contract; T10367 (docs add) and T10368
241
241
  allocator — callers should continue invoking the existing writers
242
242
  (`cleo docs add` dispatch handler, `writeChangesetEntry`) directly.
243
243
 
244
+ **T10367 LIVE — `cleo docs add --type changeset` delegates to
245
+ `writeChangesetEntry`.** The dispatch handler in
246
+ `packages/cleo/src/dispatch/domains/docs.ts` now branches on
247
+ `payload.type === 'changeset'` and routes the call through the
248
+ canonical dual-write transaction. This eliminates the second writer
249
+ for the `changeset` DocKind (the SG-DOCS-INTEGRITY invariant) — the
250
+ bytes that land on `.changeset/<slug>.md` AND the SSoT blob are
251
+ byte-identical regardless of which verb the operator invoked. The
252
+ `cleo changeset add` CLI remains the friendlier authoring surface
253
+ (it prompts for every required frontmatter field) while
254
+ `cleo docs add --type changeset --file <path>` works for agents that
255
+ already have a fully-formed changeset markdown blob in hand.
256
+
257
+ Contract for the docs-add path:
258
+ - The input file MUST carry valid changeset frontmatter
259
+ (`id`, `tasks`, `kind`, `summary`). Missing → `E_REQUIRES_CHANGESET_VERB`
260
+ with a fix hint pointing at `cleo changeset add` for guided authoring.
261
+ - When `--slug` is also passed it MUST match the frontmatter `id`
262
+ (the frontmatter is canonical) — divergence → `E_SLUG_MISMATCH`.
263
+ - The LAFS envelope on success carries `data.type === 'changeset'`,
264
+ `data.slug`, `data.attachmentId`, and `data.sha256` — round-trip
265
+ identical to what `cleo changeset add` emits.
266
+
244
267
  ### Slug similarity warn (T10361 · closes T10167)
245
268
 
246
269
  `cleo docs add` runs a fuzzy-match check against existing slugs for the