@cleocode/skills 2026.5.128 → 2026.5.130

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.128",
3
+ "version": "2026.5.130",
4
4
  "description": "CLEO skill definitions - bundled with CLEO monorepo",
5
5
  "main": "index.js",
6
6
  "types": "index.d.ts",
@@ -19,6 +19,9 @@
19
19
  "url": "https://github.com/kryptobaseddev/cleo",
20
20
  "directory": "packages/skills"
21
21
  },
22
+ "engines": {
23
+ "node": ">=24.16.0"
24
+ },
22
25
  "scripts": {
23
26
  "validate:ops": "tsx scripts/validate-operations.ts",
24
27
  "test": "vitest run"
@@ -113,6 +113,10 @@ The DB schema `TASK_RELATION_TYPES` (`related`, `blocks`, `duplicates`, `absorbs
113
113
  ## Task Hierarchy (PM-Core V2 — ADR-088)
114
114
 
115
115
  **Canonical source:** `docs/adr/ADR-088-pm-core-v2-workgraph-relations-completion-criteria.md`.
116
+ Legacy charter ADR-073 remains authoritative for pre-PM-Core V2 semantics; ADR-088
117
+ governs the PM-Core V2 target. The **T10638 migration removed** legacy
118
+ `task_relations.groups` hierarchy reads and the dual-shape `label='saga'` fallback —
119
+ containment is now read exclusively from `tasks.parent_id`.
116
120
 
117
121
  | Tier | Prefix | type value | Scope-of-change |
118
122
  |---------|--------|------------|----------------------------------------------------|
@@ -136,14 +140,15 @@ from `parent_id`. The parent matrix is:
136
140
  Prefixes (`SG-`, `E-`) are DISPLAY + import-mapping only.
137
141
 
138
142
  **Non-containment (I3):** `task_relations` is for secondary graph semantics ONLY — dependency,
139
- ordering, cross-reference, evidence, supersession, provenance. `task_relations` MUST NOT satisfy
140
- containment, child listing, ancestor/descendant traversal, parent rollup, parent completion,
141
- nesting-budget, or closure semantics. The `groups` relation type is retired; do not use it for
142
- hierarchy.
143
+ ordering, cross-reference, evidence, supersession, provenance. A `task_relations` row
144
+ MUST NOT satisfy containment, child listing, ancestor/descendant traversal, parent rollup,
145
+ parent completion, nesting-budget, or closure semantics. The `groups` relation type is
146
+ retired for hierarchy; do not use `task_relations.groups` for parent/child semantics.
143
147
 
144
148
  ## Typed Completion Criteria (PM-Core V2)
145
149
 
146
- `task_acceptance_criteria.kind` is one of:
150
+ PM-Core V2 introduces **typed acceptance criteria** — `task_acceptance_criteria.kind`
151
+ is one of:
147
152
 
148
153
  | Kind | Requires `target_task_id` | Purpose |
149
154
  |------|--------------------------|---------|
@@ -153,10 +158,13 @@ hierarchy.
153
158
 
154
159
  **Key rules:**
155
160
  - A parent with children uses `child_task` criteria by default; these are **deterministic
156
- projections** from `parent_id` containment.
161
+ projections** from `parent_id` containment (the T10639 child_task-projection backfill
162
+ derives parent completion from child state — mixed-criteria mode is migration-only or
163
+ explicit advanced scope).
157
164
  - `text` and `evidence_bound` criteria must NOT use `target_task_id`.
158
- - Cancelled children do NOT automatically satisfy parent completion.
159
- - Adding child work under a done parent reopens affected ancestors.
165
+ - Cancelled children do NOT automatically satisfy parent completion; they require waiver
166
+ or replacement evidence.
167
+ - Adding or reopening required child work under a done parent reopens affected ancestors.
160
168
 
161
169
  ## Saga Operations (PM-Core V2)
162
170
 
@@ -182,10 +190,10 @@ cleo saga members <sagaId>
182
190
  individually. Do not use `task_relations.groups` as a fallback for hierarchy — it is
183
191
  non-containment only per I3.
184
192
 
185
- ## WorkGraph (PM-Core V2)
193
+ ## WorkGraph (PM-Core V2 — T10632/T10633/T10634)
186
194
 
187
- The WorkGraph subsystem provides scaffold validation, atomic application, and planning
188
- document generation:
195
+ The WorkGraph subsystem provides scaffold validation (T10632), atomic application (T10633),
196
+ and planning document generation (T10634):
189
197
 
190
198
  | Feature | What it does |
191
199
  |---------|--------------|
@@ -202,21 +210,26 @@ cleo workgraph validate --file scaffold.json --dry-run
202
210
  cleo workgraph apply --file scaffold.json
203
211
  ```
204
212
 
205
- ## Task Context (PM-Core V2)
213
+ ## Task Context (PM-Core V2 — T10629/T10630/T10631)
206
214
 
207
215
  Bounded task context with token budgeting for agent ergonomics:
208
216
 
209
217
  | Feature | What it does |
210
218
  |---------|--------------|
211
- | Task Context Pack | `coreTaskContext` returns targeted task information (identity, acceptance criteria, blockers, edges, activity) respecting a configurable token budget. Uses `TasksContextOmission` to track overages and provides expansion hints. |
212
- | Saga Context & Readiness | Saga-level aggregate rollups: completion percentages, ready-frontiers, and blocker enumeration across all member epics via `parent_id` containment. |
219
+ | Task Context Pack | The `tasks.context` operation (T10629) backs `coreTaskContext` (T10630): it returns targeted task information (identity, acceptance criteria, blockers, attached docs, graph edges, recent activity) respecting a configurable token budget (default 1500). Uses `TasksContextOmission` to track overages and provides expansion hints. |
220
+ | Saga Context & Readiness | Saga-level aggregate rollups: completion percentages, ready-frontiers, and blocker enumeration across all member epics via `parent_id` containment. Grouped readiness report via `orchestrate.report` (T10631). |
213
221
 
214
- Example — get task context for agent use:
222
+ The task-context **pack** is surfaced for agents via `cleo focus <taskId>` (compact, for
223
+ prompt injection) and `cleo orchestrate report <taskId>` (full grouped readiness). Do not
224
+ confuse this with `cleo context`, which is the separate context-WINDOW usage monitor
225
+ (`cleo context status` / `cleo context check`).
226
+
227
+ Example — get the task-context pack for agent use:
215
228
  ```bash
216
- # Full context with budget
229
+ # Full grouped readiness report for a task
217
230
  cleo orchestrate report <taskId>
218
231
 
219
- # Compact context for prompt injection
232
+ # Compact context pack for prompt injection
220
233
  cleo focus <taskId>
221
234
  ```
222
235
 
@@ -194,8 +194,8 @@ describe('ct-cleo SKILL.md — PM-Core V2 doctrine (T10645)', () => {
194
194
  it('documents WorkGraph scaffold subsystem (T10632/T10633/T10634)', () => {
195
195
  expect(skillContent).toContain('WorkGraph');
196
196
  expect(skillContent).toContain('T10632');
197
- expect(skillContent).toContain('cleo graph validate');
198
- expect(skillContent).toContain('cleo graph apply');
197
+ expect(skillContent).toContain('cleo workgraph validate');
198
+ expect(skillContent).toContain('cleo workgraph apply');
199
199
  });
200
200
 
201
201
  it('documents Completion Criteria with typed ACs (child_task / text / evidence_bound)', () => {