fix: Release v3.5 - Fix interactive prompts via Array Strategy

Resolves a regression where push/pull confirmation prompts were being skipped.

**The Fix:**
* Refactored the file iteration logic in `push` and `pull` commands.
* Previously, the `while read` loop consumed `stdin`, preventing the `confirm()` function from reading user input during `[y/N]` prompts.
* Now loads the target file list into an array first, freeing up `stdin` for interactive prompts.

**Changes:**
* refactor: Implement "Array Strategy" for file processing to avoid FD conflicts.
* fix: Ensure `read -p` works correctly in Zsh/Bash strict modes.
* chore: Bump version to 3.5.

Author: snvishna

README.md

@@ -3,14 +3,14 @@
 **The minimalist's answer to dotfile management.**
 Sync your shell configurations, editor settings, and scripts to a secret GitHub Gist—securely, instantly, and without the bloat.
 
-Now with cross-platform support for **macOS** and **Linux**.
+Now with **Interactive Mode**, **Batch Syncing**, and **Cross-Platform Support** (macOS & Linux).
 
 ---
 
 ## 🎥 See it in action
 
-### 1. Syncing (Push)
-*Instant backup of your local settings to the cloud.*
+### 1. Interactive Push (Default)
+*Review changes file-by-file before uploading.*
 ![](./resources/dfsync-push.gif)
 
 ### 2. First Time Setup
@@ -26,9 +26,9 @@ Most dotfile managers are over-engineered. They force you to move your files, cr
 **dotfilesync is different:**
 * **📍 Non-Destructive:** Your files stay exactly where they are. No symlinks. No moving files.
 * **🔒 Secure by Design:**
-    * **macOS:** Uses the native **Keychain** to store tokens.
-    * **Linux:** Uses a secured file with strict read-only permissions.
-* **🚀 Zero Friction:** No `git add`, `git commit`, `git push`. Just `dfsync push`.
+    * **macOS:** Uses native **Keychain** (encrypted at rest).
+    * **Linux:** Uses a locked-down file (`600` permissions) readable only by you.
+* **🤝 Interactive or Automated:** Confirm every file operation manually, or use `-y` for instant batch processing.
 * **🛠 Zero Dependencies:** Written in pure Bash. Configuration is a simple JSON file.
 
 ---
@@ -37,70 +37,92 @@ Most dotfile managers are over-engineered. They force you to move your files, cr
 
 You do not need to clone this repository. Install the binary directly to your path using `curl`.
 
-```bash
+'''bash
 mkdir -p ~/.local/bin
 curl -fsSL https://raw.githubusercontent.com/snvishna/dotfilesync/master/src/dfsync.sh -o ~/.local/bin/dfsync
 chmod +x ~/.local/bin/dfsync
-```
+'''
 
 > **Note:** Ensure `~/.local/bin` is in your `$PATH`.
 
 ### Prerequisites
 * **curl** (Standard on most systems)
 * **jq** (Required for JSON parsing)
 
-```bash
+'''bash
 # macOS
 brew install jq
 
 # Linux (Ubuntu/Debian)
 sudo apt-get install jq
