@n8n-as-code/n8nac 2.1.2-next.24 → 2.1.3-next.151

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @n8n-as-code/n8nac
 
+## [2.1.2](https://github.com/EtienneLescot/n8n-as-code/compare/@n8n-as-code/n8nac@v2.1.1...@n8n-as-code/n8nac@v2.1.2) (2026-05-13)
+
+### Documentation
+
+* align environment terminology ([6c79f5b](https://github.com/EtienneLescot/n8n-as-code/commit/6c79f5b57e349d59035dc57a464401f493dd75b7))
+
 ## [2.1.1](https://github.com/EtienneLescot/n8n-as-code/compare/@n8n-as-code/n8nac@v2.1.0...@n8n-as-code/n8nac@v2.1.1) (2026-05-12)
 
 ### Documentation

package/README.md

@@ -6,9 +6,9 @@ The plugin uses the same model as VS Code, Claude, and the CLI:
 
 | Group | Command | Purpose |
 |---|---|---|
-| Usage Principal | `n8nac env` | Workspace environments |
-| Maintenance Workspace | `n8nac workspace` | Readiness, unified migration, upgrade |
-| Instances Managées | `n8n-manager` | Local managed instances and tunnels |
+| Primary Usage | `n8nac env` | Workspace environments |
+| Workspace Maintenance | `n8nac workspace` | Readiness and unified workspace migration |
+| Managed Local Instances | `n8n-manager` | Local managed instances and tunnels |
 
 ## Install
 
@@ -58,22 +58,22 @@ OpenClaw files live in `~/.openclaw/n8nac/`:
   workflows/
 ```
 
-`n8nac-config.json` stores workspace environments. API keys and managed local instance state stay local.
+`n8nac-config.json` stores workspace environments. API keys and local managed instance state stay local.
 
 Manual equivalent:
 
 ```bash
-n8nac env add Dev --base-url <url> --sync-folder workflows/dev
+n8nac env add Dev --base-url <url> --workflows-path workflows/dev
 n8nac env auth set Dev --api-key-stdin
 n8nac env use Dev
 n8nac update-ai
 ```
 
-For a managed local instance:
+For a local managed instance:
 
 ```bash
 n8n-manager instance list
-n8nac env add Local --managed-instance <id> --sync-folder workflows/local
+n8nac env add Local --managed-instance <id> --workflows-path workflows/local
 ```
 
 ## Agent Commands

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@n8n-as-code/n8nac",
-  "version": "2.1.2-next.24",
+  "version": "2.1.3-next.151",
   "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
   "keywords": [
     "n8n",
@@ -24,7 +24,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@n8n-as-code/telemetry": "2.0.0",
+    "@n8n-as-code/telemetry": "2.0.1-next.151",
     "@n8n-as-code/workflow-core": "2.0.0"
   },
   "devDependencies": {

package/skills/n8n-architect/SKILL.md

@@ -11,21 +11,21 @@ Use `npx --yes n8nac@next` as the primary interface. Use `npx --yes @n8n-as-code
 
 ## Context Root Protocol
 
-- Treat the current context root as the directory containing `n8nac-config.json`, `AGENTS.md`, `.agents/skills`, and the workflow sync folder.
+- Treat the current context root as the directory containing `n8nac-config.json`, `AGENTS.md`, `.agents/skills`, and the configured `workflowsPath`.
 - Generated context root hint: not embedded. Use the shell launch directory or the workspace path explicitly given by the user.
 - Before any n8n work, first run `npx --yes n8nac@next update-ai` from the context root, then read `AGENTS.md`. `update-ai` is designed to create or refresh the n8n-as-code block without destroying existing user or agent instructions.
 - Use the exact `n8nac command` and `n8n-manager command` listed in `AGENTS.md`. Those context-root commands override the portable examples in this skill.
 - Run every `npx --yes n8nac@next env ...`, `npx --yes n8nac@next workspace ...`, `npx --yes n8nac@next list`, `pull`, `push`, `validate`, `test`, and `update-ai` command from the context root unless the user explicitly gives another context root.
 - `AGENTS.md` is bootstrap context only, not a source of configuration truth.
-- Do not infer environment, project, sync folder, or workflow directory from `AGENTS.md`.
+- Do not infer environment, project, or `workflowsPath` from `AGENTS.md`.
 - Before n8n work, resolve the effective context from the backend:
 
 ```bash
 npx --yes n8nac@next env status --json
 ```
 
-- Use the returned `workflowDir` for workflow files. Treat it as an opaque backend-derived path that may contain generated or hashed segments.
-- `syncFolder` is only the user-configured sync root, not the workflow directory. Do not reconstruct `workflowDir` from `syncFolder`, environment name/id, `instanceIdentifier`, `instanceUserIdentifier`, `projectId`, or `projectName`.
+- Use the returned `workflowsPath` for workflow files. It is the configured workflow directory for the active environment.
+- Do not reconstruct `workflowsPath` from environment name/id, `instanceIdentifier`, `instanceUserIdentifier`, `projectId`, `projectName`, or legacy sync fields.
 - Never write `n8nac-config.json`, `~/.n8n-manager`, or n8n-manager secret files by hand.
 
 ## Workspace Readiness
@@ -82,7 +82,7 @@ npx --yes n8nac@next env status --json
 10. Configure the environment with:
 
 ```bash
-npx --yes n8nac@next env add <name> --base-url <url> --sync-folder workflows
+npx --yes n8nac@next env add <name> --base-url <url> --workflows-path workflows/<name>
 npx --yes n8nac@next env auth set <name> --api-key-stdin
 npx --yes n8nac@next env use <name>
 ```
@@ -90,7 +90,7 @@ npx --yes n8nac@next env use <name>
 For a managed local instance:
 
 ```bash
-npx --yes n8nac@next env add Local --managed-instance <id> --sync-folder workflows
+npx --yes n8nac@next env add Local --managed-instance <id> --workflows-path workflows/local
 npx --yes n8nac@next env use Local
 ```
 
@@ -98,12 +98,12 @@ npx --yes n8nac@next env use Local
 
 ## Environments
 
-Use `npx --yes n8nac@next env ...` for workspace environments, remote URLs, active environment, API-key binding, projects, and sync folders.
+Use `npx --yes n8nac@next env ...` for workspace environments, remote URLs, active environment, API-key binding, projects, and workflow paths.
 
 ```bash
 npx --yes n8nac@next env status --json
 npx --yes n8nac@next env list
-npx --yes n8nac@next env add <name> --base-url <url> --sync-folder workflows
+npx --yes n8nac@next env add <name> --base-url <url> --workflows-path workflows/<name>
 npx --yes n8nac@next env auth set <name> --api-key-stdin
 npx --yes n8nac@next env use <name>
 ```
@@ -117,7 +117,7 @@ npx --yes n8nac@next env use <name>
 Attach a managed local instance to the workspace with `npx --yes n8nac@next env ...`:
 
 ```bash
-npx --yes n8nac@next env add Local --managed-instance <id> --sync-folder workflows
+npx --yes n8nac@next env add Local --managed-instance <id> --workflows-path workflows/local
 npx --yes n8nac@next env use Local
 ```
 
@@ -195,7 +195,7 @@ npx --yes n8nac@next push <path-to-workflow.workflow.ts> --verify
 ```
 
 - `push` requires the full workflow file path, either absolute or context-root-relative. Do not pass a bare filename.
-- For a new workflow, create the file inside the `workflowDir` returned by `env status --json`, then confirm it with `npx --yes n8nac@next list --local`.
+- For a new workflow, create the file inside the `workflowsPath` returned by `env status --json`, then confirm it with `npx --yes n8nac@next list --local`.
 - If push/pull reports a conflict, use explicit resolution commands. Do not overwrite remote changes blindly.
 - `pull` and conflict resolution operate on a single workflow ID.
 - `list` is the lightweight command that covers all workflows at once.
@@ -491,7 +491,7 @@ npx --yes n8nac@next workflow activate <workflowId>
 For most workflow tasks:
 
 1. Resolve context with `env status --json`.
-2. Read `workflowDir` from the backend response.
+2. Read `workflowsPath` from the backend response.
 3. Inspect existing workflows with `list`.
 4. Pull before editing an existing workflow.
 5. Search examples and schemas.