lynxprompt 2.1.39 → 2.1.40

package/README.md

@@ -117,8 +117,15 @@ lynxp pull bp_abc123 --preview
 
 # Don't track for future syncs
 lynxp pull bp_abc123 --no-track
+
+# Fill [[VARIABLES]] as you download (others get their [[NAME|default]])
+lynxp pull bp_abc123 --vars PROJECT_NAME=acme,TEAM=Platform
 ```
 
+A file pulled with `--vars` stays tracked: `lynxp sync` refills cloud updates
+with the same values, and `lynxp push` refuses to send your values over the
+blueprint's variables unless you pass `--force`.
+
 ### Link / Unlink
 
 Connect local files to cloud blueprints:
@@ -146,6 +153,27 @@ lynxp diff bp_abc123
 lynxp diff --local
 ```
 
+### Sync
+
+Bring every tracked file and its cloud blueprint together in one step:
+
+```bash
+lynxp sync              # all tracked files
+lynxp sync AGENTS.md    # one file
+lynxp sync --dry-run    # show what would happen, change nothing
+```
+
+For each file, sync compares the local file and the cloud with the version
+you last pulled or pushed:
+
+- only the cloud changed: the file is updated from the cloud
+- only the file changed: your changes are pushed (marketplace blueprints are read-only, so they stay local)
+- both changed: the cloud version is written to `<file>.remote` and your file is left alone.
+  Merge what you need into the file, delete `<file>.remote`, and run `lynxp sync` again.
+  Until then sync and push leave that file alone.
+
+Sync exits with code 1 when a file has a conflict or could not be synced.
+
 ### Push (`lynxp push`)
 
 Upload a local configuration file to LynxPrompt cloud: