rulesync 3.31.0 → 3.33.0

package/README.md

@@ -189,6 +189,7 @@ Rulesync is trusted by leading companies and recognized by the industry:
 
 - **Anthropic Official Customer Story**: [Classmethod Inc. - Improving AI coding tool consistency with Rulesync](https://claude.com/customers/classmethod)
 - **Asoview Inc.**: [Adopting Rulesync for unified AI development rules](https://tech.asoview.co.jp/entry/2025/12/06/100000)
+- **KAKEHASHI Tech Blog**: [Building multilingual systems for the LLM era with a monorepo and a "living specification"](https://kakehashi-dev.hatenablog.com/entry/2025/12/08/110000)
 
 ## Quick Commands
 
@@ -273,6 +274,34 @@ Example:
 }
 ```
 
+### Target Order and File Conflicts
+
+When multiple targets write to the same output file, **the last target in the array wins**. This is the "last-wins" behavior.
+
+For example, both `agentsmd` and `opencode` generate `AGENTS.md`:
+
+```jsonc
+{
+  // opencode wins because it comes last
+  "targets": ["agentsmd", "opencode"],
+  "features": ["rules"]
+}
+```
+
+In this case:
+1. `agentsmd` generates `AGENTS.md` first
+2. `opencode` generates `AGENTS.md` second, overwriting the previous file
+
+If you want `agentsmd`'s output instead, reverse the order:
+
+```jsonc
+{
+  // agentsmd wins because it comes last
+  "targets": ["opencode", "agentsmd"],
+  "features": ["rules"]
+}
+```
+
 ## Each File Format
 
 ### `rulesync/rules/*.md`