@mfjjs/ruflo-setup 0.2.8 → 0.2.9

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/CHANGELOG.md CHANGED
@@ -2,6 +2,8 @@
2
2
 
3
3
  All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
4
4
 
5
+ ### [0.2.9](///compare/v0.2.8...v0.2.9) (2026-03-31)
6
+
5
7
  ### [0.2.8](///compare/v0.2.7...v0.2.8) (2026-03-31)
6
8
 
7
9
 
package/README.md CHANGED
@@ -241,3 +241,62 @@ This tests exactly what users get from a package install.
241
241
  - `claude-hooks/check-ruflo.cjs`
242
242
 
243
243
  It merges into existing global settings instead of replacing them, and creates a backup of the settings file before writing.
244
+
245
+ ## 🖥️ Windows vs Linux/WSL differences
246
+
247
+ `ruflo-setup` supports both Windows and Linux (including WSL), but there are important platform differences to be aware of.
248
+
249
+ ### Platform-specific generated files
250
+
251
+ The `.mcp.json` and `.claude/settings.json` files generated by `ruflo-setup` contain **platform-specific commands and paths**. For this reason, both files are excluded from version control via `.gitignore`:
252
+
253
+ ```
254
+ .mcp.json
255
+ .claude/settings.json
256
+ ```
257
+
258
+ **Practical implications:**
259
+
260
+ - These files are not committed and will not be present after cloning a repository.
261
+ - You must rerun `ruflo-setup --force` (or `ruflo-setup --yes`) after cloning into any new folder, especially when switching platforms (e.g. cloning on Windows after previously working on Linux/WSL, or vice versa).
262
+ - Each developer generates their own local copy of these files tailored to their platform.
263
+
264
+ ### Git file permission changes
265
+
266
+ When switching from Windows to Linux/WSL (or vice versa), you may notice that `git status` shows files as modified even though their content has not changed. This is a **file mode change**: tools such as Claude Code, git, or `ruflo-setup` may have updated the Unix permission bits of tracked files — for example from `0644` (non-executable) to `0755` (executable) — under the hood.
267
+
268
+ You can confirm this with:
269
+
270
+ ```bash
271
+ git diff --summary
272
+ ```
273
+
274
+ Which will show lines like:
275
+
276
+ ```
277
+ mode change 100644 => 100755 some/file.js
278
+ ```
279
+
280
+ If these mode changes are unintentional, you can discard them with:
281
+
282
+ ```bash
283
+ git checkout -- .
284
+ ```
285
+
286
+ Or suppress mode tracking for the repository entirely:
287
+
288
+ ```bash
289
+ git config core.fileMode false
290
+ ```
291
+
292
+ Note that `core.fileMode false` is a local config setting and is not committed — each developer must set it on their own clone if needed.
293
+
294
+ ### Summary
295
+
296
+ | Concern | Windows | Linux / WSL |
297
+ |---|---|---|
298
+ | `.mcp.json` commands | Windows-style paths / `cmd.exe` shims | Unix paths / shell commands |
299
+ | `.claude/settings.json` | Windows-native format | Unix format |
300
+ | Git mode changes (0644→0755) | Not tracked by default | May appear as unexpected diffs |
301
+ | Git tracking | Excluded via `.gitignore` | Excluded via `.gitignore` |
302
+ | After cloning | Rerun `ruflo-setup --force` | Rerun `ruflo-setup --force` |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mfjjs/ruflo-setup",
3
- "version": "0.2.8",
3
+ "version": "0.2.9",
4
4
  "description": "Cross-platform setup CLI for Ruflo + Claude Flow projects",
5
5
  "type": "module",
6
6
  "bin": {