Repository navigation
v3.22.2
What's new
Bug Fixes
Loading a skill no longer starts an unrelated guarded workflow. Previously, unrecognized skills were treated as ce:work, so loading ce:review, ce:brainstorm, or another skill could demand implementation evidence, reopen a completed unit, or collide with an active shipping workflow. Only ce:work, git-commit, and git-commit-push-pr now activate a workflow epoch, with or without the systematic: prefix; other skill loads leave guard state unchanged. (#1107)
Bundled workflow handoff targets now resolve, and skill instructions and review persona descriptions use loadable names such as ce:plan, ce:brainstorm, and document-review instead of directory-form names that caused not-found errors. Content-integrity checks reject stale names in code spans and prose while preserving paths, filenames, qualified agent IDs, and fenced code. (#1110, #1111)
Tests
Real-host guard tests now verify that skill loads actually succeed, rather than accepting the absence of guard markers as sufficient evidence. The non-allowlisted ce:plan scenario confirms output exceeding 32 KB and an inactive guard on a follow-up status call; the allowlisted ce:work scenario also checks the size threshold. Coverage additionally pins the fail-closed outcome when a skill name changes between hooks. (#1109, #1107)
Also in this release
- release: Version metadata updated for v3.22.2.