rulesync 16.9.1 → 16.11.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
@@ -93,7 +93,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
93
93
  | Claude Code plugin | | | ✅ | ✅ | ✅ | ✅ | ✅ | | |
94
94
  | Codex CLI | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
95
95
  | GitHub Copilot | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
96
- | GitHub Copilot CLI | ✅ | | ✅ | | ✅ | ✅ | ✅ | | |
96
+ | GitHub Copilot CLI | ✅ | | ✅ | | ✅ | ✅ | ✅ || |
97
97
  | Goose | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
98
98
  | Hermes Agent | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
99
99
  | Grok CLI | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
@@ -104,12 +104,13 @@ The tables below show whether each tool supports a given feature (✅ = supporte
104
104
  | Cline | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
105
105
  | Kilo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
106
106
  | Kimi Code | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | |
107
- | Roo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | | |
107
+ | Roo Code ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | | |
108
108
  | Zoo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | | |
109
109
  | Rovodev (Atlassian) | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
110
110
  | Takt | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
111
111
  | Vibe Code | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | |
112
112
  | Qwen Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
113
+ | Meta Muse Code | ✅ | | ✅ | | | ✅ | | | |
113
114
  | Reasonix | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
114
115
  | Kiro ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
115
116
  | Kiro CLI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
@@ -119,7 +120,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
119
120
  | Google Antigravity plugin | ✅ | | ✅ | | ✅ | ✅ | ✅ | | |
120
121
  | JetBrains AI Assistant | ✅ | ✅ | ✅ | | | ✅ | | | |
121
122
  | JetBrains Junie | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
122
- | AugmentCode | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
123
+ | AugmentCode | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ ||
123
124
  | Devin Desktop | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
124
125
  | Warp | ✅ | ✅ | ✅ | ✅ | | ✅ | | ✅ | |
125
126
  | Replit | ✅ | | | | | ✅ | | | |
@@ -147,6 +148,7 @@ The tables below show whether each tool supports a given feature (✅ = supporte
147
148
  - **Google Antigravity (`antigravity-ide` / `antigravity-cli`)** — Antigravity 2.0 splits into two products with separate global config trees: the desktop **`antigravity-ide`** and the **`antigravity-cli`** (`agy`). For project-scope rules, **both `antigravity-ide` and `antigravity-cli`** emit the root rule as a plain cross-tool **`AGENTS.md`** at the project root (the Gemini-lineage discovery order is `AGENTS.md`, `CONTEXT.md`, `GEMINI.md`; the IDE has read `AGENTS.md` since v1.20.3) and non-root rules under `.agents/rules/`.
148
149
  - **Plugin packaging (`claudecode-plugin` / `antigravity-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. See the [Plugin Packaging guide](https://dyoshikawa.github.io/rulesync/guide/plugin-packaging).
149
150
  - **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`), 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`.
151
+ - **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://dyoshikawa.github.io/rulesync/reference/supported-tools#deprecation-notes).
150
152
 
151
153
  Some features accept per-feature options. See [Configuration > Per-feature options](https://dyoshikawa.github.io/rulesync/guide/configuration#per-feature-options) for details.
152
154