rulesync 43.2.0 → 43.4.0

package/README.md

@@ -178,7 +178,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
 - **Plugin packaging (`claudecode-plugin` / `antigravity-plugin` / `augmentcode-plugin` / `zcode-plugin` / `vibe-plugin` / `devin-plugin` / `kimi-code-plugin`)** — These project-only targets generate and import Rulesync-managed components inside an existing plugin directory selected with `--output-roots` (generate) or `--output-root` (import). They are excluded from `--targets "*"` to avoid writing package-level `skills/`, `rules/`, or `commands/` directories into ordinary projects. Rulesync preserves plugin manifests, marketplace metadata, scripts, and other non-component assets; the only manifest it writes is a missing Antigravity `plugin.json`, which Antigravity needs to load the plugin at all. See the [Plugin Packaging guide](https://rulesync.dyoshikawa.com/guide/plugin-packaging).
 - **Continue (`continue`)** — Continue is end of life: it joined Cursor on 2026-06-18, the [continuedev/continue](https://github.com/continuedev/continue) repository is read-only with a final v2.0.0 release (2026-06-19), and its last commit is from 2026-07-21. The `continue` target stays supported as a frozen-compatibility target verified against that final source tree, so existing output keeps working — it just will not track anything new. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
 - **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`; Kiro's [capability matrix](https://kiro.dev/docs/kiroignore/) lists only CLI V3 for it), and global Kiro IDE subagents (`~/.kiro/agents/`) are supported too, as are global Kiro CLI commands (`~/.kiro/prompts/`) and subagents (`~/.kiro/agents/`), and global permissions for `kiro-cli`/`kiro-ide` as capability rules in `~/.kiro/settings/permissions.yaml` (project permissions stay in `.kiro/agents/default.json`). Kiro MCP generation preserves per-server `disabledTools`, and the deprecated `kiro` alias's hook caching maps `cacheTtl` to `cache_ttl_seconds`.
-- **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. It bundles OpenCode 1.x (1.18.9 as of Tabnine CLI 1.0.8), so target it with `--targets opencodev1`, not `--targets opencode`, which writes for OpenCode 2.x. The `tabnine` target stays supported for the legacy CLI. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
+- **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. It bundles OpenCode 1.x (1.19.5 as of Tabnine CLI 1.2.0), so target it with `--targets opencodev1`, not `--targets opencode`, which writes for OpenCode 2.x. The `tabnine` target stays supported for the legacy CLI. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
 - **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).
 - **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).