-```
+'''
 
 ---
 
 ## 🚦 Quick Start Guide
 
-Follow these four steps to back up your environment in under 2 minutes.
-
 ### 1. Connect (Setup)
-First, link your machine to GitHub securely. You will need a **GitHub Personal Access Token (Classic)** with **`gist`** scope.
-
+First, link your machine to GitHub. You need a **Personal Access Token (Classic)** with **`gist`** scope.
 * [Generate Token Here](https://github.com/settings/tokens/new?scopes=gist&description=dotfilesync)
 
 Run the setup wizard:
-```bash
+'''bash
 dfsync setup
-```
-*Tip: Use `dfsync setup -y` to automatically accept default config paths.*
+'''
+*(Use `dfsync setup -y` to auto-accept default config paths).*
 
 ![](https://github.com/snvishna/dotfilesync/blob/master/resources/generate_personal_access_token.gif)
 
 ### 2. Track Files
-Tell dfsync which files you want to manage. You can track individual files from anywhere in your home directory.
+Tell dfsync which files you want to manage.
 
-```bash
-# Track your Zsh config
+'''bash
 dfsync track ~/.zshrc
-
-# Track your Starship prompt config
 dfsync track ~/.config/starship.toml
-```
+'''
 
 ### 3. Sync (Push)
-Upload your tracked files to the cloud. If you don't have a Gist yet, this command creates one for you automatically.
+Upload your tracked files.
 
-```bash
+**Interactive Mode (Safest):**
+'''bash
 dfsync push
-```
+# Prompts: "Upload /Users/me/.zshrc? [y/N]"
+'''
+
+**Batch Mode (Fastest):**
+'''bash
+dfsync push -y
+# Uploads everything immediately.
+'''
 
 ### 4. Restore (Pull)
-On a new machine (or if you accidentally delete a config), download the latest version from your Gist.
+On a new machine, download your configs.
 
-```bash
+'''bash
 dfsync pull
-```
-*⚠️ Warning: This overwrites your local files with the version from the Gist.*
+'''
+*Prompts you before overwriting any local file, unless you use `-y`.*
+
+---
+
+## 🛠 CLI Reference
+
+Flags can be placed anywhere (e.g., `dfsync -y push` or `dfsync push -y`).
+
+| Command | Usage | Description |
+| :--- | :--- | :--- |
+| **setup** | `dfsync setup [-y]` | Initialize token and config. |
+| **track** | `dfsync track <file>` | Add a file to the sync list. |
+| **untrack** | `dfsync untrack <file>` | Remove a file from the sync list. |
+| **push** | `dfsync push [-y] [-v]` | Upload files. Default is interactive. `-y` auto-confirms. |
+| **pull** | `dfsync pull [-y] [-v]` | Download files. Default is interactive. `-y` auto-confirms. |
+| **config** | `dfsync config token` | Update your GitHub Access Token. |
+| **help** | `dfsync help` | Show usage guide. |
+
+**Global Options:**
+* `-y`, `--yes`: Non-interactive mode. Auto-answers "yes" to all prompts.
+* `-v`, `--verbose`: Enable detailed debug logs (HTTP status, payload sizes, etc).
 
 ---
 
@@ -110,7 +132,7 @@ dfsync uses a single JSON file to track your state.
 **Default Location:** `~/.config/dfsync.json`
 
 ### The Config Structure
-```json
+'''json
 {
   "gist_id": "8f3... (Auto-generated)",
   "files": [
@@ -119,44 +141,22 @@ dfsync uses a single JSON file to track your state.
     "~/.vimrc"
   ]
 }
-```
-You can edit this file manually if you prefer, or use the CLI commands (`track`/`untrack`) to manage it.
-
-> **Legacy Support:** If you are upgrading from an older version, your existing config (`dotFilePaths` / `gistId`) works automatically.
-
----
-
-## 🛠 CLI Reference
-
-| Command | Usage | Description |
-| :--- | :--- | :--- |
-| **setup** | `dfsync setup [-y]` | Initialize token and config. `-y` accepts defaults. |
-| **track** | `dfsync track <file>` | Add a file to the sync list. |
-| **untrack** | `dfsync untrack <file>` | Remove a file from the sync list. |
-| **push** | `dfsync push [-v]` | Upload tracked files. `-v` shows detailed logs. |
-| **pull** | `dfsync pull [-v]` | Download files from Gist. `-v` shows detailed logs. |
-| **config token** | `dfsync config token` | Update your GitHub Access Token. |
-| **config path** | `dfsync config path` | Change the location of the `dfsync.json` file. |
-| **help** | `dfsync help` | Show usage guide. |
+'''
+> **Note:** Backward compatibility with older config schemas (`dotFilePaths`, `gistId`) is built-in.
 
 ---
 
 ## 🧠 Deep Dive
 
 ### Security Model
-Unlike tools that store API tokens in plain text (`~/.npmrc`, `~/.git-credentials`), dotfilesync prioritizes security.
-
 * **macOS:** Uses the native **Keychain** (Service: `dotfilesync`). The token is encrypted and only accessible when your Mac is unlocked.
-* **Linux:** Stores the token in `~/.dfsync_token` with strict `600` permissions (read/write only by the owner).
+* **Linux:** Stores the token in `~/.dfsync_token`. The script enforces `chmod 600` on this file, meaning no other user on the system can read it.
 
 ### The "Flattening" Strategy
-GitHub Gists do not support folders—they are flat lists of files. To support deep directory structures (like `~/.config/nvim/init.lua`), dotfilesync "flattens" filenames during upload using a double underscore delimiter (`__`).
-
+GitHub Gists do not support folders. To support deep directory structures (like `~/.config/nvim/init.lua`), dotfilesync "flattens" filenames during upload using a double underscore delimiter (`__`).
 * **Local:** `~/.config/nvim/init.lua`
 * **Gist:** `_config__nvim__init.lua`
 
-When you `pull`, the script intelligently reverses this transformation to restore files to their correct folders.
-
 ---
 
 ## ❓ Troubleshooting
@@ -167,8 +167,11 @@ The script depends on `jq` to parse JSON. Install it via Homebrew (`brew install
 **"Token not found"**
 If you upgraded from v1, run `dfsync config token <paste_token>` to migrate your token to the new secure storage.
 
-**"404 Not Found" during Push**
-Ensure your GitHub Token has the **`gist`** scope enabled. If the token is invalid, generate a new one and update it using `dfsync config token`.
+**Script crashes or weird errors?**
+Run with verbose mode to see exactly what's happening:
+'''bash
+dfsync push -v
+'''
 
 ---