Release v16.14.0 · dyoshikawa/rulesync

What's Changed

Mode-specific rule directories are now authorable. A roo: frontmatter section with a mode key routes a non-root rule to .roo/rules-{mode}/ (global ~/.roo/rules-{mode}/), the directory Roo Code and Zoo Code load instead of .roo/rules/ while that custom mode is active. The section is shared by the roo and zoocode targets, which write the same .roo/ tree. Import lifts the mode back into roo.mode. Mode slugs are validated against the alphabet the tools themselves accept, and mode directories are deliberately left out of the orphan-deletion sweep so hand-authored mode rules are never removed. (#2711, part of #2596)
zoocode is now a permissions target. Canonical bash allow/deny rules are written as zoo-code.allowedCommands / zoo-code.deniedCommands in the workspace .vscode/settings.json (project scope), the settings Zoo Code unions into its auto-approval lists. The file is co-owned with the existing GitHub Copilot keys, so unrelated editor settings and the other target's keys are preserved. (#2710, part of #2596)

Dropping an unsupported per-server tool filter is no longer silent. When a target cannot express enabledTools / disabledTools, the generate now names the servers whose filter is being discarded instead of stripping it quietly. (#2709, part of #2596)