@pixlcore/xycli 1.1.0 → 1.1.1

package/docs/two-way-delete-tutorial.md

@@ -2,7 +2,7 @@
 
 This tutorial keeps Events, workflows, and Plugins in both xyOps and Git. Existing definitions can be edited on either side, and deletions can start on either side. New definitions are created in the xyOps UI and exported to Git. Every sync runs because Git accepted a push or xyOps recorded an activity. There are no cron jobs or recurring sync schedules.
 
-Use xyCLI version **v1.1.0+** (with down-sync delete support) and xyOps version **v1.1.3+** (with System Activity triggers). Both features must be available before you enable this workflow.
+Use xyCLI version **v1.1.1+** (with down-sync delete support) and xyOps version **v1.1.4+** (with System Activity triggers and exclusions). Both features must be available before you enable this workflow.
 
 > [!IMPORTANT]
 > **Two-way deletion requires authoritative triggers in both directions.** Run `--up --delete` only in response to an accepted Git change, and run `--down --delete` only in response to xyOps activity. Each invocation has exactly one authoritative side. A single command with both `--up` and `--down` cannot use `--delete`.
@@ -24,7 +24,7 @@ Use one persistent Git checkout on a machine running xySat. Target all three xyO
 
 You will need:
 
-- A xyOps API Key that can see the **complete** Event and Plugin inventories, update and delete those types, and update global sync state. A restricted or partial inventory is unsafe for up-only deletion.
+- A dedicated xyOps API Key for xyCLI that can see the **complete** Event and Plugin inventories, update and delete those types, and update global sync state. A restricted or partial inventory is unsafe for up-only deletion. You will select this same key in the System Activity trigger exclusions below.
 - A dedicated repository and a persistent checkout, such as `/srv/xyops-automation`, with noninteractive Git pull and push access.
 - A Git author identity for commits generated by xyOps.
 - Shared xyOps job capacity and queue limits on all three Events.
@@ -171,6 +171,8 @@ Create three Shell Plugin Events in xyOps, initially disabled. Target only the s
 | **Export creations from xyOps** | System Activity | `event_create`, `plugin_create` | `/usr/local/sbin/xyops-git-sync create` |
 | **Apply accepted Git pushes** | Manual | No activity selection | `/usr/local/sbin/xyops-git-sync up` |
 
+On **each of the two System Activity triggers**, open **Exclude Users / Keys** and select the dedicated xyCLI sync API Key configured on the worker in step 1. xyOps records the key's ID as the activity initiator and skips that trigger when the ID is excluded. This prevents an upsync API update or deletion from launching a redundant downsync job. Leave ordinary users out of the exclusion list so their UI changes still launch the appropriate job. If more than one API Key can make sync writes, exclude each of those keys on both triggers.
+
 The update activities make xyOps UI edits flow back to Git too. The separate creation Event runs `sync setup --new`, because ordinary downsync updates existing local sources but does not create files for new xyOps definitions. The setup command's `--down_cmd` runs only when it writes files; the down-delete command's `--down_cmd` runs only after local changes. Neither creates an empty Git commit on a no-op run.
 
 The Git Event has an enabled **Manual** trigger so a Git hook or verified webhook receiver can launch it with `xy run` or the [`run_event` API](https://docs.xyops.io/api#run_event). It has no schedule. The Git push is still the authoritative reason for that run.
@@ -237,6 +239,7 @@ Run these tests with disposable Events and Plugins, not production definitions:
 3. Delete it in xyOps. Confirm that the **down** Event removes the XYPDF and owned neighbor files and pushes the deletion.
 4. Edit an existing definition in Git and push. Confirm that the accepted-push trigger runs **up** and updates xyOps.
 5. Delete a different existing definition in Git and push. Confirm that **up** deletes only that definition in xyOps.
+6. For both Git-initiated tests, confirm that the sync API Key's activity did not launch either System Activity Event. A second downsync job means the key is missing from a trigger's exclusion list.
 
 Before the first live delete, preview each direction against the complete checkout and inspect every proposed deletion:
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@pixlcore/xycli",
-	"version": "1.1.0",
+	"version": "1.1.1",
 	"description": "A complete command-line interface for the xyOps workflow automation system.",
 	"author": "Joseph Huckaby <jhuckaby@pixlcore.com>",
 	"homepage": "https://github.com/pixlcore/xycli",
@@ -24,6 +24,9 @@
 		"test:offline": "node --test test/config.test.js test/help.test.js test/markdown.test.js test/sync-buckets-unit.test.js test/sync-syshook-unit.test.js test/sync-unit.test.js test/toast.test.js test/upgrade.test.js test/utils-unit.test.js",
 		"changelog": "node tools/changelog.js"
 	},
+	"overrides": {
+		"basic-ftp": "6.2.1"
+	},
 	"dependencies": {
 		"@pixlcore/xyops-sdk": "^1.0.7",
 		"cli-highlight": "2.1.11",