rulesync 33.0.0 → 34.0.0

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
@@ -115,7 +115,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
115
115
  | Kimi Code plugin | ✅ | | | ✅ | ✅ | ✅ | | | |
116
116
  | Roo Code ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | ✅ | |
117
117
  | Zoo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | ✅ | |
118
- | Rovodev (Atlassian) | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
118
+ | Rovodev (Atlassian) ⚠️ | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
119
119
  | Takt | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
120
120
  | Trae | ✅ | | ✅ | | | ✅ | | | |
121
121
  | Tabnine CLI ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
@@ -127,7 +127,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
127
127
  | Qwen Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
128
128
  | Meta Muse Code | ✅ | | ✅ | | | ✅ | | | |
129
129
  | Reasonix | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
130
- | Codebuff (Freebuff) | | ✅ | ✅ | | | | | | |
130
+ | Codebuff (Freebuff) | ✅ | ✅ | ✅ | | | | | | |
131
131
  | Kiro ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
132
132
  | Kiro CLI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
133
133
  | Kiro IDE | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
@@ -176,6 +176,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
176
176
  - **Kiro (`kiro`)** — Kiro's IDE and CLI use diverging config formats (IDE: Markdown subagents `.kiro/agents/*.md`; CLI: JSON agent-config subagents `.kiro/agents/*.json`), so `kiro` is split into **`kiro-cli`** and **`kiro-ide`**. The legacy `kiro` target remains as a **deprecated alias** with its current behavior unchanged. The two targets share every surface except **subagents** (Markdown vs JSON); both emit hooks as a single `.kiro/hooks/rulesync.json` (`{ "version": "v1", "hooks": [ ... ] }`) in project (`.kiro/hooks/`) and global (`~/.kiro/hooks/`) scope, the format Kiro CLI 3.0 [migrated to](https://kiro.dev/docs/cli/v3/hooks-migration/). Only the deprecated `kiro` alias still writes hooks into `.kiro/agents/default.json`, which the CLI no longer reads. Global skills (`~/.kiro/skills/`), global ignore (`~/.kiro/settings/kiroignore`, which only the IDE reads, so `kiro-cli` skips it), and global Kiro IDE subagents (`~/.kiro/agents/`) are supported too, as are global Kiro CLI commands (`~/.kiro/prompts/`) and subagents (`~/.kiro/agents/`). Kiro MCP generation preserves per-server `disabledTools`, and the deprecated `kiro` alias's hook caching maps `cacheTtl` to `cache_ttl_seconds`.
177
177
  - **Tabnine CLI (`tabnine`)** — The file-based Tabnine CLI is in maintenance mode: as of Tabnine 6.6 (2026-09-15) it is "Tabnine CLI (Legacy)" (`tabnine-legacy`), receiving only critical updates through 2026-12-31. The new `tabnine` command is Tabnine's distribution of OpenCode and reads standard OpenCode files, so target it with `--targets opencode`. The `tabnine` target stays supported for the legacy CLI. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
178
178
  - **Roo Code (`roo`)** — Roo Code is end of life: its final release was **v3.54.0 (2026-05-15)** and its repository is archived. New projects should target **`zoocode`** ([Zoo Code](https://github.com/Zoo-Code-Org/Zoo-Code)), the community continuation named by the Roo shutdown notice. The `roo` target stays supported because Zoo Code still reads the same `.roo/` project tree and `~/.roo` global tree, so existing output keeps working — it just no longer tracks anything Zoo Code added after the fork. Enable one of the two targets per project, not both. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
179
+ - **Rovo Dev (`rovodev`)** — Atlassian has announced that Rovo Dev as a standalone product will reach end of life (date TBA, with at least 60 days' notice) and that Rovo Dev CLI is evolving into the unified Atlassian Rovo CLI. Until migration instructions are shared, the `rovodev` target stays supported and keeps emitting the current Rovo Dev CLI files. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
179
180
 
180
181
  Some features accept per-feature options. See [Configuration > Per-feature options](https://rulesync.dyoshikawa.com/guide/configuration#per-feature-options) for details.
181
182