@cleocode/skills 2026.11.1-canary.2 → 2026.11.1-canary.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/README.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # @cleocode/skills
2
2
 
3
+ > Part of [CLEO](https://github.com/kryptobaseddev/cleo#readme). Start with the root README; run `cleo <command> --help` for any command.
4
+
3
5
  CLEO skill definitions - bundled capabilities for AI agents.
4
6
 
5
7
  ## Overview
@@ -61,7 +63,7 @@ installability and every documented `cleo` command honest.
61
63
  | **ct-epic-architect** | Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. |
62
64
  | **ct-ivt-looper** | Runs a project-agnostic autonomous Implement-then-Validate-then-Test compliance loop on any git worktree. |
63
65
  | **ct-provenance-keeper** | Generates in-toto v1 attestations, SLSA-level provenance records, SBOMs (CycloneDX or SPDX), and sigstore/cosi… |
64
- | **ct-release-orchestrator** | Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo rele… |
66
+ | **ct-release-orchestrator** | Orchestrates CLEO releases: `cleo release cut <version>` tags the newest main commit with green CI, and release.yml writes the CHANGELOG from changesets and publishes. |
65
67
  | **ct-research-agent** | Multi-source research and investigation combining web search, documentation lookup via Context7, and codebase … |
66
68
  | **ct-spec-writer** | Technical specification writing using RFC 2119 language for clear, unambiguous requirements. |
67
69
  | **ct-validator** | Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cleocode/skills",
3
- "version": "2026.11.1-canary.2",
3
+ "version": "2026.11.1-canary.3",
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-dev-workflow
3
3
  description: Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.
4
- version: 3.4.0
4
+ version: 3.4.1
5
5
  protocol: contribution
6
6
  dependencies: []
7
7
  sharedResources:
@@ -14,7 +14,7 @@ compatibility:
14
14
  - gemini-cli
15
15
  license: MIT
16
16
  metadata:
17
- version: 3.4.0
17
+ version: 3.4.1
18
18
  tier: core
19
19
  install: harness
20
20
  covers:
@@ -26,7 +26,7 @@ metadata:
26
26
  - packages/core/src/hooks.ts
27
27
  - packages/core/templates/git-hooks/**
28
28
  - packages/contracts/src/git-hooks.ts
29
- lastReviewed: 2026-10-29
29
+ lastReviewed: 2026-11-02
30
30
  stability: stable
31
31
  ---
32
32
 
@@ -106,6 +106,12 @@ only on a parentless first commit (T13582); a later commit with that subject, or
106
106
  longer or different subject, still needs a task ID. A template change adds the
107
107
  previously shipped hash to `legacy-hashes.json` so installed copies refresh.
108
108
 
109
+ The managed pre-commit refuses CLEO runtime state staged at ANY path (T14189):
110
+ `cleo.db`/`brain.db`/`tasks.db` and their WAL sidecars by name, a `project-info.json`
111
+ naming a `"projectId"`, and `.cleo/config.json` or a byte-identical copy. It lists the
112
+ paths and `git reset -q -- <paths>`; `cleo doctor` runs the same rule (`staged_cleo_state`).
113
+ This repository's `.githooks/pre-commit` calls the template rather than copying it.
114
+
109
115
  `cleo init` and `cleo upgrade` no longer seed the CleoOS hub (Pi extensions, CANT
110
116
  workflows, justfile) into the global CLEO home (T13994, ADR-098); only the deprecated
111
117
  `cleo admin scaffold-hub` still does.
@@ -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. Carries the CLEO writing and review guides as references and coordinates 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.33.0
4
+ version: 3.36.0
5
5
  protocol: null
6
6
  dependencies:
7
7
  - ct-spec-writer
@@ -16,13 +16,13 @@ compatibility:
16
16
  - gemini-cli
17
17
  license: MIT
18
18
  metadata:
19
- version: 3.33.0
19
+ version: 3.36.0
20
20
  tier: core
21
21
  install: harness
22
22
  covers:
23
23
  - packages/cleo/src/cli/commands/docs.ts
24
24
  - packages/contracts/src/docs-taxonomy.ts
25
- lastReviewed: 2026-10-28
25
+ lastReviewed: 2026-11-02
26
26
  stability: stable
27
27
  ---
28
28
 
@@ -87,7 +87,11 @@ referenced elsewhere; absolute paths and other devices' paths are only
87
87
  reported. Each pruned row is first appended to
88
88
  `.cleo/audit/docs-publications-prune.jsonl`, and stale mirrors are only
89
89
  reported (republish, or ingest the edit with `cleo docs update`). Use it for store
90
- hygiene checks; it never edits doc content.
90
+ hygiene checks; it never edits doc content. `--apply` runs every repair class
91
+ at once; on a live shared store, scope it with `--only <class,…>` (T14174), for
92
+ example `cleo docs doctor --apply --only publication-ledger-drift`. The dry run's
93
+ `repairCounts` shows planned repairs per class, and an unknown class is refused
94
+ with the valid list.
91
95
 
92
96
  `cleo docs migrate` (T13360) imports legacy docs + history into the re-keyed
93
97
  conduit store inside the migration safety harness (pre-step backup, verified
@@ -729,9 +733,14 @@ cleo docs publish --for T1234 --to docs/feature-x.md
729
733
  Atomic tmp-then-rename. The published file ships in the next commit; the
730
734
  SSoT blob remains canonical and continues to track future versions.
731
735
 
732
- `--to` must resolve under the project root (a relative path resolves there)
733
- or inside a registered canonical task worktree; anything else is refused with
734
- `E_VALIDATION_ERROR` and nothing is created. `--dry-run` runs the same checks
736
+ `--to` must resolve under the project root or inside a registered worktree at
737
+ the project's canonical CLEO location (`<cleoHome>/worktrees/<hash>/<name>`,
738
+ any name); anything else is refused with `E_VALIDATION_ERROR` and nothing is
739
+ created. Run from such a worktree, a relative `--to` lands in that worktree, not
740
+ the root checkout, and the publication ledger records the repo-relative path
741
+ the merge makes true (T14135). `cleo docs status` reads a mirror the root
742
+ checkout has not pulled from the default branch, and reports one that sits only
743
+ in an unmerged worktree as `pending-merge`. `--dry-run` runs the same checks
735
744
  and writes nothing, so a dry run that passes means the real run will.
736
745
 
737
746
  ### Fetch the doc back by slug
@@ -827,9 +836,13 @@ cleo docs modernize --store # stored docs: re-kind
827
836
  Ambiguous classify and merge calls are judged by System One
828
837
  (`docs.modernize.classify`, `docs.modernize.merge`; rule fallback when it is
829
838
  unreachable) and recorded on each plan row. Apply stores survivors, folds
830
- duplicates in, supersedes the removed docs, rewrites relative links to
831
- `[[slug]]` wikilinks (recorded as `links-to` graph edges) and keeps every
832
- replaced byte under `.cleo/modernize/<runId>/` for rollback.
839
+ duplicates in, supersedes the removed docs, re-points relative markdown links
840
+ at the new paths (they still render on GitHub; `--wikilinks` opts into
841
+ `[[slug]]` instead), records every link as a `links-to` graph edge, edits a
842
+ file the plan marks `keep` only by re-pointing the hrefs the plan lists as
843
+ `linkFixes` (`link-fix` rows, so apply never does more than the dry run
844
+ showed), and keeps every replaced byte under
845
+ `.cleo/modernize/<runId>/` for rollback.
833
846
 
834
847
  ---
835
848
 
@@ -7,7 +7,7 @@ adrRefs:
7
7
  - ADR-063
8
8
  - ADR-065
9
9
  metadata:
10
- version: 3.5.0
10
+ version: 3.6.1
11
11
  tier: on-demand
12
12
  install: harness
13
13
  covers:
@@ -17,7 +17,7 @@ metadata:
17
17
  - packages/core/src/release/cut.ts
18
18
  - packages/core/src/release/authorization.ts
19
19
  loomStage: release
20
- lastReviewed: 2026-11-01
20
+ lastReviewed: 2026-11-02
21
21
  stability: stable
22
22
  ---
23
23
 
@@ -64,6 +64,8 @@ cleo release cut v2026.10.28 --sha <sha> --lead lead.md --yes # the printed co
64
64
 
65
65
  **Confirmation (D11212).** Nothing is tagged without `--yes`; without it the cut reports and prints the exact confirm command, pinned to the previewed sha. With `--yes`, an active standing release authorization covering the version, or the `release.agentCut` setting, allows the tag (an agent); otherwise the cut asks on the controlling terminal (`/dev/tty`) and tags only when the version is typed exactly, refusing with `E_RELEASE_NOT_AUTHORIZED` (and naming the scope to grant) when there is no terminal. The typed confirmation stops casual misuse only: a caller that drives a pseudo-terminal can still type the version. The audit row records `allowedBy` (`tty-confirm`, `authorization:<id>` or `setting:release.agentCut=<level>@<scope>`).
66
66
 
67
+ **Previous tag (T14173).** The notes, the CHANGELOG section (`write-changelog`) and `release reconcile` start from the newest reachable lower tag whose GitHub Release published; a tag whose `release.yml` run failed before creating its release (a failed canary) is skipped, so its changesets and tasks land in the next release. A stable cut also skips every prerelease tag. When `gh` cannot read a release (auth, network), cut and `write-changelog` refuse rather than guess; reconcile keeps the tag.
68
+
67
69
  **Agent cut setting (T14170, D11221).** `release.agentCut` is `off` (default), `canary`, `prerelease` or `stable`; an agent sets it with `cleo config set release.agentCut canary --scope global`, with no terminal or owner password. Each level covers its own scope and every narrower one: `canary` covers `-canary.N`, `prerelease` any prerelease, `stable` everything. A project value (even `off`) shadows the global one. A cut it allows reports `allowedBy`, a warning naming the setting, and an audit row with `scope` and `settingSource`; when it does not cover the version and there is no terminal, the refusal names the exact `cleo config set` command.
68
70
 
69
71
  **Standing authorization (T14141, D11215).** The owner grants it at a terminal with the owner-auth password: `cleo release authorize --scope canary|prerelease|stable|<version> --expires 7d --reason "<why>" [--uses <n>]` (at most 30d; no use limit unless `--uses`). It is signed with the enrolled owner key (`cleo config owner-enroll`), stored in `.cleo/release-authorizations.json` and the global store, recorded as an owner decision, and audited in `.cleo/audit/release-authorizations.jsonl`. `cleo release authorize --list` shows each grant's state; `--revoke <id>` (owner password too) ends one now with a signed revocation, and the revocation count is sealed in `.cleo/owner-settings.json` (commit it). An edited, unsigned or one-sided grant is ignored; an edited, unsigned or shortened revocation list makes every grant tampered (fail closed). `cleo doctor` reports both. A cut it allows carries `Authorized-by: <id>` in the tag message.
@@ -566,7 +566,7 @@
566
566
  },
567
567
  {
568
568
  "name": "ct-dev-workflow",
569
- "version": "3.4.0",
569
+ "version": "3.4.1",
570
570
  "description": "Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.",
571
571
  "path": "skills/ct-dev-workflow",
572
572
  "tier": 0,
@@ -642,7 +642,7 @@
642
642
  },
643
643
  {
644
644
  "name": "ct-documentor",
645
- "version": "3.33.0",
645
+ "version": "3.36.0",
646
646
  "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. Carries the CLEO writing and review guides as references and coordinates 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.",
647
647
  "path": "skills/ct-documentor",
648
648
  "tier": 0,
@@ -1167,7 +1167,7 @@
1167
1167
  },
1168
1168
  {
1169
1169
  "name": "ct-release-orchestrator",
1170
- "version": "3.5.0",
1170
+ "version": "3.6.1",
1171
1171
  "description": "Orchestrates CLEO releases. Default (T14102): cleo release cut {version} tags the newest main commit with green CI, and release.yml writes the CHANGELOG from changesets, publishes, and opens an auto-merging CHANGELOG + version PR; cleo release reconcile records provenance. The SPEC-T9345 4-verb pipeline (cleo release plan, cleo release open, PR + tag) stays one release as a fallback (T14114). The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline end-to-end (dry-run by default). The full verb-to-state map is in docs/release/verb-matrix.md. Use when shipping a new version, validating the release pipeline end-to-end, or promoting a completed epic to released status.",
1172
1172
  "path": "skills/ct-release-orchestrator",
1173
1173
  "tier": 1,